On Sun, Jul 14, 14:56, Adam Borowski wrote > On Sun, Jul 14, 2019 at 12:28:33PM +0200, Andre Noll wrote: > > On Sat, Jul 13, 22:48, Adam Borowski wrote > > > I would gladly upload your updates, but I don't know what upstream tarball > > > to use. There's no watch file (the usual automated way to fetch one), you > > > did not provide one by uploading to mentors.d.n or some site of your own, > > > and neither did you provide instructions for some custom workflow (there > > > are > > > many of those). > > > git fetch > > git archive --prefix liblopsub-1.0.3/ origin/master | xz > > > ../liblopsub_1.0.3.orig.tar.xz > > This looks like the "git" mode of uscan; I haven't used it though as the > vast majority of my upstreams use github or something similar that offers > downloadable tarballs for tags.
We also have a gitweb instance which has the same contents as the
public git repos:
http://git.tuebingen.mpg.de/
The snapshot links of each project lets you download the tarball of
any commit. For example
wget -O liblopsub_1.0.3.orig.tar.gz
'http://git.tuebingen.mpg.de/?p=lopsub.git;a=snapshot;h=master;sf=tgz'
However, you still need to specify the name of the output file, and
the tarball will extract into a directory named lopsub-master-$SHA1,
which is probably not optimal.
> > I could certainly create the tarball and upload it somewhere for the
> > tools to to pick up, but TBH I think that's a bit pointless because
> > everybody can create the tarball from the public git repo with a
> > command like the above.
>
> Yeah, but there's no commonly agreed way to do that. Or rather, there's
> _too many_ ways, with none being dominant. And generating a bit-to-bit
> identical tarball is not as easy as it sounds.
Right. I don't know if git archive creates identical tarballs when
run from two different repos that share the same commit. The man page
does not mention anything about this.
> > My preferred choice would be to create a signed tag each time the
> > version number in debian/changelog changes, to indicate that a new
> > version should be uploaded, but I have no strong opinion in this
> > regard.
>
> That's a common and recommended workflow, although when the package can't be
> uploaded immediately (eg. NEW or sponsoring), I'd recommend leaving not
> pushing the tag until the upload is done. Thus, a finalized changelog
> version serves that purpose, yet is not immutable.
>
> > Which mechanism do you prefer to get informed about pending updates?
>
> Anything that's convenient for you; in general RFS bugs are best but some
> folks prefer other arrangements.
OK, then lets continue to use email for this. I'll always include a
suitable git archive command in the future.
Thanks
Andre
--
Max Planck Institute for Developmental Biology
Max-Planck-Ring 5, 72076 Tübingen, Germany. Phone: (+49) 7071 601 829
http://people.tuebingen.mpg.de/maan/
signature.asc
Description: PGP signature
