Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 17867 - portage upgrade deadlock
Summary: portage upgrade deadlock
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Nicholas Jones (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-20 06:00 UTC by Toby Dickenson
Modified: 2003-04-28 05:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toby Dickenson 2003-03-20 06:00:51 UTC
I have some systems that hadnt been updated since the end of last year. Updating 
from portage 2.0.43 leads to a deadlock: 
1. portage 2.0.47 depends on app-shells/bash 
2. my machines have sys-apps/bash installed, but not app-shell/bash 
3. the ebuild for app-shell/bash uses the epatch function, not present in the older 
portage. 
 
Breaking the deadlock in this case is easy, but I think it demonstrates a more general 
problem. 
 
I believe gentoo should make a promise that it is always possible to emerge the 
current development tools using tools that were emerged in the previous x months.  
I'm not sure what x should be, but I had expected it to be longer than 5.
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-03-23 16:00:21 UTC
since 2.0.47 portage has autonotification if a new stable version is available

could we close this ?
Comment 2 Nicholas Jones (RETIRED) gentoo-dev 2003-04-28 05:44:37 UTC
It's is workable. You just have to use a rescue tarball if you drift too far
behind.