Could not calculate the upgrade
Page 1 of 1 (13 posts)
Tags:
None
Registered Member 
|
I tried to upgrade KDE Neon from 18.04 to 20.04 however i get the message:
Could not calculate the upgrade An unresolved problem occurred while calculating the upgrade. This was likely caused by: * Unoffical software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log' So what can I do here to solve the issue? I uploaded thain main.log and apt.log here: https://file.io/iomndl9N3kgC https://file.io/iomndl9N3kgC |
|
Registered Member
|
Don't know the solution, but I have the very same problem.
I tried to move all custom files in `/etc/apt/sources.list.d/` out of the way, but that did not help. |
|
Registered Member
|
When I check the main.log at the bottom it says:
However when I check for held or broken packages I cannot find any. How to find out which packages could be problematic and need to be disabled? |
|
Registered Member
|
My log has > 2500 lines, including some about neon-desktop as well:
And at the very bottom it says:
|
Registered Member 
|
Use ppa-purge (or add-apt-repository -r) as described, which both removes a PPA, but more importantly, downgrades any packages from that PPA back to stock versions.
Simply deleting PPA info from /etc/apt/sources.list.d does not do anything about the packages installed on the system, which are what is causing the conflicts. https://www.omgubuntu.co.uk/2019/12/how ... ppa-ubuntu Read thee page, and use the section using the ppa-purge command. You probably have to install this. I suggest starting with any PPA used for drivers and the like, like oibaf and others that upgrade Mesa and other system level items. PPAs for single, simple applications are less likely to be the cause here. If you have removed files from sources.list.d, either put them back, or re-add the PPA, then remove it as described. EDIT: note that using add-apt-repository -r does NOT downgrade packages,.
Last edited by claydoh on Tue Aug 11, 2020 7:54 pm, edited 1 time in total.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
|
Registered Member
|
But how can I find out which PPAs are not the default ones?
My source list.txt looks like this:
|
|
Registered Member
|
PPAs are explicitly added by the user, and not found in the sources.list file. They are normally added via the add-apt-repository command. PPAs are soecifically hosted on Ubuntu's launchpad, Any other repo added by the user is NOT a PPA In your sources.list file , anything with a '#' is ignored. Anything that does not contain 'ubuntu.com' or 'canonical.com' was added by you. I do not see anything there that might cause a problem, though that codelite.org line is old and meant for Ubuntu 17.10 Artful, and Neon never used that version ever, so it probabky needs to be removed. The Winehq related lines (without the '#') should be OK, and the other winehq lines with the '#" can be removed. Now as to PPAs, the files that have the repo info for those are in /etc/apt/sources.list.d. Neon's specific repo file is in there as well. You need to determine what PPAs you added and find out the PPA url for them. Probably the same place you found the info to add it originally. Thgen follow instructions in my url above, using ppa-purge.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
|
Registered Member
|
Thanks for the explanation. The problem is I cannot remember exactly anymore when I added what.
The source list-d contains this:
I assume I have to kick out everything here with purge which has bionic in the name because I upgrade to focal? Also I wonder if the apt.log file can give additional information what is wrong. there I have many entries with python. Truth is a installed a newer python version in parallel but I linked the system back to the default python version
|
|
Registered Member
|
I purged the deadsnake python ppa and then I could run the upgrade.
However now it looks like I have 7 broken packages. How can I solve that?
|
|
Registered Member
|
I deleted the hold back packages. So far everything looks fine.
However when I tryed to reinstall clang with
I get this error:
How can I solve this issue? |
|
Registered Member
|
I have the same problem ...
All my custom sources are commented out in /etc/apt/sources.list.d/*.list files
in main.log I only found this
Any help on how to upgrade is appreciated I have event commented out ALL source in .list files. Still same error:
Regards Armando |
Registered Member
|
I am like you, I had the same issue and reading claydoh's reply was very helpful at getting me going down the right path. Like you, I had a bunch of PPA's that, like claydoh mentioned, got their fingers deep into the system. I looked through my list of files in /etc/apt/sources.list.d and just started to do some Googling to figure out the original name of the PPA so I could run it through ppa-purge. I wound up doing this:
The last line was because I noticed that jackd and libomp5 were causing problems when I looked in the syslog. Looking in /var/log/dist-upgrade/main.log was useless for telling me which files were tripping up the upgrade process.
Glancing through your PPA list, the ones that I'd try to ppa-purge would be these: graphics-drivers-ubuntu-ppa-bionic.list jonathonf-ubuntu-ffmpeg-4-bionic.list yannubuntu-ubuntu-boot-repair-bionic.list Again, you'll have to do a Google on each of them to figure out the exact "ppa:/owner/ppaname" . |
|
Registered Member
|
Sounds like you're close! I'd just do a simple:
and then try the upgrade again. |
Page 1 of 1 (13 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]
