=== chris14_ is now known as chris14 [07:15] Don't want to be too annoying, but is this removal of some of the 5.15 / 5.19 kernel packages from the archive a normal situation ? [07:23] caribou: what packages, do you mean old ones that have been superseded? [07:23] caribou: we don't remove packages from the archive. /me thinks. [07:23] yes, some of them but not all [07:24] This is one example of them : linux-image-5.15.0-52-generic [07:25] Yeah, superseded, we're in -71- now [07:26] should still be in the archive though [07:26] here is a listing : https://paste.ubuntu.com/p/CNmXJHsW29/ [07:26] But how come old versions disappeared from the archive? [07:26] Then apt update would need a lot more data, if all the versions of all the packages were being kept ... [07:26] that's our question : for some reason one kernel version was pinned for installation and now the install fails since it is no longer there [07:26] And mirrors too [07:27] AFAIK the original kernel is kept, from the installation media, and the two last ones [07:27] When du the purges occur? [07:28] Kernels are different. A new kernel version is a new package (not just a new version of an existing package). So should always be in the archive. [07:29] For the 5.19 in Jammy, only the last one has been kept for example, so this does not seem to comply with this policy. [07:29] Well, apt install linux-image-5.15.0- and tab-tab, shows only 25 and 71 available (25 is the original one from the installation media) [07:30] alkisg: the current situation is a change from what is always been the case : all kernel packages were present in the archive [07:31] you could pretty well need to go back to an old kernel package + dbgsym for crash dump analysis for instance [07:31] caribou: I'm just a long time user so my opinion isn't too important. But I've never seen more than 2-3 versions of the same kernel in the archive in the last 10 years. [07:31] caribou: in these cases, I had to download it from launchpad, where they are kept [07:32] yes but right now there not even on launchpad : https://packages.ubuntu.com/jammy/linux-image-5.15.0-52-generic [07:32] does 404 [07:32] They're in the build history [07:32] Your link there is the archive, not the launchpad build [07:32] hrm [07:32] juergh@gollum:~$ curl -s http://archive.ubuntu.com/ubuntu/pool/main/l/linux/ | grep linux-image-unsigned-5.4.0-[0-9]*-generic | wc -l... (full message at ) [07:33] caribou: here's a link to get you started: https://launchpad.net/ubuntu/+source/linux/+publishinghistory [07:34] From there you'll end up in the .debs [07:34] So when I needed to pin an older kernel, I always used the "installation media" one [07:34] That's available via apt, instead of searching launchpad and using wget [07:50] This is still a sudden deviation from what it used to be [08:02] As of march 1st, for example, there was still 20 releases of the 5.15.0 kernel available from the Jammy repositories, including the original -25, going from -27 through -60. So there must have been either a deletion mistake or a deliberate purge. Whatever it is, there must be some kind of explanation somewhere. [08:05] ultratox: I've never seen that, I believe you somehow remember wrong [08:11] alkisg: Try this command on an up-to-date Bionic, Focal and Jammy --> apt-cache search linux-image | grep -E '^linux-image-[0-9].*-generic' | sort -t. -nk2 [08:12] ultratox: I think you're right, I think I was confused with the result of `apt policy linux-generic`, which only lists the last and the original version [08:13] And the commands that juergh has posted also verify what you're saying [08:13] (i.e. I was pinning linux-generic instead of individual kernel packages) [08:26] So, is this possible that there was a mistake? Any reversion possible? [09:32] Hi, does anybody know why all but the latest kernel versions for Jammy, has gone missing from the jammy-updates repo and is now only in proposed ?. This happened on Tuesday morning (UTC) [09:34] soeby: have a look at the logs, we discussed it a few minutes ago : https://irclogs.ubuntu.com/2023/05/11/%23ubuntu-kernel.html [09:35] soeby: We happen to be talking about this [09:35] sorry - I just joined the sorry :-) [09:35] Good thing you add your voice to this cry for help ;-) [09:57] On May 8th, we had 23 kernels (-27 through to -71) in the updates repo. On May 9th, only one (-71) was available. [09:59] 5.15 series ^^ [09:59] Have you got any log regarding the 5.19? [10:03] @ultravox - yes, apparently the versions from 5.19.0-28 to -40 went missing on the 10th, so a bit later... [10:04] read ubuntu-release@, it was announced in late april that obsolete kernel abi versions are getting cleaned now [10:05] https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005625.html [10:12] @tjaalton - so the resolution for installing an older (possibly working) kernel is to enable the proposed repo ? [10:12] no [10:13] you install the metapackage [10:13] ...but I do not *want* the latest kernel [10:14] then you keep your own mirror [10:14] and don't remove stuff [10:16] if proposed still has them, I think it's an oversight [10:19] The .deb packages are still there - so the size of mirrors are the same... only what is included in -security and -updates definitions are changing. [10:20] For the record, I believe it's always possible to get package from LP: https://launchpad.net/ubuntu/+archive/primary/+files/. For example: https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-5.15.0-30-generic_5.15.0-30.31_arm64.deb [10:21] anyway, it's pointless to complain about it here, use the mailing list [10:22] or discourse, since it's the Future [10:22] @tjaalton - I will... [11:50] thanks for the clarification tjaalton