Johannes Schauer writes ("Re: [buildd-tools-devel] Bug#868527: want sbuild
--no-source or something"):
> Quoting Ian Jackson (2017-07-17 11:31:07)
> > 4. Building and unpacking a git bundle is pointless work when we know that
> >the destination completely trusts the
Quoting Ian Jackson (2017-07-17 11:31:07)
> That would be a perfectly fine answer from my point of view. However,
> it has a few different behaviours. I'm not sure what is best.
>
> Things I thought of:
>
> 1. If there are files which are ignored, or uncommitted, this would
>use the
Johannes Schauer writes ("Re: [buildd-tools-devel] Bug#868527: want sbuild
--no-source or something"):
> Indeed, the task to solve is how to transfer the source into the chroot.
>
> But is $(dpkg-source -Zgzip -z0 --format=1.0 -sn) really the right
> thing to do? Would
Quoting Ian Jackson (2017-07-16 14:32:17)
> It would be nice if it were easier to use sbuild with a gitish
> downstream workflow which does not produce "3.0 (quilt)" source
> packages.
>
> [snip]
>
> The above attempt will probably fail.
>
> This is because the package "foo" is probably "3.0
4 matches
Mail list logo
