Bug#523408: lintian says file: unrecognized option `--lzma' with 3.0 format.
On Fri, 2009-04-10 at 14:28 +1000, Trent W. Buck wrote: When running lintian on a binary built from a 3.0 (quilt) source package, with both the .orig.tar.lzma and .debian.tar.lzma being compressed with lzma (not gzip), I got the error file: unrecognized option `--lzma' printed early on in the output. The full output is: $ lintian dosage*changes E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file md5 dosage_1.6.0+2-1.dsc E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file sha1 dosage_1.6.0+2-1.dsc E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file sha256 dosage_1.6.0+2-1.dsc Those are to be expected, as the dsc will contain the details for the generated package (i.e. it should match the checksums in _amd64.changes). file: unrecognized option `--lzma' My assumption is that the above is being generated by the file-info collection script; could you please retest using Lintian's -d option to confirm? Assuming that the file-info script is generating the error, that implies that the source tarball index Lintian has generated contains a line which contains --lzma which is then being split and passed to 'file'. Would it be possible for you to make a copy of the source and binary packages available? That would be very useful for debugging the issue. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523408: lintian says file: unrecognized option `--lzma' with 3.0 format.
retitle 523408 file-info should use file -- foo, not file foo thank you On Fri, Apr 10, 2009 at 10:49:06AM +0100, Adam D. Barratt wrote: file: unrecognized option `--lzma' Assuming that the file-info script is generating the error, that implies that the source tarball index Lintian has generated contains a line which contains --lzma which is then being split and passed to 'file'. Would it be possible for you to make a copy of the source and binary packages available? That would be very useful for debugging the issue. Oh, you're right! I realized (after sending the mail above) that I had accidentally called tar -cf --lzma ... by accident, before I successfully created the .orig.tar.lzma. So there was a file CALLED --lzma in the source tarball or in the working tree (or both). So this sounds like my fault, but in future perhaps lintian should called file -- foo instead of just file foo? (When I filed the original report, I thought lintian was calling file --lzma instead of file -z or something.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523408: lintian says file: unrecognized option `--lzma' with 3.0 format.
On Fri, 2009-04-10 at 21:31 +1000, Trent W. Buck wrote: Oh, you're right! I realized (after sending the mail above) that I had accidentally called tar -cf --lzma ... by accident, before I successfully created the .orig.tar.lzma. So there was a file CALLED --lzma in the source tarball or in the working tree (or both). Yeah, that would do it. :-) So this sounds like my fault, but in future perhaps lintian should called file -- foo instead of just file foo? I've just committed a fix that does exactly that. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523408: lintian says file: unrecognized option `--lzma' with 3.0 format.
Package: lintian Version: 2.2.9 Severity: normal When running lintian on a binary built from a 3.0 (quilt) source package, with both the .orig.tar.lzma and .debian.tar.lzma being compressed with lzma (not gzip), I got the error file: unrecognized option `--lzma' printed early on in the output. The full output is: $ lintian dosage*changes E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file md5 dosage_1.6.0+2-1.dsc E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file sha1 dosage_1.6.0+2-1.dsc E: dosage_1.6.0+2-1_source.changes: checksum-mismatch-in-changes-file sha256 dosage_1.6.0+2-1.dsc file: unrecognized option `--lzma' Usage: file [-bcikLhnNrsvz0] [-e test] [-f namefile] [-F separator] [-m magicfiles] file... file -C -m magicfiles Try `file --help' for more information. W: dosage source: out-of-date-standards-version 3.8.0 (current is 3.8.1) E: dosage source: unsupported-source-format 3.0 (quilt) W: dosage: maintainer-script-ignores-errors postinst $ -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-23-openvz (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lintian depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii diffstat1.45-2 produces graph of changes introduc ii dpkg-dev1.14.25 Debian package development tools ii file4.26-1 Determines file type using magic ii gettext 0.17-4 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1Help i18n of RFC822 compliant conf ii libipc-run-perl 0.80-2 Perl module for running processes ii libparse-debianchan 1.1.1-2 parse Debian changelogs and output ii libtimedate-perl1.1600-9 Time and date functions for Perl ii liburi-perl 1.35.dfsg.1-1Manipulates and accesses URI strin ii man-db 2.5.2-4 on-line manual pager ii perl [libdigest-sha 5.10.0-19Larry Wall's Practical Extraction lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarchnone (no description available) pn libtext-template-perl none (no description available) ii man-db2.5.2-4on-line manual pager -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
