Summary: | portage-2.0.50 / Emerge -p acting extra verbose the first time it is run on an item | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Urgo <spam> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | trivial | CC: | eric.williams, flash3001, gentoo-bugger, lafou, mentus, mholzer, mkrainer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Urgo
2004-02-08 11:41:08 UTC
Found this on the gentoo-user mailinglist From: "Brett I. Holcomb" <brettholcomb@charter.net> Newsgroups: gmane.linux.gentoo.user Subject: Re: Portage update Date: Sun, 08 Feb 2004 12:55:33 -0500 One system had no problem - I merged portage, then it gave me strange stuff searching and doing a build but then I reran them and it went away. The other system had problems but I ran python-updater and ldconfig (not in that order) and that fixed it. Urgo: That email isn't related. Portage flushed the cache after you upgraded it. If you emerge sync, it shouldn't show any of that info. *** Bug 41221 has been marked as a duplicate of this bug. *** I've just updated portage here and noticed the exact same problem. I just updated portage on two other machines and the same thing happened. Nicholas Jones's suggestion of running emerge sync DOES stop the issue from happening again. Again not a major problem, but just a minor cosmetic issue. *** Bug 41637 has been marked as a duplicate of this bug. *** *** Bug 50191 has been marked as a duplicate of this bug. *** Portage nukes the cache after an upgrade... run emerge --metadata rather then emerge --sync. At the moment, that's how it's implemented and no reason/gain to change it... so closing this as invalid. |