"No Release file" from do-release-upgrade with an aptly repo

[Sam Varshavchik]

Liam Proven writes:

> There is a phrase for this sort of question on Stack Overflow, but I
> can't offhand remember it. It comes with a warning: work out what the
> asker is really trying to achieve, rather than just answering their
> question, because askers often get in a mess because they are doing
> something that they shouldn't really do.

I'm very familiar with Stackoverflow's culture. This was true some time ago,  
but these days the dominant Stackoverflow mindset is something else; but  
I'll leave that for another day.


> You said in your first message you recompile code, build your own
> packages, and install them.
>
> Why?

Two reasons: some of them are not packaged at all, and those that are set up  
with notable deviations from upstream packaging. In both cases I'm of the  
mind that using a distribution's native package manager is better than  
running "make install", crossing one's fingers, and hoping that nothing gets  
bricked.

But set aside the underlying reasons. The question to answer here: should or  
shouldn't there be a way to add a custom third party repo and have it  
smoothly integrated with the default distribution repos and without having  
to constantly fight with the package manager.

If you're saying: no, stick with the default repositories and whatever's in  
there. But I must note the wide availability of third part repositories for  
Ubuntu, both free software and commercial software, especially for LTS  
releases.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20220816/809c3450/attachment.sig>