Your message dated Fri, 12 Feb 2021 22:41:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#982646: routine-update errors out with message "E:
Uscan did not return tarball name"
has caused the Debian Bug report #982646,
regarding routine-update errors out with message "E: Uscan did not return
tarball name"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
982646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982646
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: routine-update
Version: 0.0.6
Severity: normal
Dear people,
I'm using routine-update to automate some packaging of mine and, while I'm
still adapting, it works great.
That being said, I'm getting the following error message when I invoke
routine-update on a package where I'm working:
,----[ routine-update ]
| gbp:info: Fetching from default remote for each branch
| gbp:info: Branch 'master' is already up to date.
| gbp:info: Branch 'upstream' is already up to date.
| 6b28db3bf21694f2dff16e367e17d19cefe2470e
| E: Uscan did not return tarball name
`----
In fact, I have already run routine-update, but stopped to change some stuff
manually (nothing that I believe that would affect the way that it works)
and routine-update had already imported the newest version of the tarball.
The output that I get from uscan is:
,----[ uscan --report-status ]
| uscan info: uscan (version 2.20.5) See uscan(1) for help
| uscan info: Scan watch files in .
| uscan info: Check debian/watch and debian/changelog in .
| uscan info: package="jbig2enc" version="0.29+dfsg1-1~1.gbp7c61b3" (as seen in
debian/changelog)
| uscan info: package="jbig2enc" version="0.29+dfsg1" (no epoch/revision)
| uscan info: ./debian/changelog sets package="jbig2enc" version="0.29+dfsg1"
| uscan info: Process watch file at: debian/watch
| package = jbig2enc
| version = 0.29+dfsg1
| pkg_dir = .
| uscan info: opts:
dversionmangle=s/\+dfsg\d*$//,repacksuffix=+dfsg1,filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/jbig2enc-$1\.tar\.gz/
| uscan info: line: https://github.com/agl/jbig2enc/tags .*/v?(\d\S+)\.tar\.gz
| uscan info: Parsing dversionmangle=s/\+dfsg\d*$//
| uscan info: Parsing repacksuffix=+dfsg1
| uscan info: Parsing
filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/jbig2enc-$1\.tar\.gz/
| uscan info: line: https://github.com/agl/jbig2enc/tags .*/v?(\d\S+)\.tar\.gz
| uscan info: Last orig.tar.* tarball version (from debian/changelog):
0.29+dfsg1
| uscan info: Last orig.tar.* tarball version (dversionmangled): 0.29
| uscan info: Requesting URL:
| https://github.com/agl/jbig2enc/tags
| uscan info: Matching pattern:
| (?:(?:https://github.com)?\/agl\/jbig2enc\/)?.*/v?(\d\S+)\.tar\.gz
| uscan info: Found the following matching hrefs on the web page (newest first):
| https://github.com/agl/jbig2enc/archive/0.29.tar.gz (0.29) index=0.29-1
| https://github.com/agl/jbig2enc/archive/0.29.tar.gz (0.29) index=0.29-1
| https://github.com/agl/jbig2enc/archive/0.28-dist.tar.gz (0.28-dist)
index=0.28-dist-1
| https://github.com/agl/jbig2enc/archive/0.28-dist.tar.gz (0.28-dist)
index=0.28-dist-1
| https://github.com/agl/jbig2enc/archive/0.28.tar.gz (0.28) index=0.28-1
| https://github.com/agl/jbig2enc/archive/0.28.tar.gz (0.28) index=0.28-1
| https://github.com/agl/jbig2enc/archive/0.27.tar.gz (0.27) index=0.27-1
| https://github.com/agl/jbig2enc/archive/0.27.tar.gz (0.27) index=0.27-1
| https://github.com/agl/jbig2enc/archive/0.26.tar.gz (0.26) index=0.26-1
| https://github.com/agl/jbig2enc/archive/0.26.tar.gz (0.26) index=0.26-1
| https://github.com/agl/jbig2enc/archive/0.23.tar.gz (0.23) index=0.23-1
| https://github.com/agl/jbig2enc/archive/0.23.tar.gz (0.23) index=0.23-1
| https://github.com/agl/jbig2enc/archive/0.22.tar.gz (0.22) index=0.22-1
| https://github.com/agl/jbig2enc/archive/0.22.tar.gz (0.22) index=0.22-1
| https://github.com/agl/jbig2enc/archive/0.21.tar.gz (0.21) index=0.21-1
| https://github.com/agl/jbig2enc/archive/0.21.tar.gz (0.21) index=0.21-1
| https://github.com/agl/jbig2enc/archive/0.2.tar.gz (0.2) index=0.2-1
| https://github.com/agl/jbig2enc/archive/0.2.tar.gz (0.2) index=0.2-1
| https://github.com/agl/jbig2enc/archive/0.1.tar.gz (0.1) index=0.1-1
| https://github.com/agl/jbig2enc/archive/0.1.tar.gz (0.1) index=0.1-1
| uscan info: Looking at $base = https://github.com/agl/jbig2enc/tags with
| $filepattern = .*/v?(\d\S+)\.tar\.gz found
| $newfile = https://github.com/agl/jbig2enc/archive/0.29.tar.gz
| $newversion = 0.29
| $lastversion = 0.29+dfsg1
| uscan info: Matching target for downloadurlmangle:
https://github.com/agl/jbig2enc/archive/0.29.tar.gz
| uscan info: Upstream URL(+tag) to download is identified as
https://github.com/agl/jbig2enc/archive/0.29.tar.gz
| uscan info: Matching target for filenamemangle:
https://github.com/agl/jbig2enc/archive/0.29.tar.gz
| uscan info: Filename (filenamemangled) for downloaded file:
jbig2enc-0.29.tar.gz
| uscan info: Newest version of jbig2enc on remote site is 0.29, local version
is 0.29+dfsg1
| (mangled local version is 0.29)
| uscan info: => Package is up to date from:
| => https://github.com/agl/jbig2enc/archive/0.29.tar.gz
| uscan info: Scan finished
`----
Is there anything that can be done to fix this? Am I using the tool
incorrectly?
Thanks,
Rogério Brito.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages routine-update depends on:
ii cme 1.032-1
ii devscripts 2.20.5
ii dpkg-dev 1.20.7.1
ii fakeroot 1.25.3-1.1
ii git 1:2.30.0-1
ii git-buildpackage 0.9.22
ii libconfig-model-dpkg-perl 2.143
ii lintian-brush 0.92
ii pristine-tar 1.49
ii quilt 0.66-2.1
routine-update recommends no packages.
routine-update suggests no packages.
-- no debconf information
--
Rogério Brito : rbrito@{users.sf.net,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : salsa.debian.org/rbrito :
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40gmail.com
--- End Message ---
--- Begin Message ---
Hi Rogério,
thanks for using routine-update.
On Fri, Feb 12, 2021 at 05:27:12PM -0300, Rogério Brito wrote:
>
> In fact, I have already run routine-update, but stopped to change some stuff
> manually (nothing that I believe that would affect the way that it works)
> and routine-update had already imported the newest version of the tarball.
>
> The output that I get from uscan is:
>
> ,----[ uscan --report-status ]
> ...
> | (mangled local version is 0.29)
> | uscan info: => Package is up to date from:
> | => https://github.com/agl/jbig2enc/archive/0.29.tar.gz
> | uscan info: Scan finished
> `----
>
> Is there anything that can be done to fix this? Am I using the tool
> incorrectly?
If uscan reports (correctly according your d/changelog) no new upstream
you can use
routine-update -f
(see `man routine-update`).
Hope this helps
Andreas.
--
http://fam-tille.de
--- End Message ---
