Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified fyba as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for fyba which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads.
Please cancel the NMU and let us upload it instead with pending changes from git. Kind Regards, Bas
Am 30.01.24 um 15:22 schrieb Sebastiaan Couwenberg: But please remember that this is meant to only hit experimental for now, until the dpkg change lands in unstable. So please don't upload it into unstable just yet. See: https://bugs.debian.org/1061931
gdal will need to be rebuilt once fyba moves to unstable, how will these transitions be coordinated? Regular transitions are staged in experimental, and once the Release Team gives the go-ahead the package is uploaded to unstable after which they schedule binNMUs. Presumably there will be and overarching t64 transition to determine the order in which packages need to be moved to unstable triggering their respective transition which may include packages having their own t64 transition pending in experimental. Kind Regards, Bas
Am 30.01.24 um 16:06 schrieb Sebastiaan Couwenberg: Please see prior discussion in https://bugs.debian.org/1036884 for the overall game plan.
We believe that the bug you reported is fixed in the latest version of
fyba, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061961@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg <sebastic@debian.org> (supplier of updated fyba package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 30 Jan 2024 15:27:24 +0100
Source: fyba
Binary: libfyba-dev libfyba0t64 libfyba0t64-dbgsym
Architecture: source amd64
Version: 4.1.1-9~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Changed-By: Bas Couwenberg <sebastic@debian.org>
Description:
libfyba-dev - Header files for FYBA library
libfyba0t64 - FYBA library to read and write Norwegian geodata standard format
Closes: 1061961
Changes:
fyba (4.1.1-9~exp1) experimental; urgency=medium
.
* Team upload.
.
[ Bas Couwenberg ]
* Enable Salsa CI.
* Bump Standards-Version to 4.6.2, no changes.
* Bump debhelper compat to 13.
* Use not-installed file instead of dh_install override.
* Drop obsolete -Wl,--as-needed linker flag, used by default.
.
[ Lukas Märdian ]
* Rename libraries for 64-bit time_t transition.
(closes: #1061961)
Checksums-Sha1:
24f8877fbd16fd7567bb5fa12b0342614fd44b2e 2014 fyba_4.1.1-9~exp1.dsc
3133edadae0e30aa9eb89f9a5d432690b080ef1a 13224 fyba_4.1.1-9~exp1.debian.tar.xz
0568b3c89097b461372b03687c12040751b98da1 8096 fyba_4.1.1-9~exp1_amd64.buildinfo
afefa1d2fb8d28a04e4818f99e388510fab9314e 168376 libfyba-dev_4.1.1-9~exp1_amd64.deb
0e45496fad010e12b1067b938698704750cdd838 294024 libfyba0t64-dbgsym_4.1.1-9~exp1_amd64.deb
e3ba3520db9e62027c14f7c7b6d40a8a859356fe 112764 libfyba0t64_4.1.1-9~exp1_amd64.deb
Checksums-Sha256:
713de66030201c6c23f3734122a030448a48261fca36208e46e4f6f020b795e8 2014 fyba_4.1.1-9~exp1.dsc
fac1922d08b1418ca54cc5c10a69da932e4c9028c726b45b9607acf52cbac81d 13224 fyba_4.1.1-9~exp1.debian.tar.xz
b5419f444ac8101178f74811a97e16238f43e7d4d42ba7a7ec6a7912b7dd6f69 8096 fyba_4.1.1-9~exp1_amd64.buildinfo
9e9d92d85a61e56b8fdaec0154378d1dfbf401db5e0ed663dfeb00c6908a4c7a 168376 libfyba-dev_4.1.1-9~exp1_amd64.deb
07b102ee04cd90849e264f13d8049b33adb1f1b84efd958c2c3bb5dbd45d4af5 294024 libfyba0t64-dbgsym_4.1.1-9~exp1_amd64.deb
b9a633e2eaf0fb15056a965aa1a830ee3728bf3e6bd51ac32f5e4bad52ddc638 112764 libfyba0t64_4.1.1-9~exp1_amd64.deb
Files:
2aa48a9407edb11930695abb7c9e7582 2014 libs optional fyba_4.1.1-9~exp1.dsc
9d102649a643e71b89ee9dc4cf8f27d5 13224 libs optional fyba_4.1.1-9~exp1.debian.tar.xz
ce2e613a1bca8b94bc1f8e39c396bb7c 8096 libs optional fyba_4.1.1-9~exp1_amd64.buildinfo
485fe61cc437837f2b0cf56c2497d80f 168376 libdevel optional libfyba-dev_4.1.1-9~exp1_amd64.deb
4025bb2ee41d81e51245fa82a4a8bee5 294024 debug optional libfyba0t64-dbgsym_4.1.1-9~exp1_amd64.deb
2573cd8a4f9224e1b0dee23f42ff8e41 112764 libs optional libfyba0t64_4.1.1-9~exp1_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmW5Cb0ACgkQZ1DxCuiN
SvHBHg/9EHrBEeH2P2FO/o6g9QEonjSAhF8maVRIDamvEV0pfxDd2llQw7UbTuLf
YsfB9mroznyhnRuwFKkWQdYfMXPUfz5jz/sbyqJRLhT5941Tax5jeFajihF8Fb/J
lA7M+kZVJZvwJiVpzKtv6MT9ggANfD5CKr6eqI2AWX6my6m+eYSsALdDnTvQvl2Z
fBas1ee2eNWP8A+L/nRf7GKz33uCxyOyVeNQecQlHPK9B5RtKDagcKEiDJonGy/c
KW97IYYvdWkxJYqesIdj/lR9966nkiUoT1wEczlF4CioS+KIJfhQ8nlT7ngFx9vC
sDdEbGVOMBwle5Ep1z54KSv5pZK3kgvP6uCiyHuj5SVN0UK6Md4CnAdAkmYaoO11
8l4AjPHFZvDUQTO0M3iFhz5EjX/JTguzPRVNrgm7/wBZcYhIj97OyiuBG+fGqEQp
wS9l5rWAjGDg79dd7GQ4SxhSwRZ2OL/b9H4OXwQuRktixuqW2sBRkLxuUPoWDsVH
laY0v+m9mNQqx0JU0wWWC842qwueFFK4qanWfSzCdPfBKs4IdSGYQAKYuU/tgqoB
jEuuHLEHAWTooHW9cKAKaZI/fzbORST9HG8+5znqU0y+y1274eSE5R0zlM8tjYCp
/nDJeoWeo72aXIbBJRfGnghXFVBuZRYLupLDo795Wh9d4XDPJdM=
=Vxee
-----END PGP SIGNATURE-----
That only mentions:
"
- sourceful NMUs of all the libraries will be reuploaded to unstable
(without binaries, so that they can be promoted to testing without
additional uploads).
"
Should we assume that to mean that everything will be uploaded at the
same time without taking inter-dependencies into account?
How will the t64 transitions be coordinated with the release team?
Kind Regards,
Bas
We believe that the bug you reported is fixed in the latest version of
fyba, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061961@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg <sebastic@debian.org> (supplier of updated fyba package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 28 Feb 2024 14:40:18 +0100
Source: fyba
Architecture: source
Version: 4.1.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Changed-By: Bas Couwenberg <sebastic@debian.org>
Closes: 1061961
Changes:
fyba (4.1.1-9) unstable; urgency=medium
.
* Team upload.
* Move from experimental to unstable.
(closes: #1061961)
Checksums-Sha1:
d5e29259fd97eec9ac00a8b7a53afe790b8f9c13 1994 fyba_4.1.1-9.dsc
6421bb3009b14b5996b10a79658d9a55fd59704a 13268 fyba_4.1.1-9.debian.tar.xz
f0255c0f9c995c11f248834f6c9f55445b61ce0d 8103 fyba_4.1.1-9_amd64.buildinfo
Checksums-Sha256:
7d260e215ff5fdd074b2f467bddc71fc4133bf1680613a8200383c627d590b78 1994 fyba_4.1.1-9.dsc
4e74d96fc3a9784cf112e301c820c8303696e65bd4d50741cc8e2fee2d9c1985 13268 fyba_4.1.1-9.debian.tar.xz
07d5a6f09e800a64025398669d00cb605d4c40075657bdf6b94c42f5c667c9e3 8103 fyba_4.1.1-9_amd64.buildinfo
Files:
a9c68e9523eb6e42690524fda3e989fa 1994 libs optional fyba_4.1.1-9.dsc
479fea70bca5a7ab2e3f1549b0e0389c 13268 libs optional fyba_4.1.1-9.debian.tar.xz
dde5d15f7ab94cae185260eecee2f378 8103 libs optional fyba_4.1.1-9_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXfOLcACgkQZ1DxCuiN
SvHrzA//QpE1xlLHI01I/qv+CkIJoqQoAT+1BT88RMpWOpuqlPxg4UYXJRvmcX39
7KtBeGB6aTynKF2RJWanVe9x4ueMy+J4uHd1wSLVRZuSovN/ZGjQh8/sE0deLgZ/
+E+Qkwr0r7FSV8QRiHP3Srnkpf5TSYLBLsJEZejZlDeJR7sqfYBRA4A0q+vC/GbJ
jPTIin79D1HXUeruA9oyFIVRqH5L1/1vTe8V3dBiep9ygFtN6qab7VLDiOp2riMx
15N3Qrzov3B8hU1d+EzS484VtMo0iboxjV1c9VEFgCGcuBzX4RB9cxrUFgVv5Rrd
13rgT84AAu4eFYzmWYIWGjy9ZypFdimBAgMmRL/xbrGPktygpqDxrWCU3wG/aow7
ODG3f4k1l3nHQhMUguOsBYQQsMRJYQ/rJLjvtRPyF3i4hPIVe5F5bgc5OO60vX5I
MvMrrYkdVBphGDM3nv0RoqVtFfnYCMD7ZThgksB1+1Ly+lezDL0ng5G8jRqM/2Y7
p3fRjLSCYkLhZqau5esgcuMqU4fSuhQrp/Xp5LDyD+88SPQDcol7bL4P5JCasCxs
i/j7+kcLtxBzn0UTjzgdPLIF/7pE7br+dYFccmc9fucn1N9FwdJAMxSkPGTKqYph
hCRdoXOH6O5rYMElirqSrWCVTbn6MaLmIijS2uxq9HPRXVAoRKY=
=LisQ
-----END PGP SIGNATURE-----
Hi, thanks for taking the NMU. Unfortunately it looks like you uploaded just slightly too early and the package was built with 32 bit time_t on ARM :(
That's odd, because gcc-13 and dpkg were already built & installed on armel & armhf. I also didn't start my builds until I saw a whole bunch by vorlon in the transition tracker. Those should have the same issue then. Kind Regards, Bas
On Thu, 29 Feb 2024 at 17:11, Sebastiaan Couwenberg <sebastic@xs4all.nl> wrote: Hmm well maybe I'm just confused about everything. But this log https://buildd.debian.org/status/fetch.php?pkg=fyba&arch=armhf&ver=4.1.1-9&stamp=1709134774&raw=0 Looks like it was built with "dev_1.22.4 gcc-13_13.2.0-13" which I think are the pre-time64 abi ones. The script we've been using to upload the NMUs adds a versioned build-dep on dpkg-dev which should have avoided this. But maybe we should check...
Might have needed to wait for the buildd chroots to get updated because the package is not fetched from the archive like tzdata? A whole bunch of packages will need to be binNMUed any way, just have the release team include packages like fyba among those too. That change was not included in your NMU diffs. Kind Regards, Bas