© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@Brian Murray, if you don't mind, I will post my notes here, as comments, so that it will be easier for someone else to follow my thought process on getting familiar with the problem, i.e., getting to better know how does `do-release-
It is very important to know all recent Ubuntu release names (https:/
Ok, so I inspected the `DistUpgrade.cfg` file (https:/
...
108 [Sources]
109 From=impish
110 To=jammy
...
So it represents my most recent update. (I finally did groovy=>impish, and impish=>jammy.) Then, during the next update, it would look like:
...
108 [Sources]
109 From=jammy
110 To=kinetic
...
(see: https:/
I also found the `DistUpgrade.
...
108 [Sources]
109 From=focal
110 To=jammy
...
Interestingly, the `DistUpgrade.
...
108 [Sources]
109 From=focal
110 To=hirsute
...
E.g., it was moved to the trash when the `ubuntu-hirsute` branch was in use on my system, see: https:/
---
@Brian Murray, your other suggestion was to create `demoted.
Maybe part of the simplest solution (for the others to use) is, as you suggest, to create "demoted.
---
Brian Murray wrote:
> "For what its worth I tested an upgrade of a stock Ubuntu 20.10 system to Ubuntu 21.10 by copying DistUpgrade.
It worked because of this piece of code: lines 44 & 45 here: https:/
(
```
if os.path.
maincfg += "." + from_release
```
)
It is not a particularly neat solution, but it will work.
In the ideal world, there would be a mechanism similar to this: https:/
That's it for the analysis. I will try to come up with some solution (in the code) that will support upgrading from at least groovy, if not from any EOL release, to the first available, still supported release (e.g., at the moment, groovy=>impish and hirsute=>impish).