Hi Marc,
Your current watch file (as of a few minutes ago) is fine so don't
change anything. What happened in your previous attempt is that you
declared two conflicting sources for the same tarball:
Le 2025-08-27 20:35, Marc Haber a écrit :
| Version: 5
| | Template: Github
| Owner: dlundquist
| Project: sniproxy
| | Source: https://github.com/dlundquist/sniproxy.git
| Matching-Pattern: HEAD
| Mode: git
| Filename-Mangle: s/^(@PACKAGE@)-0\.0/$1-0.6.2/
This appears in gbp's debug output as:
| uscan warn: more than one main upstream tarballs listed.
and relevant lines in uscan's debug output, first looking at the
template source (HTTP):
| uscan info: package="sniproxy" version="0.6.1+git20250616-1~" (as
seen in debian/changelog)
| uscan info: package="sniproxy" version="0.6.1+git20250616" (no
epoch/revision)
| uscan info: ./debian/changelog sets package="sniproxy"
version="0.6.1+git20250616"
|
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.6.1
(0.6.1) index=0.6.1-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.6.0
(0.6.0) index=0.6.0-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.5.0
(0.5.0) index=0.5.0-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.4.0
(0.4.0) index=0.4.0-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.6
(0.3.6) index=0.3.6-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.5
(0.3.5) index=0.3.5-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.4
(0.3.4) index=0.3.4-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.3
(0.3.3) index=0.3.3-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.2
(0.3.2) index=0.3.2-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3.1
(0.3.1) index=0.3.1-0 |
https://api.github.com/repos/dlundquist/sniproxy/git/refs/tags/0.3
(0.3) index=0.3-0 | uscan info: Looking at $base =
https://api.github.com/repos/dlundquist/sniproxy/git/matching-refs/tags/
with
| $newversion = 0.6.1
| $lastversion = 0.6.1+git20250616
| uscan info: Newest version of sniproxy on remote site is 0.6.1, local
version is 0.6.1+git20250616
| uscan info: => Only older package available from:
| =>
https://api.github.com/repos/dlundquist/sniproxy/tarball/refs/tags/0.6.1
so no tarball was downloaded, and then from the second source (git):
| uscan warn: more than one main upstream tarballs listed.
[Devscripts::Uscan::WatchSource: 614]
| Newest version of sniproxy on remote site is
0.6.2~git20240702.2d99653, local version is 0.6.1+git20250616
| => Newer package available from:
| => https://github.com/dlundquist/sniproxy.git HEAD
| uscan debug: line: download_file_and_sig()
| uscan debug: line: mkorigtargz()
| uscan debug: Keep git repo (../sniproxy-temporary.358789.git)
the new version was actually found, but no tarball was generated,
because the download flag in uscan's code was reset by the first source
not going on with a download. This could be considered a bug (not sure
it's worth reporting or fixing though), or as some say "unspecified
behaviour" resulting from the conflicting sources.
Hope this sheds some light on uscan mysteries.
Cheers,
--
Julien Plissonneau Duquène
