Hi, Quoting Soren Stoutner (2024-11-26 01:07:06) > I suppose I should note that I have made a few modifications to the example > file because it wasn’t behaving as expected. Specifically, I disabled the > mmdebstgrap auto create because otherwise it was ignoring the tarball I had > created in the previous steps (including the apt-cacher-ng setting) and > creating a new tarball pulling straight from the internet at each build, at > each run of lintian, and at each run of piuparts.
please report a bug about this. This should not happen. It's easier to get to the bottom of this in a bug on the BTS than on d-devel. :) > I also had to specify the distribution or things didn’t work when building > against a changelog that targeting UNRELEASED. That should also not happen. At least it works fine for me... If you open a bug or write me a private mail we can hopefully figure out how our setups differ. > Piuparts is fine if I let it generate its own tarball on each run. But it > doesn’t like using the tarball previously created. Jochen is the sbuild+piuparts expert and probably has some input on this. :) > # Specify the distribution, -d > $distribution = 'unstable'; Setting this will override the Distribution of the .changes file created by sbuild with "unstable", ignoring what your package has set. Are you sure you want this? Thanks! cheers, josch
signature.asc
Description: signature
