On Thu, 18 Apr 2024 23:39:14 +0000 IvanAbs <i...@alk.mx> wrote: > On 2024-04-17 several of my servers running Debian 10 received an > update for the tzdata package via Debian unattended-upgrade. However, > this update resulted in corruption of files within the > /usr/share/zoneinfo directory.
I, too, encountered a variation of this issue today while trying to update the tzdata package on my system. I was eventually able to resolve the issue with a little manual intervention. Details follow. > I was using tzdata 2023c-2 package, and originally installed from an > official Debian source In my case, the installed version of the package was tzdata 2023c-5. > I installed tzdata 2023c-2 with dpkg -i, because our severs needs the > last-year updated data, but there were not a release for Debian 10, > until yesterday. Similarly, I had installed tzdata 2023c-5 on what is effectively Debian Bullseye install (though what is actually an unabashed FrankenDevuan install that is mostly composed of packages from Devuan's Chimaera release). My motivation for doing so was similar: I wanted the then-current timezone database and the package in chimaera/bullseye had yet to be updated. I fully acknowledge this course of action is actively frowned upon[1]. [1] https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian > To resolve this issue, I had to completely remove the tzdata 2023 > version and perform a clean installation of the new tzdata 2024 > version. Here's how I was able to resolve the issue. Using snapshot.debian.org, I downloaded tzdata_2023d-1_all.deb which installed without issue over 2023c-5. Afterward, I was able to install tzdata 2024a-0+deb11u1 without issue. As this issue only manifests on systems in explicitly unsupported configurations, the severity of the bug should probably be reduced from grave, but I will leave that decision to others. I hope this was helpful, -- Plasma
