Re: 64-bit time_t transition question, and Re: Backport request for btrfs-progs
Nicholas D Steeves <[email protected]>
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <[email protected]> |
Benjamin Drung <[email protected]> writes: > On Fri, 2024-06-21 at 16:14 -0400, Nicholas D Steeves wrote: >> >> One thing I'm not sure about is how the 64-bit time_t transition affects >> backports: A no-change backport of btrfs-progs would normally require a >> no-change backport of reiserfsprogs, but I feel like reiserfsprogs' >> 64-bit time_t transition could break things for bookworm users. The >> three options appear to be: >> >> 1. No-change backports everywhere (and risk breakage). >> 2. Disable support for reiserfs in btrfs-convert (my preference). >> 3. Backport reiserfsprogs without the 64-bit time_t transition. >> >> I don't yet trust or recommend the use of btrfs-convert, but "ReiserFS >> has been deprecated upstream and scheduled for removal 2025" >> (reiserfsprogs/debian/changelog), so I can understand why people might >> want support for this to migrate in-place now... That said, backup and >> restore to a filesystem created with mkfs (rather than btrfs-convert) is >> the safest route, and I'd prefer if users used trixie to experiment with >> in-place conversion. > > tl;dr: Backport with the 64-bit time_t transition changes reverted > > Long answer: In case you backport a package, it will build with the old > dpkg/debhelper and therefore will not enable 64-bit time_t. So in case > your backport would include the 64-bit time_t changes, these changes > would be wrong. Belated thank your reply! Ah, so it seems no-change uploads will often not be possible this cycle, and the checklist would be: 1. Revert 64-bit time_t transition changes 2. Downgrade dpkg-dev requirement (related to #1) The Debhelper bpo reverts movetousr, but it really required to use bookworm's dh? Not having (>= 13.11.5~) will reintroduce up to three bugs to affected packages, and as the next year progresses the delta will grow. Thus 3. Downgrade debhelper requirement? Is this documented anywhere yet? Best, Nicholas
signature.asc
(application/pgp-signature, 857 B)
-----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmZ9hYwQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYUsMD/94niYd2NJZ1i/jITDNfp4+f9rELeXC5Qei UMtxjno6ROpyMOd/A0IXGPTYT8xDJjkgXTw+vdpHVWfdW6AmWy9sqvKo8Y/UHdff FM8zZ2zid4MRseD6BgXxkdIYAUg5bH8Og/DD+WzrE4xoRzJW0HZZVSvX89Nl63Hw ppVkH/k3l5jOWFDNq/WgsWo/1OhqBt12IIsBEIeRE7AwiDVTG35pPwM8z2Ns/IaB Yb1bp5AiDrN7D8nurcHo8wuoqRwV3LJvs8t9zsSkmwxts2CjtD5SvYzry/a31hj0 bnJZ+KEPRVsDLN0Fcsv5mbQPZiFHalcB3Y6jlZa1r/ezeYekEYuyf+1NRjE5hjfw Fb3lfnBWzdKz+CRdE61cMz2wMfB5cX/vTrA//OuF9yh695xFGMs2sz9w2Sz1Rcz7 oSI7X/RCReIuSw20zz4LCJsWZRKntxwcGe9OAL8miNzOC7j4nzHjHGSMs62vHX67 BHLQfEcfO6RyfTbhFaRLR4ewUnyRQ7/qDOyFdy9fbjiMJ7Qom2uaMoxs6pVPn2xR uvnssBNmbSq7IeAX5gIcK5yend26Kv5nC5DkNCpMmgwQzGkZ1WUEjXv9NJmaBvxU 0M7qJuKSJO3d7ZAx7Z+NN4EOUWuHZzBbfCLdg45xA31gUklEh7JkCcXdXx7Rof8d IYLdOGE4Bg== =CHvf -----END PGP SIGNATURE-----