Mon Aug 15 15:10:58 CDT 2005 If user already has proftpd emerge, user will not be able to update proftpd unless he/she unmerges it first. Example: localhost conf.d # emerge --pretend --update proftpd These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] <net-ftp/proftpd-1.2.10-r6 (is blocking net-ftp/ftpbase-0.00) [ebuild N ] net-ftp/ftpbase-0.00 [ebuild U ] net-ftp/proftpd-1.2.10-r7 [1.2.10-r1] If user wants update proftpd they must manually unmerge proftpd first. emerge --unmerge proftpd Then he/she can safely update proftpd by emerging it again. localhost conf.d # emerge --pretend proftpd These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] net-ftp/ftpbase-0.00 [ebuild N ] net-ftp/proftpd-1.2.10-r7 of course you would not "--pretend" when updateing this package. Reproducible: Always Steps to Reproduce: 1. Already have proftpd emerged 2. emerge --pretend --update proftpd 3. Actual Results: emerge refuses to updaet proftp as the old version of proftpd blocks the newer ftpbase. Expected Results: updated proftpd automaticly
*** This bug has been marked as a duplicate of 100783 ***
