Summary: | Suspicious result of `emerge --sync` | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | pde <pavel.elkind> |
Component: | Misc | Assignee: | Gentoo Security <security> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | dev-portage, infra-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The output of `emerge --sync` |
Description
pde
2012-02-03 23:31:06 UTC
Created attachment 300885 [details]
The output of `emerge --sync`
Please see last 50 lines.
dev-portage, infra, anything to this? Thanks, guys... (In reply to comment #0) > All profiles in the range 2Q-2005 ... 1Q-2012 have been updated. No, not really. A modification to 2Q-2005 will cause portage to process updates for all quarters thereafter, since it's possible for earlier moves to affect the results of later moves. It's been like this for about a year now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d055cc9b6e46f37193841ef89843493e0d61ee7b This behavior is an effect of the fix I applied for bug 401633. The master tree copy was completely redone, thus the file timestamps were updated, so portage ran the updates again. Nothing points to a compromise here. Thanks! |