Problem Description:
I’m kind at a loss when upgrading ubuntu I always used to do clean installs of ubuntu and this problem never occurred.
So the issue is how do you deal with thired party software sources.
The documentation says :
Understand Third-party repositories: Third-party software repositories and Personal Package Archives (PPAs) are disabled during the release upgrade. While software installed from these sources will not be removed, it’s the most common cause of upgrade issues. Be prepared to re-enable them or find updated versions after the upgrade.
When installing wine i remember i selected Plucky Puffin version of source, so does this means after upgrading to 25.10 I can simply re check software software & updates and i will properly get wine upgrade (when they will add support to 25.10) or i need to purge everything including wine software source and re add everything from 0 point.
Should i just add new ( Questing Quokka) ppa’s / sources and delete the (Plucky Puffin) source entries and everything will work just fine ?
I’m asking this because after upgrading from 24.10 to 24.04, just checking mesa ppa or chrome source didn’t work last time i simply re checked i had to remove everything and than re enable (Had ton of problems with getting chrome updates working after deleting it from sources (after installing .deb file it wouldn’t create software source)).
So what is your recommendation and correct way to deal with thrid party sources after upgrading the ubuntu version.
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
No active apt repos in: /etc/apt/sources.list.d/kisak-ubuntu-kisak-mesa-oracular.sources
Active apt repos in: /etc/apt/sources.list.d/kisak-ubuntu-kisak-mesa-plucky.sources
1: deb https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu/ plucky main
No active apt repos in: /etc/apt/sources.list.d/mkusb-ubuntu-ppa-plucky.sources
No active apt repos in: /etc/apt/sources.list.d/obsproject-ubuntu-obs-studio-plucky.sources
Active apt repos in: /etc/apt/sources.list.d/ubuntu.sources
1: deb http://archive.ubuntu.com/ubuntu plucky plucky-updates plucky-backports main restricted universe multiverse
2: deb http://security.ubuntu.com/ubuntu/ plucky-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/winehq-plucky.sources
1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu plucky main
I should point out that i haven’t upgraded yet to 25.10 and previous upgrade was done from 24.10 to 25.04 by purging everything.
About obs and mkusb i clearly remember removing those from software & updates gui however it wasn’t reflected in software sources file (something i encountered on chrome source before i manually removed it from sources file(I pressed modernize sources it screwed up google updates had to delete it and then re install it to get updates working))
I’m writing this because i’m interested in best practices and how people deal with this because i couldn’t find any information online and new users might find this problematic.
I can do a upgrade but i know mesa ppa doesn’t have a 25.10 files nor wine but if you are interested what will happen i can do an upgrade in few hours.
Yes it gets disabled automatically but what is the best practice. That is what i’m interested in.
Before upgrade i can remove/purge every additional sources software (However this doesn’t sounds like a good option in modern day and age) I know this works but re downloading software isn’t the best option.
I can do an upgrade and than add new sources from software, for example (sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/plucky/winehq-**Quokka**.sources
And then remove the old source (sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/plucky/winehq-plucky.sources) However as discovered software & updates gui doesn’t works (doesn’t removes the sources fully)
And i’m not sure if this works or not.
I kinda noticed just re enabling sources doesn’t work this happened
Mesa ppa worked up until the maintainer supported 24.10 files after that it stooped upgrading so what i want to point out it automatically didn’t change to 25.04 channel so i had to purge mesa ppa and than re add it and it added the 25.04 source of ppa.
Maybe i had to tweak the source entry to reflect moving to 25.04 however i couldn’t find an option to do this or what file i had to change. So i purged the ppa and than re added it.
overall what is the best practice with dealing with third party sources ??
Repos:
No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/google-chrome.sources
No active apt repos in: /etc/apt/sources.list.d/kisak-ubuntu-kisak-mesa-oracular.sources
No active apt repos in: /etc/apt/sources.list.d/kisak-ubuntu-kisak-mesa-plucky.sources
Active apt repos in: /etc/apt/sources.list.d/ubuntu.sources
1: deb http://archive.ubuntu.com/ubuntu questing questing-updates questing-backports main restricted universe multiverse
2: deb http://security.ubuntu.com/ubuntu/ questing-security main restricted universe multiverse
No active apt repos in: /etc/apt/sources.list.d/winehq-plucky.sources
As you can see the wine and mesa ppa is still set to plucky
just checking google source game me this message but most probably it’s changed text for modernizing source stuff
Notice: Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘https://dl.google.com/linux/chrome/deb stable InRelease’ doesn’t support architecture ‘i386’
The new fonts are terrible though making my eyes bleed what was changed in 25.10 ??
Hi levin,
It is important check the ppa host page at upgrade time. There can sometimes be a ppa update delay when a new Ubuntu version is released. This depends on how well the ppa is maintained . Some ppas only update for LTS versions of Ubuntu because that is what the maintainer uses. Unfortunately sometimes purging and reinstalling are required.
Best practice is to restore your Ubuntu system to as close to stock condition as possible before a release-upgrade. In other words, as close to the tested state as you can.
Like painting a room, most of the time and effort is spent preparing and organizing.
Backup your data. Create a LiveUSB installer.
These are precautionary. It’s rare for something to go terribly wrong. But if it does, these two actions will reduce a catastrophe to a mere annoyance. Your system will be bootable and your data will be safe regardless of anything else that might happen.
Uninstall all non-Ubuntu deb-packaged software, and disable/delete the sources that provided that software.
Non-deb software (Snaps, AppImages, Flatpaks, tarballs, etc.) don’t need to be removed.
Deb-packaged software that came from the official Ubuntu repositories don’t need to be removed.
Deb-packaged software that didn’t come from the official Ubuntu repositories does need to be uninstalled. And remember to disable/delete those non-Ubuntu sources.
Most PPAs are not official, and while they are less likely to cause problems, most should still be removed.
This may seem excessive at first glance, but Ubuntu support sites are knee-deep in the tears of folks whose third-party software broke release-upgrades. Wine and VirtualBox upstream packages are commonly used…and are also notorious for breaking release-upgrades. If there is any doubt, remove it. It’s easy enough to reinstall later.
Run apt update. Check that only Ubuntu sources are hit. Ensure that the required main (noble), updates (noble-updates), and security (noble-security) repos are present.
Run apt upgrade. Fix all warnings and errors before proceeding.
Run the release-upgrade
Review the non-Ubuntu software that you want to re-install. Maybe you don’t use it anymore. Maybe the feature or version you want is now in the Ubuntu repos. Maybe a good alternative is in the Ubuntu repos. Maybe the developer prefers to distribute via Snap or AppImage or Flatpak now. Maybe the non-Ubuntu software isn’t available (yet) for the new release.
Reinstall the non-Ubuntu deb sources and software that survived the review. After each new source, run apt update and apt upgrade . Read each output carefully to ensure that only what you want is being installed, nothing removed, and no system libraries replaced by different versions.
unless you have backups and want to test this anyway.