Ubuntu 24.04 (noble) creates an error 404 - Githubissues

fujiapple852 / trippy

A network diagnostic tool

https://trippy.cli.rs

Apache License 2.0

3.8k stars 82 forks source link

Ubuntu 24.04 (noble) creates an error 404 #1308

Closed Imperial929 closed 2 months ago

Imperial929 commented 2 months ago

Describe the bug Ign:5 https://ppa.launchpadcontent.net/fujiapple/trippy/ubuntu noble InRelease Err:6 https://ppa.launchpadcontent.net/fujiapple/trippy/ubuntu noble Release 404 Not Found [IP: 2620:2d:4000:1::81 443] E: The repository 'https://ppa.launchpadcontent.net/fujiapple/trippy/ubuntu noble Release' does not have a Release file.

To Reproduce Install trippy on a fresh Ubuntu 24.04 system

Expected behavior Successfull installation (just as with Ubuntu 22.04 LTS

Environment Info Ubuntu 24.04.01 LTS

fujiapple852 commented 2 months ago

Thank you for flagging this @Imperial929.

At the time of release of Trippy 0.11.0 (11th Aug 2024), the latest Ubuntu LTS was jammy. It seems that since then a newer Ubuntu LTS (noble) has been released so it makes sense to release for that as well.

fujiapple852 commented 2 months ago

I'm having trouble uploading the same version for noble.

TL;DR; when I try to upload Trippy 0.11.0 for noble I get an error that trippy_0.11.0.orig.tar.gz already exists, which is true as the filename does not contain the suffix -ppa1~ubuntu24.04 and so clashes with the prior upload for jammy. I don't know how to convince debuild to use a different name.

Build script is here: https://github.com/fujiapple852/trippy/blob/master/debian/release.sh

fujiapple852 commented 2 months ago

I found this: https://help.launchpad.net/Packaging/UploadErrors

If you did change the version number, this usually happens for re-packaged orig.tar.gz. The Gzip header includes a timestamp, resulting in files with different checksums for each individual compression step. The solution for this problem consists of: downloading the pristine original tarball from the location pointed in the rejection message; regenerate the source upload using it, debuild -S will do it, note that there is no need to include the original tarball in the upload, a reference to the right file will suffice; reupload the just created source package as usual, dput .

fujiapple852 commented 2 months ago

@Imperial929 this is now resolved, Trippy 0.11.0 has been released for Ubuntu 24.04 (noble). This is trippy - 0.11.0-ppa2~ubuntu24.04.

For my own reference, there were two issues:

The original tarball (trippy_0.11.0.orig.tar.gz) is not versioned with the Ubuntu version and so to use it for noble I had to download the exact tarball that was previously uploaded for jammy and use that (see the helpful comment from the launchpad docs immediately above).
The (freshly rebuilt) vendor.tar.zx was no longer compatible with the (old) orig tarball, specifically as the locked version of arrayvec (and likely other) crates was different between the src tarball and the vendored crates and so the build failed. The solution was the similar to the above, download the existing trippy_0.11.0-ppa1~ubuntu24.04.debian.tar.xz file and extract the vendor.tar.zx file and use that to build the package. Note that this required bumping the REVISION to 2 such that we upload trippy_0.11.0-ppa2~ubuntu24.04.debian.tar.xz.

For the 0.12.0 release I will upload for both jammy and noble at the same time and so the issues above should not arise.

Aside: there is an in-flight ITP to package Trippy for upstream Debian, so hopefully PPAs will not be required in the future.

fujiapple852 commented 2 months ago

debian release.sh updated to release to noble, jammy, focal & bionic at the same time.