Prevent do-release-upgrade from disabling 3rd party repos

Sam Varshavchik mrsam at courier-mta.com
Fri Aug 30 11:56:24 UTC 2024


Chris Green writes:

> On Fri, Aug 30, 2024 at 07:35:23AM -0400, Sam Varshavchik wrote:
> > I have a local APT repository with custom packages that I install, it's
> > added to /etc/apt/sources
> >
> > I want to use do-release-upgrade to update jammy to noble.
> >
> > I rebuilt my custom packages for noble, using pbuilder-dist, and installed
> > them in the apt repo, everything should be ready to go.
> >
> > However, no matter what I try, do-release-upgrade wants to disable third
> > party repos:
> >
> > ===============================================================
> > Third party sources disabled
> >
> > Some third party entries in your sources.list were disabled. You can
> > re-enable them after the upgrade with the 'software-properties' tool
> > or your package manager.
> >
> > ===============================================================
> >
> > Things that I have tried, based on Googling around:
> >
> > 1)
> >
> > $ cat /etc/update-manager/release-upgrades.d/mine.cfg
> > [Sources]
> > AllowThirdParty = yes
> >
> > 2)
> >
> > $ do-release-upgrade --allow-third-party
> >
> > Neither one makes any difference. do-release-upgrade still issues a warning
> > that it's going to disable third party sources. How do I do this, for
> > upgrading from jammy to noble?
> >
> Just do the upgrade, then re-enable the 3rd part sources and do 'apt
> update', 'apt upgrade'.

This is not going to work, because I need the local repository pulled into  
the upgrade in order to update the custom packages from jammy to noble, as  
part of the upgrade. Otherwise I believe the upgrade will either fail due to  
unresolved dependencies, or my custom packages will get uninstalled. Or,  
even worse, they'll get replaced by Ubuntu-packaged debs, which will create  
a mess. I need to include my local repo in the upgrade, in order to properly  
update everything.

I can see that at the point where it issues this warning, do-release-upgrade  
already fudged /etc/apt/sources.list, and commented out my entry in  
/etc/apt/sources.list.d, and I am very tempted to manually reenable it.  
However, I'd like to know the right way to do this.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20240830/72b55a93/attachment.sig>


More information about the ubuntu-users mailing list