On Mon, 2022-11-21 at 00:03 +1100, Stuart Prescott wrote: > Hi Michał, > > Thanks for the intriguing report. > > The error is coming from the invocation of dpkg-deb which runs > ["tar", "-x", "-m", "-f", "-", "--warning=no-timestamp"] > > Do I take it that on your system dpkg-deb exists but is entirely > non-functional because it can't actually work with any archives?
Ah, I didn't even realize I have dpkg installed! I've never used it but if you think it's broken, then it probably is ;-). > If that's the case, I guess the real solution is fixing dpkg-deb. In the > meantime, I'll need to think about how the test can navigate its way > around a broken dpkg-deb being installed — at present, it assumes that > the tools it finds are not broken. Indeed. Should I file a new bug against dpkg, or can you "reassign" this one then? As for python-debian, please don't worry too much about it. This setup with bsdtar is quite experimental, and mostly meant to catch and report potential issues right now. I don't think you have to worry about real users being affected right now. -- Best regards, Michał Górny