On Fri, Dec 20, 2013 at 10:01:22AM +0100, Raphaël Hertzog wrote: > Package: git-buildpackage > Version: 0.6.7 > Severity: normal > > When you build with git-buildpackage -A, dpkg-buildpackage will generate > an *_all.changes file but git-buildpackages will still try to call lintian > with an *_<arch>.changes file. This results in this:
Hmm...while we don't support -A yet I still wonder why this happens since it should fall back to _source.changes instead. I know it's still incorrect but it certainly shouldn't check the arch specific file. Can you attach (or mail me directly) the full build output with --git-verbose please. Do you have any better ideas than checking the dpkg-buildpackage command line for -A to detect wheter we need arch or all? I'd be so cool if dpkg-buildpackage would have a nice way to communicate back such information to build tools. Cheers, -- Guido > > Now running lintian... > warning: "linux-kali_3.12.3-1~kali2_amd64.changes" cannot be processed. > warning: It is not a valid lab query and it is not an existing file. > Finished running lintian. > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages git-buildpackage depends on: > ii devscripts 2.13.8 > ii git 1:1.8.5.1-1 > ii man-db 2.6.5-2 > ii python 2.7.5-5 > ii python-dateutil 1.5+dfsg-0.1 > ii python-pkg-resources 1.4.2-1 > > Versions of packages git-buildpackage recommends: > ii cowbuilder 0.73 > ii pristine-tar 1.30 > > Versions of packages git-buildpackage suggests: > ii python-notify 0.1.1-3 > ii unzip 6.0-10 > > -- 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
