On Mon, Jul 06, 2026 at 01:34:30AM +0200, Michael Biebl wrote: > Package: devscripts > Version: 2.26.9 > Severity: normal > File: /usr/bin/uscan > > Hi, > > I've tried to update the following watch file > > version=4 > opts="searchmode=plain" \ > https://api.github.com/repos/storaged-project/udisks/releases \ > > https://github.com/storaged-project/udisks/releases/download/udisks-(?:\d[\d.]*)/udisks@ANY_VERSION@@ARCHIVE_EXT@ > ... > using the new, template based approach in version 5: ... > I.e., it prefers the strongest compression it finds. In this case bz2 ... > > In contrast, v5 produces: ... > $newfile = > https://api.github.com/repos/storaged-project/udisks/tarball/udisks-2.11.1 ... > So, v5 would download a .gz tarball. > > Is this a deliberate decision of v5? If so why? > If not, could it be changed to behave more like @ARCHIVE_EXT@ in v4.
Hi, Michael, With 'Release-Mode: yes' github template uses what AFAIK is the only path useful for all projects. With it, is github who creates the compressed tarball (and uses .tar.gz). Some projects provide explicit tarballs with other compressions (and naming schemes), but I think there is no uniform way to reach them (I think I even saw some projects where tarballs are behind nested dynamically generated json files). This is also a problem with tarball signatures, where there is no single way to find them. Regards, -- Agustin
