Summary: | Portage can't resolve upgrades if installed package ebuild has been deleted from tree | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tiago Marques <bugs> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | bugs, gentoo, hydrapolic, joakim.tjernlund, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tiago Marques
2023-03-21 09:37:25 UTC
How long since the last update? PYTHON_TARGETS="python3_6 -python3_5 -python3_7" Seems pretty old. This bug feels like one filed out of frustration rather than something specific we can address. Some notes: - Blockers mean the ebuild contains a !x or !!x dependency so collisions are ignored temporarily between them or they cannot be co-installed at all, even temporarily (respectively). You're talking about *conflicts* which are something else. - There was a news item specifically about the libxcrypt migration which made clear people should upgrade, and the news item was published well in advance to give people in a position like yours an opportunity to upgrade ahead of time. We knew it would be one of those awkward transition points which makes it harder (not impossible) to upgrade an older system. - Using existing packages in /var/db/pkg wouldn't help your situation because 'emerge --sync' will have changed the eclasses and such as well. See bug 303403 for something similar to the spirit of your request, though. - Even if it could use a large amount of existing packages, it would take a long time to backtrack so much, and you'd end up with a massive number of skipped upgrades. - Portage isn't always great at actually explaining the issue. Your output is truncated (please don't do that, nor did you include the command used) but often one needs to run something like 'emerge -pev @world --backtrack=0' (only with -p/--pretend) to diagnose issues with an old system to emerge --deselect anything removed. See also bug 257009 and bug 760783. - No emerge --info in this bug. Please provide it. We're happy to work through issues like this on IRC (#gentoo on libera) and I regularly help people to upgrade very old systems indeed. (In reply to Sam James from comment #2) > This bug feels like one filed out of frustration rather than something > specific we can address. > > Some notes: > - Blockers mean the ebuild contains a !x or !!x dependency so collisions are > ignored temporarily between them or they cannot be co-installed at all, even > temporarily (respectively). You're talking about *conflicts* which are > something else. > > - There was a news item specifically about the libxcrypt migration which > made clear people should upgrade, and the news item was published well in > advance to give people in a position like yours an opportunity to upgrade > ahead of time. We knew it would be one of those awkward transition points > which makes it harder (not impossible) to upgrade an older system. > (I would also say that various other news items have mentioned "please do a full upgrade" and the Python news items would also be a good point to actually do such an upgrade...) If you haven't updated, let's say for a year, it may be hard to update. Consider these options: 1) if you don't have that many services, a new installation and migration may be a quicker solution 2) discover the last time you fully updated your system, then update your portage tree to +1year and try to update. Then continue again moving portage +1year until your portage tree is the current one. For very old installations not updated for several years, path 2 can be really time consuming especially if it's a slow machine. Hi all, I apologize for any mistake in the bug reporting, this snippet may not related to the bug reported but another issue with Portage that I had encountered. I have had a recently installed stage 3 Gentoo that, after a month or so, couldn't update due to missing ebuilds. So that is quite frustrating. Would a full emerge output be appropriate or should I also provide details about the ebuilds? This does seem like bug 303403, which will cause rebuilds that I don't think are required. |