Bug 62895

Summary:	revdep-rebuild fails because of packages no longer in portage
Product:	Portage Development	Reporter:	crusaderky
Component:	Enhancement/Feature Requests	Assignee:	Portage Tools Team <tools-portage>
Status:	RESOLVED DUPLICATE
Severity:	enhancement	CC:	fuzzyray
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description crusaderky 2004-09-05 02:29:49 UTC

If a package no longer in the portage tree is broken, revdep-rebuild will fail and the user will have to manually fix the problem, either by removing the package from .revdep-rebuild-4 or emerging an updated version of the package.

Suggested attitude:
a)if a different version of such package exists in portage, revdep-rebuild should emerge that one instead (remember to issue a 5 seconds warning and allow the user to disable this behaviour)
b)if such package doesn't exist at all, it should be skipped and a warning should be issued.

Comment 1 Paul Varner (RETIRED) gentoo-dev

2004-09-14 11:06:41 UTC

revdep-rebuild already supports this behavior.  If you run 'revdep-rebuild -X' it will use the name of the package and will emerge the latest version available according to your ACCEPT_KEYWORDS variable.

Comment 2 Matthias Liertzer 2004-09-25 07:18:20 UTC

sry, I saw the "bug depends on 62644" just right after I clicked on the commit button

Yours Matt

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2005-12-03 07:46:33 UTC


*** This bug has been marked as a duplicate of 22161 ***