Am Samstag, dem 03.02.2024 um 20:27 +0000 schrieb Sergio Durigan Junior: > Source: reiserfsprogs > Version: 1:3.6.27-7 > Severity: serious > Tags: patch pending sid trixie > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t > > NOTICE: these changes must not be uploaded to unstable yet! > > 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 > reiserfsprogs 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). > >
Hi, thanks for working on the time_t transistion. But ReiserFS is too old. It still uses 32bit fields in it's superblock and other metadata blocks. And fsck is just writing out the return value of time(NULL) to the superblock when the last check was run. So I don't think it makes currently any problems. But it can't be made 64bit safe and so shouldn't be used at all in 2038 and beyond. Luckly it has been already marked deprecated upstream and scheduled for removal in Linux this year 2024 Only problem to directly RM reiserfsprogs is, that now btrfs-progs depend on libreiserfscore0 due to btrfs-convert supporting ReiserFS. Cheers Felix
