using old kernels/os releases to build old ubuntu releases

Bug #2039128 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Expired
Undecided
Unassigned

Bug Description

I am slowly working to prepare Ubuntu to be y2038 compatible.

In the kernel, I would like to start turning off COMPAT_32BIT_TIME syscalls.

However, glibc on focal is the one that started to wrap 64bit syscalls even on 32bit machines.

If these syscalls are turned off, it is likely that glibc in bionic will not execute correctly anymore in a chroot.

This brings the question until when we need to support builders that can build bionic and earlier releases; whilst using identical pool of builders for all releases.

Bionic is currently projected to be supported until 2028, so it matters if launchpad buildd network can stay on Jammy until then.

Or have a dedicated pool of amd64/arm64 "builders" setup to build for i386/armhf only. which will be Jammy based VMs.

Please let me know what is your target lp-buildd VM host OS version in 2028.

Revision history for this message
Jürgen Gmach (jugmac00) wrote :

Hi Dimitri,

thanks for raising this issue.

I think it would make sense to sit down in Riga and discuss this in person.

Would you kindly set up a meeting with me and Colin, and I will add other team members if they are interested?

Thank you!

Changed in launchpad:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.