Where can I see the list of things that are deprecated or removed in each release, Lubuntu in particular?
1 Like
Are you attempting to create a historical list, by release, over time?
No
Iām wanting to move up to the 24.04.4 when it is released as Iām still on 22.04.
The Lubuntu team have historically notified users of changes that will occur on their discourse; with that gone, that will likely occur here instead (Iām not aware of any, so canāt provide example). Beyond notices of change, release notes (inc. beta) have often repeated that detail, though these notices tend to focus on packages/apps on the install media itself.
Most packages in Ubuntu repositories are imported from upstream Debian, so removal is often arranged to impact both at the same time, eg. Qt4 was discussed here from to it happening, with the same with Qt5 also found here. These toolkit changes [indirectly/directly] relate/refer to everything that uses them, though normally no list of impacted packages is provided; notifications are given allowing maintainers, or end-users of packages/apps using that toolkit to have time to consider moving if their app isnāt being ported to the newer library/toolkit. These notices often can change over time, as they allow maintainers/teams impacted to comment & reach out, thus timing can be adjusted where required, and anyone whoāll be impacted should continue to watch for changes.
I get most notices via email though, on watched packages list either on upstream Debian packages, or their Ubuntu equivalences. These notices are package based though.
I also see bug reports on packages (the final thing youāll see when a package disappears!), most of these also hitting my inbox (email). Again these are package specific, and not lists. A number of websites can be useful (https://tracker.debian.org/ etc) but theyāre not usually providing lists except relating to a specific package youāre wanting details on.
Uh oh
Does that mean that changelog from release to release will no longer be posted with the respective distro?
Iām not sure what youāre referring to with the ādoes that meanā, but I see no actual change, except that Lubuntu isnāt using its own discourse, and unfortunately some historical data (pre-2025) that was posted on that site is no longer accessible publicly, unless blogged officially (which is where youāll find our/Lubuntuās most important announcements anyway!).
somewhere I read that Muon Package Manager was removed from 24.04 LTS.
It was in a list of things that will no longer be in Lubuntu. Most everyone used Muon before 24.04 and with 24.04, we installed Synaptic due to Muon backing out of being used.
Iām talking about that list of things.
The list was included with every release until apparently just recently.
Iām not sure what ālistā youāre referring to.
guiverc@d7050-next:/de2900/lubuntu_64$ grep muon mantic-desktop-amd64.manifest
muon 4:5.8.0-2ubuntu1
We included muon in mantic for example; the release notes being available at https://lubuntu.me/mantic-released/ ; which is a release where that package was included.
The comparative announcement for 24.04 or noble can be read at https://lubuntu.me/noble-released/ ; no mention of it there.
I usually posted almost the same text of that official announcement on Lubuntuās discourse, with the bulk of the text just copy/pasted from our team notepad, and whilst I did on occasion add a little extra detail of what interested me or others (but wasnāt seen as āworthā being in official release announcement) as well, but most of that detail was just put in general discourse posts and referenced in the announcement post on discourse. Any future equivalent posts of that extra detail will now be published on this discourse.
For muon specifically, my prior response maybe useful, ie. https://tracker.debian.org/pkg/muon will tell anyone when it was removed from upstream Debian sid or testing, which is a huge clue thatāll disappear in Ubuntu. Launchpad can give some details, ie. https://launchpad.net/muon/+packages though detail of the actual removal of the package from the seed is at https://git.lubuntu.me/Lubuntu/seed/commit/2cb1140dab8674ec7f790affc367f99d2ca0524e
Team discussions used to frequently be on IRC, but now theyāre mostly on Matrix; but no lists there either. I do recall discussion on muon, but I canāt recall any ālistā like what you remember sorry.
Not sure if this will help you in your quest.
Take a look at this. The paragraph at the top will explain what the cloud image is. I donāt know if there is anything similar for Lubuntu Desktop. Maybe somebody else can come along and refine this for Lubuntu.
You should be able to use something similar to the following.
So ā¦ get the cloud image manifest for Jammy server and save it:
wget https://cloud-images.ubuntu.com/jammy/20251111/jammy-server-cloudimg-amd64-azure.vhd.manifest -O cldimg1.txt
Then do the same for Noble:
wget https://cloud-images.ubuntu.com/noble/20251026/noble-server-cloudimg-amd64-azure.vhd.manifest -O cldimg2.txt
Then, you can use diff to check for differences. Honestly, Iām not sure if you will be able to spot obsoletes and removed packages easily.
diff cldimg1.txt cldimg2.txt
One might be able to spin this idea into a script, but I havenāt time right now to work on that.
Edit:
Found the Lubuntu manifest for Noble. Havenāt found Jammy.
https://cdimage.ubuntu.com/lubuntu/releases/jammy/release/lubuntu-22.04.5-desktop-amd64.manifest
And the one you linked for Noble is wrong as thatās the daily image. You want:
https://cdimage.ubuntu.com/lubuntu/releases/noble/release/lubuntu-24.04.3-desktop-amd64.manifest
Thank you! Senior moment. I knew it was there. Sigh.
Still, the Noble daily might show differences that the user might eventually get on updating. Unless, of course, the daily doesnāt have the pending point release. I believe the user specified 24.04.4 when it is available.
I would not rely on the dailies for the āchangesā. The stable release is unlikely to have changes that are that significant between point releases, and to my knowledge the dailies arenāt always running for the stable releases. Thus for 24.04 you should stick to the stable release ISO and manifests, not dailies.
I will defer to the view from your side of the window. However, I think you may have made a pretty good case for suggesting that the user wait until 24.04.4 is released, then do the check ā the results would certainly be less ambiguous. When satisfied, then move to the new point release.
Iām regularly comparing manifest files myself; in fact my zsync scripts which update a daily ISO include a diff of the newly updated manifest file with the manifest Iād last used, with certain files highlighted if theyāre changed (part of our (Lubuntu) prior QA regime when we used our own checklist on Lubuntu Discourse).
The manifest file contains package versions, and whilst this detail can be super handy, it also adds noise if you only want to detect package changes, thus Iād consider seed files as an option
The seed files (Index of /seeds) contain the ~formula or tell the builder software what to put on the ISO for all Ubuntu ISOs, and that includes flavors like Lubuntu. If I was contrasting Lubuntu jammy with noble Iād thus maybe contrast
- https://ubuntu-archive-team.ubuntu.com/seeds/lubuntu.noble/desktop
- https://ubuntu-archive-team.ubuntu.com/seeds/lubuntu.jammy/desktop
though theyāre only a single file, and wonāt give a complete picture; but I still find that useful. The seed file structure can be easily explored with a web browser, and itās really only showing the same detail as the manifest files in a different way (ie. seed file is used to create the ISO, the manifest file shows result of that build including package versions; version detail is not [for debs] included in seed files as itāll grab the latest available [in archive] when not specified)
Speaking of 24.04.4, when is it due to be available?
Read the release schedule
12 February 2026 as its listed today, but installed systems get those updates before the ISO release date, which is what 12-Feb-2026 represents.
eg.
its been visible for some number of days
linux-image-generic-hwe-24.04-edge | 6.17.0-9.9~24.04.2 | noble-proposed | amd64, arm64, armhf, ppc64el, s390x
linux-image-generic-hwe-24.04 | 6.17.0-9.9~24.04.2 | noble-proposed | amd64, arm64, armhf, ppc64el, s390x
or the HWE kernel for Ubuntu 24.04.4
What are the projected general differences between 24.04.4 and 24.04.5
- theyāre both Ubuntu 24.04 LTS systems, so essentially the same
- Ubuntu 24.04.5 will have more updates/fixes applied than a 24.04.4 system
- if using the GA kernel, the kernel will be identical (excluding updates/security fixes as covered in prior point); however if using HWE the 24.04.4 will be using 6.17 where as the HWE kernel for 24.04.5 is expected to be 6.20.
The point release number (ie. .4 or .5) is just an normal package update of base-files, the current noble or 24.04 changelog can be seen at https://changelogs.ubuntu.com/changelogs/pool/main/b/base-files/base-files_13ubuntu10.3/changelog
If not obvious, 24.04.5 is still in the future, which is why I added the word āexpectedā, as the 6.20 kernel is what is expected, but that may change. The kernel used will be the GA kernel stack back-ported from Ubuntu 26.04 LTS.
1 Like
How may we upgrade the LiveUSB from 24.04.3 to 24.04.4 without going through the whole full download time?
I guess itās called an āin-place Live upgradeāā¦please correct.
An in-place upgrade refers to an installed system only as far as Iām aware, a live system is just re-written and not upgraded; as itās almost always a READ ONLY image which is intentional by design (an ISO) preventing corruption etc.
You could have a live system with persistence; which still doesnāt actually change the live system if I understand it correctly; the updates exist on a later partition (the persistence part) and thru linked list type of structure theyāre used instead of the older (non-updated) program found on the initial live system. Whilst this is useful for a small number of updates, itās not ideal for many, and Iād personally just re-create live system with persistence.
In the past (years ago now) I used to run installed systems from thumb-drive; as Iād carry the USB thumb-drive with me to family, or other work sites, and perform updates there (where theyād be done normally; just written to the thumb-drive), but I stopped doing that when I started Quality Assurance testing for Ubuntu, and used live ISOs instead, and that was back in 2018.
Personally I use zsync to update an ISO, so only differences are downloaded, rather than the whole ISO. If I want to reduce bandwidth required; I guess the closest ISO I have to what I really want, then use it as my starting pointā¦ Lots more CPU will be used as it needs to calculate the diff which needs to be downloaded, but actual download is only the difference. You could (Iāve done it) try multiple ISOs and work out which is closest, and whilst it does save bandwidth, it takes me more time, so Iāve not done that in years either. The last updated ISO only had 1.3% of ISO size downloaded for me; after download I just re-write the ISO to thumb-drive.
FYI: The commands that actually do the download or really update my daily ISO for noble are
wget https://cdimage.ubuntu.com/lubuntu/noble/daily-live/current/noble-desktop-amd64.manifest
wget https://cdimage.ubuntu.com/lubuntu/noble/daily-live/current/noble-desktop-amd64.iso.zsync
zsync -u http://cdimage.ubuntu.com/lubuntu/noble/daily-live/current/noble-desktop-amd64.iso noble-desktop-amd64.iso.zsync
(the manifest isnāt required, but I always get that at the same time & didnāt remove it; the filenames and URLs are what I use given Iām downloading daily ISOs and not a released final ISO; adjust them for the ISO you want)
Those commands (taken from a script I run) will update my current noble daily, then a number of diffs are run & results shown telling me differences & moreā¦ If I want to write it, I actually run another script that does thatā¦ I have a push script if I want to write it to a Ventoy thumb-drive, OR I use a mkusb-nox command which overwrites the thumb-drive with the new ISO.
2 Likes