Summary: | sys-apps/portage-2.1.12.13: pulling unnecessary dependencies during oneshot upgrade | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paul Slinski <deviantgeek> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | dschridde+gentoobugs, esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300071 | ||
Attachments: | fix --backtrack=0 to work properly (see issue in comment #3) |
Description
Paul Slinski
2013-08-07 18:54:47 UTC
Apologies for the ugly cut/paste. Here's a pastebin of that emerge output: http://pastebin.com/ZnYSNXBh The issue is that it pulls in rebuilds for broken slot-operator dependencies. You can avoid that by adding --backtrack=0 to your options like this: emerge --oneshot --backtrack=0 portage Unfortunately, that results in nothing happening. (In reply to Paul Slinski from comment #3) > Unfortunately, that results in nothing happening. Please attach a debug log created as follows: emerge --oneshot --backtrack=0 portage --debug 2>&1 >debug.log xz -9 debug.log (In reply to Zac Medico from comment #4) > (In reply to Paul Slinski from comment #3) > > Unfortunately, that results in nothing happening. > > Please attach a debug log created as follows: > > emerge --oneshot --backtrack=0 portage --debug 2>&1 >debug.log > xz -9 debug.log Nevermind, since I see that you have portage-2.1.12.13 installed, you need this patch: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c6679936d162f35a330ce541ec4cd0567ccf76d8 Created attachment 355368 [details, diff] fix --backtrack=0 to work properly (see issue in comment #3) Save as /tmp/backtrack_0.patch and apply as follows: patch /usr/lib/portage/pym/_emerge/depgraph.py /tmp/backtrack_0.patch Thanks, that did it. Now I can move on to scratching my head with the other issues. Zac, is this problem still an issue? Or can we close it? |