After upgrading from portage-2.0.49-r4 to portage-2.0.49-r5 this morning, I'm getting lots of warnings such as the following: Generating cache entry(0) for: /usr/portage/x11-base/xfree/xfree-4.1.0-r6.ebuil|Generating cache entry(0) for: /usr/portage/x11-base/xfree/xfree-4.3.99.11.ebuild Generating cache entry(2) for: /usr/portage/x11-base/xfree/xfree-4.3.99.11.ebuild These warnings seem to occur when doing just about anything with emerge (sync, -S, install). The changelog for r5 indicates `Cache fixes and useful output added.' I find this output annoying rather than useful. If these warning are here to stay, could there at least be a switch to suppress them?
Created attachment 18139 [details, diff] portage Patch Per the referenced forum thread, here is the patch for portage-2.0.49-r5 that solved the problem for me and other users in the thread.
r5 is a debugging version
I guess that's a good reason for the debug messages ;) Still, if it's a debugging version, shouldn't it be hard masked? Ultimately, I suppose that I can live with it as part of being on the bleeding edge that is ~x86...
The ebuild for portage .49-r5 has these keywords KEYWORDS="~alpha ~amd64 ~arm ~hppa ~mips ~ppc ~sparc ~x86 ia64" So yes, it is masked, but not hard masked.
Can we get this masked or a new version out that doesn't have this?
use 2.0.49-r6 :p
*** Bug 36022 has been marked as a duplicate of this bug. ***
