Hi Niels,
I'm also hitting this lintian bug.
> Aha, I think I got it. There is no ".orig" tarball in the result dir.
It looks like you're right:
$ lintian build-area/build-area/hashid_3.1.4-2_amd64.changes
cp: cannot stat '/tmp/temp-lintian-lab-NVFEj9_sPr/pool/h/hashid/hashid_3.1.4-2_source/hashid_3.1.4.orig.tar.gz': No such file or directory
dpkg-source: error: cp /tmp/temp-lintian-lab-NVFEj9_sPr/pool/h/hashid/hashid_3.1.4-2_source/hashid_3.1.4.orig.tar.gz to /tmp/temp-lintian-lab-NVFEj9_sPr/pool/h/hashid/hashid_3.1.4-2_source/hashid_3.1.4.orig.tar.gz subprocess returned exit status 1
internal error: dpkg-source -x failed with status 25 at /usr/share/lintian/collection/unpacked line 72.
warning: collect info unpacked about package hashid failed
warning: skipping check of source package hashid
$ cp build-area/hashid_3.1.4.orig.tar.gz build-area/build-area/
$ lintian build-area/build-area/hashid_3.1.4-2_amd64.changes
[works]
... another time
$ lintian build-area/build-area/bleachbit_2.0-2_amd64.changes
[doesn't work, same error]
$ cp build-area/bleachbit_2.0.orig.tar.gz build-area/build-area/
$ lintian build-area/build-area/bleachbit_2.0-2_amd64.changes
[works]
... the other way
$ lintian build-area/build-area/dwm_6.1-4_amd64.changes
[works]
$ rm build-area/build-area/dwm_6.1.orig.tar.gz <-- Yep, the orig was present in the folder
$ lintian build-area/build-area/dwm_6.1-4_amd64.changes
[doesn't work, same error]
Cheers,
Hugo
--
Hugo Lefeuvre (hle) | www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA
Attachment:
signature.asc
Description: PGP signature