I was on +1 rotation this past week, aiming mainly to help move the
64-bit time_t transition further along. Being a DD but not yet having
full upload rights to Ubuntu directly, I did most of my work upstream
in Debian and Steve kindly synced my changes into noble - thanks!
Also, for the same reason, Steve kindly kicked off some no-change
rebuilds for me to fix a few FBTFS.
libdmtx
-------
A leftover reference in debian/rules to the old shared library name
was causing FTBFS. I NMU'd a fix.
https://bugs.debian.org/1066810
nsync
-----
A symbols file needed updating to reflect the 64-bitness of time_t
on the relevant arches. Did a QA upload with the fix.
https://bugs.debian.org/1065979
lirc
----
FTBFS on 32-bit arches with 64-bit time_t, due to reliance on the
kernel's timeval, which is not y2038-safe and being phased out.
NMU'd upstream patch to fix build.
https://bugs.debian.org/1066905
ulfius
------
Also FTBFS on 32-bit arches with 64-bit time_t. NMU'd upstream patch.
https://bugs.debian.org/1066944
accountsservice
---------------
Lastly, not time_t-related and not truly +1 (since I'm on the Desktop
team and this is a desktop package), but I did review and sponsor an
accountsservice upload by fossfreedom with an upstream patch to fix
FTBFS across all arches in noble due to removal of the 'assertEquals'
method alias in unittest in Python 3.12, deprecated in Python 3.2.
https://launchpad.net/bugs/2057710
I'll check back in on the excuses page this week as well,
for any other potential fixes I may be able to help with.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
