Summary: | portage 2.2.24: backtrace during emerge --sync (after proper sync, before updates) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas K. Hüttel
2016-01-08 13:29:26 UTC
Just as side note, this is using a "handmade" profile, and one of the atoms in "packages" just got pkgmoved and still needs to be fixed in the profile. Oddity worth noting. https://gitweb.gentoo.org/dev/dilfridge.git/tree/profiles/uni-regensburg OK this may have been related to * a repos.conf file with type "laymansync" * and layman accidentally getting downgraded to stable... Closing as invalid, is gone after updating layman to ~arch *** This bug has been marked as a duplicate of bug 567932 *** |