Often I use portage overly to enhance featuresets of packages, however when emerge --update doesn't show when it's updating something from overly, whilst updating a version, it might actually reduce the featureset, and stop a deamon from running. For example, I have hacked the exim-4.43-r1 ebuild to allow SPF, however exim-4.43-r2 came out, and emerge didn't make it appearnt it was about to update a custom package. I could rename my package to eximcustom-4.43, but then I don't know when my package isn't the latest version anymore. A little [1] should appear, likeit does when installing something form overlay, to inform you it's updating something. Reproducible: Always Steps to Reproduce: 1. 2. 3.
emerge -pv shows that information already.
It doens't. No warning is visible below, but as tests show, currently installed exim is in portage overly, and the one it's trying to upgrade to isn't. # emerge --update --deep world -pv These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] mail-mta/exim-4.43-r2 [4.43-r1] -X -dnsdb +exiscan +exiscan-acl +ipv6 +ldap -lmtp -mailwrapper -mbox +mysql -nis +pam +perl -postgres -sasl +ssl -syslog -tcpd 0 kB Total size of downloads: 0 kB # qpkg -vv -I exim /var/db/pkg/mail-mta/exim-4.43-r1/exim-4.43-r1.ebuild mail-mta/exim-4.43-r1 * # diff /var/db/pkg/mail-mta/exim-4.43-r1/exim-4.43-r1.ebuild /usr/portage/mail-mta/exim/exim-4.43-r1.ebuild | wc -l 42 # diff /var/db/pkg/mail-mta/exim-4.43-r1/exim-4.43-r1.ebuild /usr/local/portage/mail-mta/exim/exim-4.43-r1.ebuild | wc -l 0
we cant hold your hand with everything i think `emerge -pv` is more than sufficient and/or files in /etc/portage/ to control local masking
Please see bug 77873 for a potential "solution" to this problem.
