Simon Josefsson writes ("Bug#1143850: tag2upload pristine-tar with gbp
import-orig filter?"):
> Quoting debian/watch:
>
> Version: 5
> Source: https://secure.nic.cz/files/knot-dns/
> Matching-Pattern:
> (?:|.*/)knot(?:[_\-]v?|)(\d\S*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz)
> Dversionmangle: s/\+hotfix//
> Pgpsigurlmangle: s/$/.asc/
> Uversionmangle: s/-((alpha|beta|rc)\d*)$/~$1/
>
> So that fetches the "real" upstream tarball with PGP signature. I think
> it puts the unfiltered tarball into the pristine-tar branch.
OK.
> Which filters out files when doing the git import.
>
> Is this mode supported?
I think the result of this is that the pristine-tar branch specifies
a tarball which is not the one you want to use.
Is that right? What .orig are you expecting? How are you expecting
the tag2upload service to generate it?
When we designed the tag2upload pristine-tar support we assumed that
the presence of data for foo_NNN.orig.tar.gz in the pristine-tar
branch meant that you want to use that foo_NNN.orig.tar.gz as your
.orig.tar.gz.
There is not currently any way to disable the pristine-tar support in
git-debpush. Probably there should be such a thing for use as a
workaround but we should consider how to detect this scenario.
Reading gbp.conf and trying to second-guess its behaviour doesn't seem
like a good idea.
We could detect that the .id file in the pristine-tar data is
different to the upstream/NNNN tag. But how would we know that the
upstream/NNNN tag is to be preferred?
Ian.
