Shengjing Zhu writes ("Bug#903392: want support for packaging-only maintainer
views"):
> Here's the example for my package, which only has debian dir in
> debian-branch.
>
> https://salsa.debian.org/zhsj-guest/anbox
>
> To build, using
>
> gbp clone https://salsa.debian.org/zhsj-guest/anbox
> gbp buildpackage --git-export-dir=../build-area --git-builder=sbuild
>
> I'm not sure if I have magic gbp.conf elsewhere, so let me you if you
> can't build.
Thank you for this and your followup messages. I have now looked at
this. I think it would be very useful to enable dgit push for your
workflow and this is now much higher up on my todo list.
Thank you so much for providing a concrete helpful and clear test/use
case for me. That is invaluable.
For my reference.
I observe that in your git repository there is a tag
upstream/0.0_git20190124
and that this tag
(i) appears to contain the upstream git history
(ii) is absolutely identical to your orig tarball
anbox_0.0~git20190124.orig.tar.gz
I think you must have generated the latter with git-deborig or
something. This is good.
I intend to support this with
--quilt=packaging-git
Sean, there is of course the other possibility, where upstream is only
a tarball. I propose to intend to support this, eventually, with
--quilt=packaging-plus-tar
dgit will look for the corresponding upstream source tag with an
algorithm like git-deborig's. In case that doesn't work there will
have to be an option to specify it explicitly.
Anyone have any comments on these UI decisions ?
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
