upgrading from proftpd to pureftpd installs -r1 by default (no ACCEPT_KEYWORD="~x86", resulting in a block: # emerge -upvD world [blocks B ] <net-ftp/pure-ftpd-1.0.20-r2 (is blocking net-ftp/ftpbase-0.00) [ebuild N ] net-ftp/ftpbase-0.00 +pam 0 kB with # ACCEPT_KEYWORDS="~x86" emerge pure-ftpd -r2 gets installed, the block is resolved however portage want's to downgrade to -r1 (stable version) best, Ilona Reproducible: Always Steps to Reproduce: Detailed procedure at http://forums.gentoo.org/viewtopic.php?p=2890811 Actual Results: pure-ftpd -r1 blocks baseftp, pure-ftpd -r2 does not. Expected Results: pure-ftpd -r1 should not block baseftp
(In reply to comment #0) > upgrading from proftpd to pureftpd installs -r1 by default (no > ACCEPT_KEYWORD="~x86", resulting in a block: > > # emerge -upvD world > > [blocks B ] <net-ftp/pure-ftpd-1.0.20-r2 (is blocking net-ftp/ftpbase-0.00) > [ebuild N ] net-ftp/ftpbase-0.00 +pam 0 kB is an known behaviour, you are required to unmerge to old version first; portage won't handle this transparently yet. > # ACCEPT_KEYWORDS="~x86" emerge pure-ftpd > > -r2 gets installed, the block is resolved however portage want's to downgrade > to -r1 (stable version) is plain bad, that's what /etc/portage/package.keywords is for. *** This bug has been marked as a duplicate of 79606 ***