On Tuesday, November 26, 2024 12:27:22 PM MST Andrey Rakhmatullin wrote: > On Tue, Nov 26, 2024 at 12:21:55PM -0700, Soren Stoutner wrote: > > > > # 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 > > I just always pass -d to sbuild explicitly. It's not a big deal when you > always pass something like 7-8 options to sbuild explicitly and building for > !unstable is rare enough so editing the command is not a big deal either.
Yes. Passing -d to sbuild is functionally the same as specifying the $distribution variable .sbuildrc. In either case, if it isn’t specified, UNRELEASED appears to cause problems with sbuild and unshare, which appears to be a bug (unexpected behavior) according to this thread. The build logs do show that the main sbuild process converts UNRELEASED to unstable when auto- creating tarballs, although not when trying to find an existing one (see the bug reports previously linked). But Piuparts doesn’t so auto-adjust from UNRELEASED to unstable. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
