Package: devscripts
Version: 2.25.19
Severity: normal

Dear Maintainer,

I'm trying to update my d/watch files to version 5 - it's really much more
readable.

unfortunately, i've run into the following issue:
my upstream uses tags with a 'v' prefix (e.g. 'v0.6.1'), and for whatever
reason, the gitlab-template keeps this prefix and does not allow me to strip it
away.

Consider the following d/watch:
```
Version: 5

Template: Gitlab
Dist: https://git.iem.at/pd/vstplugin
```

Running it yields:
```
uscan --package test --upstream-version 0 --report --watchfile watch
Newest version of test on remote site is v0.6.1, local version is 0
 => Newer package available from:
        => 
https://git.iem.at/api/v4/projects/485/repository/archive.tar.gz?sha=v0.6.1
```

as you can see, the upstream version is 'v0.6.1', rather than just '0.6.1'

now a version4 watchfile that looks like this:
```
version=4
opts=\
 searchmode=plain \
 https://git.iem.at/pd/vstplugin/tags?sort=updated_desc 
-/archive/v?\d[\d.-]+/vstplugin-@ANY_VERSION@@ARCHIVE_EXT@
```

works just nicely:
```
$ uscan --package test --upstream-version 0 --report --watchfile watch4
Newest version of test on remote site is 0.6.1, local version is 0
 => Newer package available from:
        => 
https://git.iem.at/pd/vstplugin/-/archive/v0.6.1/vstplugin-v0.6.1.tar.bz2
```

so the automatic mangling of upstream version seems to be broken.


it does not help, that #1116633 prevents me from using my own mangling rules.
with the patch from #1116633 applied, I could at least use
```
Version: 5

Template: Gitlab
Dist: https://git.iem.at/pd/vstplugin
Uversion-Mangle: s/v//g
```

but this really shouldn't be necessary

Reply via email to