Simon Josefsson writes ("Re: Bug#1121367: tag2upload-obtain-origs: Needs to ask
git-deborig for .gz compression"):
> I went from gbp-build-package+debsign+dput directly to tag2upload, so I
> never integrated dgit into my workflow.
Right.
> I have more NEW uploads coming up, so I will try to use 'dgit
> push-built' next time, I don't recall if I ever got dgit to build
> packages for me.
Please let us know your experience.
> > I think if we did what Sean suggests in this bug report, this would
> > work (at least, almost all of the time) - because t2u would be able to
> > reproduce the gbp-generated .orig.tar.gz.
>
> Without parsing gbp-related files, which I think you want to avoid?
> That would be nice.
I think we are probably OK parsing at least some gbp-related files.
But I don't think that's needed here, since the tag2upload service can
tell fromk the ftpmaster API that a .gz is wanted.
> >> Re 1) I have used this a couple of times now. It leads to things not in
> >> the archive showing up on browse.dgit.debian.org.
> >
> > Was this package wholly-NEW, or only NEW due to new binary packages?
>
> Wholly NEW.
>
> > The system is supposed to hide wholly-NEW packages from the public git
> > view on browse.dgit.d.o and git.dgit.d.o until they are ACCEPTed.
> > If that isn't working it needs fixing.
>
> I didn't actually check but merely assumed that it automatically
> appeared on browse.dgit.d.o. I have several NEW uploads coming, I can
> try to use the same method again and report back. Nothing beats
> throwing things at live systems.
:-).
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
