It seems that years ago the dpkg maintainers strongly disagreed with the "/usr merge" policy, or at least the way it was being implemented using symlinks such as /bin→usr/bin.dpkg: warning: This system uses merged-usr-via-aliased-dirs, going behind dpkg's
dpkg: warning: back, breaking its core assumptions. This can cause silent file
dpkg: warning: overwrites and disappearances, and its general tools misbehavior.
dpkg: warning: See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>.
They lost that argument, because even Debian itself now requires this configuration. The warning has been disabled for Debian and Ubuntu, but I assume you are running Raspberry Pi OS 32bit, which is based on Raspbian.
(The warning is in /var/lib/dpkg/info/dpkg.postinst, which only runs after dpkg itself is updated.)
Was it shortly after boot? Your local clock was a few hours in the past.now - 17:04 CET I've got this
E: Release file for http://deb.debian.org/debian/dists/book ... /InRelease is not valid yet (invalid for another 3h 39min 37s). Updates for this repository will not be applied.
E: Release file for http://archive.raspberrypi.com/debian/d ... /InRelease is not valid yet (invalid for another 4h 12min 15s). Updates for this repository will not be applied.
(The two InRelease files are signed with different keys by different groups in different places, so it is inconceivable they both made a mistake and also corrected it at exactly the same time.)
Statistics: Posted by jojopi — Mon May 13, 2024 4:37 pm