Johannes, On Monday, November 25, 2024 11:37:41 PM MST Johannes Schauer Marin Rodrigues wrote: > 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 assumed this was some documentation problem in the rewrite of the wiki (hard to submit a bug report against the wiki page). But if this is an actual bug in sbuild I will be happy to submit a bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088304 > > 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. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088307 > > 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. :) I see he responded separately, so I will reply to that email with further information. I have also filed a bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088308 > > # 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? I would like it to be able to build instead of fail when the changelog says UNRELEASED, but I would be happy to not specify the distribution if I can figure out how to make it work. Lintian produces an error when this happens, so there is no chance I would ever upload such a package, because I always produce a lintian-clean build before upload. E: python-trezor changes: unreleased-changes N: N: The distribution in the Changes field copied from debian/changelog N: indicates that this package was not intended to be released yet. N: N: Please refer to Bug#542747 for details. N: N: Visibility: error N: Show-Always: no N: Check: fields/distribution -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
