"Adam D. Barratt" <[email protected]> writes: > On Sat, April 4, 2009 17:20, Russ Allbery wrote:
>> Could you run lintian with -d so that we can see what's generating >> those messages? The options that Lintian uses with tar haven't changed >> in a while, but then neither has tar, so I'm a bit befuddled by this. > There was a tar upload to unstable yesterday. Sean, have you upgraded to > tar 1.22-1, or is this with the older 1.20-1? Ah, indeed, I missed that. I suspect the following change from 1.21: ** Fixed record size autodetection. If detected record size differs from the expected value (either default, or set on the command line), tar always prints a warning if verbosity level is set to 1 or greater, i.e. if either -t or -v option is given. Not sure what's generating the unexpected record sizes, but it's rather annoying that tar now warns about them. We run tar -t four different places in Lintian currently: * Index of the control tar file of a binary package * Index of the data tar file of a binary package * Numeric index of the data tar file of a binary package * Index of the source tar file of a source package I suspect the solution is to capture errors from the first two and the fourth and turn any errors into Lintian tags, possibly suppressing particular messages (such as maybe this one), and just suppress all errors from the third since they're going to duplicate the second. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
