Control: tag -1 + moreinfo Control: severity -1 normal Hi,
On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia <[email protected]> wrote: > With the new release of sbuild 0.77 (which moves the run_lintian call outside > of the build function), lintian receives the name of a no longer existing > changes file (as the unlink is part of the copy_changes) and as such it fails > with, for example: > I: schroot -d /<<BUILDDIR>> -c > unstable-amd64-sbuild-a8e6ff65-a882-41b6-9ce3-b5e764b4ca8c --run-session -q > -u maxy -p -- lintian -I --pedantic --show-overrides > sddm_0.18.0-1_amd64.changes > D: Running command: schroot -d /<<BUILDDIR>> -c > unstable-amd64-sbuild-a8e6ff65-a882-41b6-9ce3-b5e764b4ca8c --run-session -q > -u maxy -p -- lintian -I --pedantic --show-overrides > sddm_0.18.0-1_amd64.changes > warning: "sddm_0.18.0-1_amd64.changes" cannot be processed. > warning: It is not a valid lab query and it is not an existing file. > > E: Lintian run failed (runtime error) > > The issue is not present using the 0.76 version, and can be workaround > commenting the unlink call from the copy_changes function (as shown in the > attached file). > > Thanks for working in sbuild. :) I really fail to reproduce your problem. Can you give me your exact sbuild invocation so that I may be able to see the same error that you see? I see it neither in the version currently in unstable nor in git master. Thanks! cheers, josch
signature.asc
Description: signature
