What's happening in Noble repositories?

42

This is probably not the place for this discussion BUT the dev branch of noble actually seems pretty stable to me - as a newbie who ignorantly upgraded his PC’s stable Ubuntu 22.04 LTS to 24.04 dev branch. Claiming this because I’ve ran a number of "apt upgrade"s until this point.

[Back-story: I was way too careless and didn’t bother to check what the -d flag does in do-release-upgrade. Though I don’t know why trying do-release-upgrade alone - initially - didn’t show me the option to upgrade to 23.10. Anyways, I basically got tired and blindly followed an online instruction just for the thrill of upgrading.]

Note that I already had a bunch of stuff pre-installed from jammy and after software-properties-gtk was fixed, I’m still using repos meant for jammy to keep my Brave, OBS, MikTeX and FSearch up to date. I don’t really know how secure that is but I’ve already done it. I guess I can’t complain now. Constructive advice is welcome. Thank you for your time and patience.

43

Now things are back to a roughly normal state.
We maybe could close this thread?

44

Bring on the new builds. Delighted to see the daily builds back up and updated. I can resist anything but temptation. Let’s give it a spin.

45

With the arrival of the new ISO I think it can be closed.
I installed the new ISO on 2 PC and it seems working well.

2 Likes
46

I noticed that several amd64 packages were migrated to t64, among others libgtk-3-0 (which is now libgtk-3-0t64: Ubuntu – Details of package libgtk-3-0t64 in noble)

Why is that necessary (or was it a mistake)? amd64 always had 64bit time_t, I thought this change would only affect 32bit packages?

47

They are not migrated on x86 but since this is causing incompatible symbol changes of the ABI, this change needs to be reflected in the package name as per debian policy…(which is then indeed visible on all arches)

2 Likes
48

Thanks for the explanation!

They are not migrated on x86

I guess you mean “on amd64” or “on x86_64”?

So all packages containing native binaries will be renamed to *t64 on all platforms that support 64bit time_t (no matter if they have done so before or not)?

This looks like a quite invasive change - TBH I’m surprised it was apparently rolled out about a month before release…

49

No, i mean the greater x86 architecture (namely i386 and amd64 in dpkg terms)

The tramsition has started ages ago in debian and has been happening in ubuntu since package syncing from debian started for noble. But it went arguably rather slow which is why it is visible to endusers testing noble now.

2 Likes
50

The tramsition has started ages ago in debian and has been happening in ubuntu since package syncing from debian started for noble.

But even in Debian it’s not done yet (or if it is, only since a few days), at least https://wiki.debian.org/ReleaseGoals/64bit-time says

The t64 transition is ongoing (end March 2024) in Debian

Well, I wish you good luck with all this, I hope we can get a usable, stable (and updatable) 24.04 release in the foreseeable future - and many thanks to everyone working their ass off to make it happen, especially now that the xz disaster makes it even harder! <3

1 Like
52

I have just installed the “Beta” release of today and I see that all of these packaging issues are now FIXED. I just want to take a minute to give all the developers that got involved in all this XZ package rebuilding madness a huge round of applause. Seriously - on behalf of the community, job well done!

5 Likes