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

[Sam Varshavchik]

Tommy Trussell writes:

> I still think you might do best starting with the process for installing your  
> software on a pristine Ubuntu system from scratch, and build your upgrade  
> procedure from there. Hopefully that would be less brittle than do-release- 
> upgrade, which of course does all sorts of funky stuff while it's running so  
> that it can "change the tires on a moving car."

It's my understanding that do-release-ugprade is the established mechanism  
for updating an existing Ubuntu system to a new release, no?

I don't quite follow – I think you're suggesting using a separate system to  
build packages on the new release, and then bringing them over to a  
repository that gets fed into do-release-upgrade.

Using a separate system to build packages on a new release is certainly a  
viable possibility. However, it's also true that pbuilder exists precisely  
for the reason of not needing to do that. Instead pbuilder prepares a chroot  
with the new distribution for building the software packages on it. And  
that's exactly what you get with pbuilder: an image containing a pristine  
Ubuntu release.

pbuilder definitely works, and my issue was not with pbuilder, but with do- 
release-upgrade's limitation of not being able to digest file: URLs, and its  
confusing failure. Once my foggy brain cells recalled this limitation, this  
showstopper was gone…


-------------- 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/195952f3/attachment.sig>