Bug#827814: [uscan] Please always download the newest of all versions if more than one main upstream tarball is listed (i.e. consider it a feature, not a problem)
Osamu Aoki
osamuaoki at e01.itscom.net
Wed Jun 22 11:18:26 UTC 2016
Hi,
On Tue, Jun 21, 2016 at 12:31:26PM +0200, Axel Beckert wrote:
> Package: devscripts
> Version: 2.16.5
> Severity: wishlist
> File: /usr/bin/uscan
>
> Hi,
>
> I've got several upstreams which have several places where they publish tar
> balls.
>
> There are at least three kinds of cases:
>
> 1. Not that seldom it's a combination of sometimes less reliable (but
> earlier filled) developer-maintained/-centric primary server and a
> reliable mirror network.
>
> (More or less) example: screen
>
> https://ftp.gnu.org/gnu/screen/screen-([\d\.]+)\.tar\.gz
> http://download.savannah.gnu.org/releases/screen/screen-([\d\.]+)\.tar\.gz
I am aware of this type of archive (some KDE) but this is non-trivial.
The best is to loop over several URLs. That's a serious new feature.
Before adding such, watch file syntax needs to be carefully thought out.
A very good candidate for wishlist.
> 2. Another case are beta releases and final releases being in
> different directories, but I want to track both.
>
> Example: zsh
>
> http://www.zsh.org/pub/zsh-(\d[^\sd]*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz))
> http://www.zsh.org/pub/development/zsh-(\d[^\sd]*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz))
I think solution should be the same as case1.
> 3. A third case are upstreams which sometimes forget to upload
> manually build tar balls to Github, but have already tagged their
> new upstream release.
>
> Example (from a recent NMU of mine, still waiting in DELAYED/10): flashbake
>
> http://github.com/commandline/flashbake/releases /commandline/flashbake/archive/(.*)\.tar\.gz
> http://github.com/commandline/flashbake/downloads /downloads/commandline/flashbake/flashbake-(.*)\.tar\.gz
That's a bit more complicated.
> >From my point of view, these are all perfectly sane usages of more
> than one main upstream tarballs.
>
> Unfortunately, at least in the 2rd case, if the first line finds a
^^^ 3rd?
> newer version, an even newer version from the second line is ignored
> and not the newest version is downloaded.
>
> So please fully support such setups, always download the newest
> version over all download sites specificed and don't emit "uscan warn:
> more than one main upstream tarballs listed." about such setups
> anymore.
>
> Additionally, such watch files cause false positives in PTS and
> Tracker because this warning is considered to be an error by PTS and
> Tracker and shows up there as TODO. Examples:
>
> https://packages.qa.debian.org/s/screen.html
> https://tracker.debian.org/pkg/screen
> https://packages.qa.debian.org/z/zsh.html
> https://tracker.debian.org/pkg/zsh
> https://packages.qa.debian.org/f/flashbake.html
> https://tracker.debian.org/pkg/flashbake
Osamu
More information about the devscripts-devel
mailing list