Can the following ebuild be stablised. mail-client/balsa/balsa-2.0.15-r2.ebuild x86 alpha Can the following ebuilds please be removed: mail-client/balsa/balsa-2.0.14.ebuild mail-client/balsa/balsa-2.0.15-r1.ebuild app-crypt/seahorse/seahorse-0.6.3.ebuild
stablising: x86: mail-client/balsa/balsa-2.0.15-r2.ebuild removal: rm: mail-client/balsa/balsa-2.0.14.ebuild rm: app-crypt/seahorse/seahors-0.6.3.ebuild mail-client/balsa/balsa-2.0.15-r1.ebuild can't be removed until -r2 is alpha.
alpha people: forgot to add a test plan differences between mail-client/balsa/balsa-2.0.15-r1.ebuild and -r2 are: 1. it depends on the next revision of gpgme (0.3.14-r1) which installs libraries to a different location. 2. It does some checking for gnupg-1.9+ and uses gpg2 if present. test stratergy: ensure that only gpgme-0.3.14-r1 is installed an no other pre 0.9.0 ebuilds. 0.9.0+ ebuilds of gpgme are on their own slot and won't affect the test. See if mail-client/balsa/balsa-2.0.15-r2 compiles/installs. A quick run of the balsa gui should be enought to confirm.
thanks for the alpha keyword test kloeri and thanks foser for allowing me to remove lots of pain in the neck gpgme ebuilds.