> > On Mon, 19 Sep 2022 at 18:12:15 +0200, Samuel Thibault wrote: > > julien.pu...@gmail.com, le lun. 19 sept. 2022 18:00:37 +0200, a ecrit: > > > Le lundi 19 septembre 2022 à 20:50 +0900, Hideki Yamane a écrit : > > > > Recent changes in GitHub releases pages, I cannot check upstream > > > > version with uscan. How do you deal with it? > > > > > > version=4 > > > opts="\ > > > dversionmangle=s/\+dfsg.*$//,\ > > > filenamemangle=s/.+\/[vV]?(\d\S+)\.tar\.gz/coq-$1\.tar\.gz/,\ > > > repack,repacksuffix=+dfsg,\ > > > " \ > > > https://github.com/coq/coq/tags .*/[vV]?(\d[^\s+]+)\.tar\.gz > > > > That works for the tags page, but not for the releases page... The > > problem is that the tags page only contains snapshots of the repository, > > and not an autoconf-ed tarball.
> It's quite noisy and unpleasant, but here's the best I could come up with: > > https://salsa.debian.org/debian/bubblewrap/-/blob/debian/latest/debian/watch > (my upstream here uses tags like v1.2.3, adjust as necessary if yours > doesn't) > or if you need to repack for DFSG reasons: > https://salsa.debian.org/sdl-team/libsdl2/-/blob/master/debian/watch > (in this case my upstream uses tags like release-1.2.3) > smcv I've encountered the same problem and come out with a version of the watch file using the GitHub APIs. In my case I also needed to download the PGP signature. I've add some comments to the watch file for an easier understanding. The approach should be generic enough to work for others [1]. The package name in the URL could also be replaced with @PACKAGE@ if that's the same of the GitHub project name. In my case too, tags are prefixed with a 'v' (i.e. v1.2.3), but that's easily adaptable to different formats. What is the process to find an agreement on which updated version should be published on the wiki [2] ? Thanks, Riccardo [1] https://github.com/volans-/gjson-py/blob/debian/debian/watch [2] https://wiki.debian.org/debian/watch#GitHub
