On Sat, Jul 13, 22:48, Adam Borowski wrote > On Sat, Jul 13, 2019 at 03:09:49PM +0200, Andre Noll wrote: > > I've merged the commit and bumped the Debian version number. Adam: > > would you please upload lopsub-1.0.3-2? This version corresponds to > > the current master branch of the public repo. > > 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).
Sorry for not being clear. You can create the tarball with
git fetch
git archive --prefix liblopsub-1.0.3/ origin/master | xz >
../liblopsub_1.0.3.orig.tar.xz
But yes, that's tedious and error prone.
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. The only thing that needs to be communicated is
a git tree-ish, i.e. an identifier for the tree that should be tared,
origin/master in this case.
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.
Which mechanism do you prefer to get informed about pending updates?
Best
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
