linphone packaging and testing sbuild

[Johannes Schauer]

Quoting Tzafrir Cohen (2017-05-07 09:51:54)
> On Sun, May 07, 2017 at 07:04:35AM +0200, Johannes Schauer wrote:
> > Quoting Geert Stappers (2017-05-07 00:49:53)
> > > On Sun, May 07, 2017 at 12:46:21AM +0200, Geert Stappers wrote:
> > > > chroot:UNRELEASED chroot does not exist
> > > > E: Error creating chroot session: skipping bctoolbox
> > > How to setup "sbuild"?
> > 
> > sbuild chooses the chroot to do the package build in from the distribution
> > value of the latest debian/changelog entry. In our case, that value is
> > UNRELEASED and it seems that you don't have your sbuild configured to map
> > UNRELEASED to unstable chroots.
> > 
> > There are two ways to solve this. Either you specify the schroot manually on
> > the command line by passing the following option to sbuild:
> > 
> >  -c unstable-amd64-sbuild
> 
> Or:
> 
>   -d unstable
> 
> right?

From the man page:

 | -d, --dist=distribution
 | Explicitly set the distribution for the package build. This will be
 | selecting the  correct  chroot  to use  and  also  sets  the  value  of the
 | Distribution field in the created .changes file.

So yes, one side-effect of -d is to select the right chroot but another one is,
that it changes the value of the Distribution field of the generated .changes
file which might not be what you want, so be careful with that option.

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20170507/35f4e2b7/attachment-0001.sig>