Package: sbuild
Version: 0.62.6-1
Severity: wishlist

Hi,

this is a bit related to #529281 but not completely. When using a
build_dir, the output files are copied to the relevant folder. But when
building a -2+, the orig file is not copied to that folder, meaning it's
not possible to run lintian on the source part.

It seems that pbuilder/cowbuilder do copy the orig file in the
destination folder everytime.

Regards,

We only copy the files set in the .changes.  If we copy additional
files, then you can't e.g. 'dcmd rm foo.changes' to remove the
files after upload, which would result in accumulating a lot of
additional files.

There is another request to run lintian in the chroot rather than
on the host.  We could certainly do that before copying the files
out of the chroot.  Would this solve the problem for you?


Thanks,
Roger

Yes, but I'm personally ok with that, I can't easily remove them
manually.

Well, the lintian part would be ok, but I might use it for other stuff,
I find that pretty convenient to be honest :)

Regards,

I've just switched over to using sbuild (from pbuilder) to build my packages
for upload to Debian and I've run into this same bug.

My workflow generally involves building the source package by whatever means
is necessary for the package (depends on team, vcs, etc).  Then I run adt-run,
sbuild (possibly with --run-piuparts), and do a bunch of other testing on the
package before I upload it.  One of the last things I do is explicitly run
lintian over the changes file.

Because pbuilder copies the orig.tar.gz even for -2+ packages, lintian is
usually happy, but when building the package with sbuild, lintian will thrown
an internal error before you even get to the good stuff.

I can manually cp the orig.tar.gz from the tarballs directory to the results
directory after sbuild completes and then lintian is happy, but I wish I
didn't have to do this one extra step.