Hi, it seems that i achieved the goal that motivated me to upgrade my Sid. lsb_release -a now says Description: Debian GNU/Linux forky/sid
In hindsight it would have been more civilized to run apt-get purge gnome-themes-standard-data instead of mutilating /var/lib/dpkg/info/ and /var/lib/dpkg/status when the update aborted with a file conflict. But who would come to the idea that "standard-data" is outdated and has been replaced by "extra-data" ? Another obstacle was the presence of a now forbidden sshd configuration line PubkeyAcceptedKeyTypes +ssh-dss It is not clear whether lack of RAM caused the error messages about missing files in /tmp when i tried to upgrade directly from pre-trixie Sid to pre-forky Sid. Now with 2 GiB of RAM and upgrading from trixie no such problems appeared. About my motivation: With the successfully upgraded system i verified that Linux kernel 6.16 can indeed represent ISO 9660 Rock Ridge file dates after year 2038 up to at least 2500 (probably up to 9999). Without Rock Ridge all times beginning at Jan 1 2156 UTC are curbed by libisofs to the end of year 2155. Long story: ======================================================================= I looked into an old version of man sshd_config to determine the past meaning of the deprecated configuration options in my /etc/ssh/sshd_config : ----------------------------------------------------------------------- Sep 12 19:30:01 ts6-sid sshd[103708]: /etc/ssh/sshd_config line 16: Deprecated o ption UsePrivilegeSeparation Sep 12 19:30:01 ts6-sid sshd[103708]: /etc/ssh/sshd_config line 19: Deprecated o ption KeyRegenerationInterval Sep 12 19:30:01 ts6-sid sshd[103708]: /etc/ssh/sshd_config line 20: Deprecated o ption ServerKeyBits Sep 12 19:30:01 ts6-sid sshd[103708]: /etc/ssh/sshd_config line 31: Deprecated o ption RSAAuthentication Sep 12 19:30:01 ts6-sid sshd[103708]: /etc/ssh/sshd_config line 38: Deprecated o ption RhostsRSAAuthentication ----------------------------------------------------------------------- All could be removed because UsePrivilegeSeparation seems to be hardcoded to "yes" now. It was already "yes" in my sshd_config. The other options belonged to protocol version 1, which is not supported any more. I restarted the ssh service and still can log in from the host. Now for the error messages of the failed upgrade from pre-trxie to pre-forky Sid: ----------------------------------------------------------------------- Preparing to unpack .../2-libnss-nis_3.1-5+b1_amd64.deb ... Unpacking libnss-nis:amd64 (3.1-5+b1) over (3.1-4) ... dpkg-deb: error: failed to read archive '/tmp/apt-dpkg-install-cvyXki/2-libnss-nis_3.1-5+b1_amd64.deb': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-cvyXki/2-libnss-nis_3.1-5+b1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 dpkg: error processing archive /tmp/apt-dpkg-install-cvyXki/3-libc-devtools_2.41-12_amd64.deb (--unpack): cannot access archive '/tmp/apt-dpkg-install-cvyXki/3-libc-devtools_2.41-12_amd64.deb': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-cvyXki/4-libc-dev-bin_2.41-12_amd64.deb (--unpack): cannot access archive '/tmp/apt-dpkg-install-cvyXki/4-libc-dev-bin_2.41-12_amd64.deb': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-cvyXki/5-libcrypt1_1%3a4.4.38-1_amd64.deb (--unpack): cannot access archive '/tmp/apt-dpkg-install-cvyXki/5-libcrypt1_1%3a4.4.38-1_amd64.deb': No such file or directory Errors were encountered while processing: /tmp/apt-dpkg-install-cvyXki/2-libnss-nis_3.1-5+b1_amd64.deb /tmp/apt-dpkg-install-cvyXki/3-libc-devtools_2.41-12_amd64.deb /tmp/apt-dpkg-install-cvyXki/4-libc-dev-bin_2.41-12_amd64.deb /tmp/apt-dpkg-install-cvyXki/5-libcrypt1_1%3a4.4.38-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) E: Unable to read /tmp/apt-dpkg-install-cvyXki - opendir (2: No such file or directory) ----------------------------------------------------------------------- The problematic packages are download neighbors: ----------------------------------------------------------------------- Get:941 http://ftp.de.debian.org/debian unstable/main amd64 libnss-nis amd64 3.1-5+b1 [26.1 kB] Get:942 http://ftp.de.debian.org/debian unstable/main amd64 libc-devtools amd64 2.41-12 [67.6 kB] Get:943 http://ftp.de.debian.org/debian unstable/main amd64 libc-dev-bin amd64 2.41-12 [58.2 kB] Get:944 http://ftp.de.debian.org/debian unstable/main amd64 libcrypt1 amd64 1:4.4.38-1 [90.1 kB] ----------------------------------------------------------------------- followed by: ----------------------------------------------------------------------- Get:945 http://ftp.de.debian.org/debian unstable/main amd64 libcrypt-dev amd64 1:4.4.38-1 [119 kB] Get:946 http://ftp.de.debian.org/debian unstable/main amd64 libc6-dev amd64 2.41-12 [1,991 kB] Get:947 http://ftp.de.debian.org/debian unstable/main amd64 libc6-dbg amd64 2.41-12 [7,341 kB] ----------------------------------------------------------------------- of which none where unpacked before the upgrade aborted. Further i see in the running trixie system $ df /tmp Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 1010624 0 1010624 0% /tmp instead of the pre-trixie Sid's /dev/sda1 31815696 16821324 13352696 56% / So the idea that /tmp was not large enough during the upgrade gains plausibility. It depends on when tmpfs is employed during the upgrade procedure. But now it is clear that i need more RAM than before. Before the trixie attempt i had increased the VM's memory from 1 GiB to 2 GiB as recommended "With Desktop" by https://www.debian.org/releases/stable/amd64/ch03s04.en.html I dont's see the memory footprint of a running desktop, though: $ free total used free shared buff/cache available Mem: 2021248 328184 1614820 976 218708 1693064 Swap: 1045500 0 1045500 It's time for getting on Sid again. In /etc/apt/sources.list : deb http://ftp.de.debian.org/debian/ unstable main deb-src http://ftp.de.debian.org/debian/ unstable main As superuser: apt update apt -o APT::Get::Trivial-Only=true full-upgrade apt upgrade --without-new-pkgs apt full-upgrade All seems to have worked well. I can login before and after reboot. $ uname -a Linux ts6-sid 6.16.5+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.16.5-1 (2025-09-05) x86_64 GNU/Linux That's what i'm after. The Y2038 bug in the ISO 9660 driver should now be fixed in favor of a Y9999 bug. (It would have been easier to fix it only up to year 2156. But as the more generous fix was obviously accepted i as bystander will not complain.) Building GNU xorriso-1.5.7 ... new compiler warnings, old false warnings, but all in all it works. Hmm ... year 9999 is too ambitioned for libisofs for now. But 2500 gets properly encoded and decoded. Let's see what Linux 6.16 says: ----------------------------------------------------------------------- # mount /dvdbuffer/test.iso /mnt/iso mount: /mnt/iso: WARNING: source write-protected, mounted read-only. # $ ls -l /mnt/iso ... -rwxr-xr-x 2 root root 149960 Sep 13 2030 Y2030 -rwxr-xr-x 2 root root 158632 Sep 13 2149 Y2149 -rwxr-xr-x 1 root root 149960 Sep 13 2152 Y2152 -rwxr-xr-x 1 root root 63944 Sep 13 2500 Y2500 -rwxr-xr-x 1 root root 63944 Jun 4 17:14 Y9999 $ # umount /mnt/iso # mount -o norock /dvdbuffer/test.iso /mnt/iso mount: /mnt/iso: WARNING: source write-protected, mounted read-only. # $ ls -l /mnt/iso ... -r-xr-xr-x 1 root root 149960 Sep 13 2030 y2030 -r-xr-xr-x 1 root root 158632 Sep 13 2149 y2149 -r-xr-xr-x 1 root root 149960 Sep 13 2152 y2152 -r-xr-xr-x 1 root root 63944 Jan 1 2156 y2500 -r-xr-xr-x 1 root root 63944 Jun 4 17:14 y9999 $ ----------------------------------------------------------------------- The first two dates are encoded in traditional 7-byte time format. xorriso will begin to use the 17-byte time format on Jan 01 2150. (Cough cough ... i can hardly await it ...) Only Rock Ridge offers the long format for after year 2156. Plain ISO 9660 only offers the short format. The date of Y9999_long is the one of the original file "/bin/who", as of today's Sid. I will have to investigate why xorriso-1.5.7 said xorriso : SORRY : -alter_date: Cannot decode timestring 'Sep 13 15:50:50 9999' and how far it is able to put a file in the future. (Also i will rectify the embarassing but harmless new warnings about swappend arguments of calloc(2). To my luck multiplication is commutative.) Have a nice day :) Thomas
