Le lundi 06 juillet 2026 à 20:43 -0700, Soren Stoutner a écrit : > On Monday, July 6, 2026 2:30:50 PM Mountain Standard Time Julien > Puydt wrote: > > Le samedi 04 juillet 2026 à 21:11 +0500, Andrey Rakhmatullin a > > écrit : > > > On Sat, Jul 04, 2026 at 06:09:24PM +0200, Julien Puydt wrote: > > > > > > It doesn't happen in a chroot. > > > > > > > > > > I thought you said it does. > > > > > > > > I rechecked and it doesn't. I think I mixed up somewhere... > > > > > > Well then the problem is mot likely in /usr/local or something > > > like > > > that. > > > > Nothing in /usr/local... > > > > Is there a way to actually debug what goes sideways? > > > > I'm a bit desperate... > > My guess is that one of the binaries that creates or processes > tarballs is > corrupt on your system. You could try reinstalling anything that > looks > suspicious. You could also try looking at the list of packages > installed in > your chroot as a list of possible packages to verify that haven’t > been > corrupted. > > In this regards, dpkg -V is helpful. > > https://manpages.debian.org/trixie/dpkg/dpkg.1.en.html
Oh, dear, I did just that and now the error is gone! We had checked so many thing, and somewhere some file was just corrupt and stayed so even through package upgrades... THANK YOU ALL! JP
