On Wed, Sep 22, 2010 at 12:15:47AM -0600, Bdale Garbee wrote: >> According to the changelog, the latest version of tar >> package in lenny replaced rmt source with the one from >> paxutils for security reasons. Unfortunately, it also made >> it impossible to use tar and rmt together.
> Have you tried using a tar 1.23 version? The rmt version I > used for 1.20-1+lenny1 is the one that's shipping in the > current tar source tree. So, I'd like to understand whether > there's something about fresher versions of tar that causes > them to work better with rmt, or if this is a general > upstream problem with the rmt in tar at this point. I hadn't before. I have just tried using rmt binary from tar 1.23-2.1 (squeeze). It's just as broken as the one in 1.20-1+lenny1. Using it with tar binary from the same version of the package doesn't help either, naturally. My bad, I misinterpreted the 1.20-1+lenny1 changelog entry, somehow thinking that taking paxutils rmt was a Debian-specific way of the security fix. It indeed seems a tar upstream problem. However, I also found out that rmt in the paxutils upstream has been altered a week ago to fix the buffering of stdout (but not debug output) and parsing of the `mode' argument of `O' command. (I found that out from Debian bug #587702, reporting essentially the same as the one I posted, albeit with no patches. I should have found it first and added to it instead of posting a new report, another bad of mine...) So, Debian Lenny version of tar package can wait for the updated rmt to get from paxutils upstream to tar upstream, and then reimport it, or reimport the updated rmt directly from paxutils upstream, or just outright apply the fixes like mine or the one referred to in #587702. Cheers, -- /Awesome Walrus <wal...@amur.ru> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
