-
Notifications
You must be signed in to change notification settings - Fork 100
WIP: update to Ubuntu 20.04 #42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Most of those packages have a version number in them: we "just" need to find the newer version of them and install those. |
Okay I have an idea for this. Let me try writing a small script that does it. |
Okay here's what my script came up with: These are the replacement packages:
These packages doesn't have any replacement and requires further investigation:
Again, this is a basic script that I wrote to check for replacements. This is in noway accurate, and needs manual inspection, but it eases the burden on us. Also, @jyn514 I would've loved to contribute, but I don't have write access to your repo, so I'm commenting it here. |
Okay update: I'm gonna try building the image based on further manual inspection of those missing packages. Will keep you updated on my progress |
Okay yeah, that seems to work. Only 3 packages are now not found. I've narrowed it down to this:
I'm not really sure what these packages are, so I'll need help finding replacements. The new packages.txt file is here:
Also, sorry for the spam, I'm just super excited about this is all 😅 |
Thanks so much for working on this! If you like you can fork my repo and make a PR of your own and we can work from there instead. That would make it easier to read the packages as well since I'd only have to look at the diff.
I'm not sure either ...
|
elektra seems to have been removed altogether from 20.04: https://repology.org/project/elektra/versions. I ran
|
@PhilippGackstatter do you have any idea why libelektra was removed? Are you interested in adding to the 20.04 release? If not I'm not sure there's a clear path forward here ... |
Thanks for bringing this to my attention. I'll check with the project's maintainers about the 20.04 situation and get back to you. One question: If we are unable to add it to 20.04, the existing documentation wouldn't get lost, it's just that when I publish a new crate, the docs wouldn't build, is that correct? |
That's correct. |
Note that we always redirect |
@rakshith-ravi some of these changes look a little odd. This is the diff I see:
In particular, there are packages added that weren't there before:
Additionally, you've removed several packages that are present in 20.04:
Can you explain how you came up with the new versions that you posted? |
@jyn514 the script I wrote basically did the same thing I was doing manually: type the first few characters on a terminal and use tab-completion to find the actual package name. Naturally the script fell short in a lot of areas, but it gives us a good estimate. However, in the specific case of |
Closing in favor of #43 |
This doesn't pass, apparently 20.04 got rid of a bunch of packages. We'll have to make a policy decision about whether we should get rid of outdated ones/look for a new version.
Missing packages:
Generated by copy pasting the errors from apt, then
"s/^E: Unable to locate package // ; s/E: Couldn't find any package by glob //; s/E: Couldn't find any package by regex //; s/E: Package '\([^']*\)' has no installation candidate/\1/" | tr -d "'" | sort -u
.