release upgrade aborted: failed to fetch apt URIs to fetch #284
Comments
|
It looks like the problem is from the package holds. However, I don't have any of these packages installed. I don't know what is happening. |
|
Did you try again later? It could be a temporary problem and trying a second time works. |
|
I tried multiple times yesterday and today. |
|
Nothing is listed from |
|
There is: And this is the confusion. I did not install any of these packages. I tried unmarking them, but then they get marked again when I attempt an upgrade. |
|
Maybe it'd help if you could provide the list of manually installed packages so we can try to replicate that setup |
|
Some packages are not in official repo, and I have removed a bunch of repos when trying to fix the error: |
|
Any repos I need to add? Or is this good? |
|
I am actually unsure. The Zotero package come from repo of https://github.com/retorquere/zotero-deb. VSCode comes from Microsoft repo. |
|
I'm sure VS Code is fine since I upgraded with that one. |
|
I removed every package marked |
|
Same, tried to update it and it failed to fetch the api URis to fetch Here is my holding packages in case it can help finding which one is causing problem |
|
A system shouldn't be holding |
|
You can wait and see if the next update to pop-upgrade will resolve the issue. I'll move the holding of transitional packages to after the fetch |
|
Maybe that return code 100 is significant? Anyways, this is my cleaned up package list, removing anything not in a repo (still contains PPA, etc): |
|
Quite a few packages. 6 GB download. |
|
Doesn't work, still this error: |
|
Is it possible to see what |
|
If you switch your sources to jammy and try to run that same command after updating the package lists, that should do it. But I haven't made the change to pop-upgrade yet. Waiting for some system-updater changes to get merged first. |
|
Ah, OK, I saw an upgrade and thought it was this. I strongly suggest logging the APT error message, because now it is extremely apparent what happened: Here it is: |
|
I don't know about others' cases, but I removed Looks like it's just a matter of better error messages. |
|
I have this exact same problem, with the same exact packages held (that I don't even have installed). Is the upgrade tool holding those packages as part of the process? Seems a bit odd |
|
The problem isn't the held packages but a dependency conflict. Usually that a specific package needs to have its newer version forced to be installed in advance of the rest of the upgrade. |
|
Yep, I see that now.. here's my issue: |
|
Forgot to follow up. Computer A with 21.10 upgraded fine after conflict resolution. Computer B with 20.04 doesn't seem to hit this error. I would say, just print the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I attempt to upgrade to 22.04, and get this error. The below is the
journalctl -u pop-upgrade.servicelog:The text was updated successfully, but these errors were encountered: