On Sun, Aug 25, 2013 at 08:11:56PM +0100, Ian Jackson wrote:
> Steve Langasek writes ("Re: Introducing dgit - git integration with the Debian archive"):
> > I don't think "removing the automatic importer" is an improvement at all.
> I agree. Except that I wanted something I could deploy and use
> immediately. Providing an automatic importer would involve
> suddenly dumping the whole archive into alioth, which is not something
> I should do without consultation. (It looks like the alioth admins
> are very busy or away right now.)
> However, dgit's design certainly doesn't forbid having an automatic
> importer. Indeed there's a nice hole where the automatic importer
> would sit, and most of the code necessary is already present.
Right. Getting this going manually is an important first stepping stone on
the path; I just wanted to make sure we weren't stopping short of the real
goal.
If anything, the problems with the UDD automatic importer can be summarized
as: the importer is /not automatic enough/.
> > > And one is free to push pristine-tar (if makes sense/easy to
> > > generate), and/or any other branches into the repository (git-dpm,
> > > git-quilt, etc)
> > I would have expected dgit to support pristine-tar
> > directly/automatically/unconditionally. Any system that requires me to
> > download the same information (== the upstream source) both from a VCS
> > repository and the archive in order to get a fully-formed source package for
> > upload is a non-starter.
> I'm afraid you'll have to wait for dgit to be enhanced to treat
> .orig tarballs specially, then.
That's fine, I don't mind waiting, just as long as this is on the roadmap.
:-)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature