Your message dated Mon, 3 Nov 2025 18:14:20 +0100
with message-id <[email protected]>
and subject line Re: Bug#1119954: routine-update: The version passed for the
tarball is an erroneous duplication
has caused the Debian Bug report #1119954,
regarding routine-update: The version passed for the tarball is an erroneous
duplication
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.)
--
1119954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119954
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: routine-update
Version: 0.2.4
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Was about to run routine-update on a local checkout of the apache-arrow
source tree as team-maintained on salsa/science-team.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran "routine-update" (no arguments) from the root of the apache arrow
source tree.
* What was the outcome of this action?
$ routine-update
I: Retrieved latest version via 'gbp pull'
gbp:info: Fetching from default remote for each branch
gbp:info: Branch 'upstream' is already up to date.
gbp:info: Branch 'master' is already up to date.
gbp:info: Branch 'pristine-tar' is already up to date.
089e672e6fcb4833e079e35156d0f8ea260b4b2d
I: Running uscan to test for new upstream releases
uscan warn: Possible OpenPGP signature found at:
https://dist.apache.org/repos/dist/release/arrow/arrow-rs-57.0.0/apache-arrow-rs-57.0.0.tar.gz.asc
* Add opts=pgpsigurlmangle=s/$/.asc/ or opts=pgpmode=auto to debian/watch
* Add debian/upstream/signing-key.asc.
See uscan(1) for more details
gpgv: Signature made Mon 20 Oct 2025 15:51:53 BST
gpgv: using RSA key A2AC7132B5DA7C273A7A147665F4A8CA9769ECD7
gpgv: Good signature from "Apache Arrow Automated Release Signing
<[email protected]>"
=> Newer package available from:
=>
https://dist.apache.org/repos/dist/release/arrow/arrow-rs-57.0.0/apache-arrow-rs-57.0.0.tar.gz
--
Successfully symlinked ../apache-arrow-rs-57.0.0.tar.gz to
../apache-arrow_rs-57.0.0.orig.tar.gz.
uscan info: New orig.tar.* tarball version (after mk-origtargz): rs-57.0.0
--
=> Newer package available from:
=>
https://dist.apache.org/repos/dist/release/arrow/arrow-22.0.0/apache-arrow-22.0.0.tar.gz
--
Successfully symlinked ../apache-arrow-22.0.0.tar.gz to
../apache-arrow_22.0.0.22.0.0.orig.tar.gz.
uscan info: New orig.tar.* tarball version (after mk-origtargz):
22.0.0.22.0.0
* What outcome did you expect instead?
The new version should be 22.0.0 not 22.0.0.22.0.0.
-- System Information:
Debian Release: forky/sid
APT prefers oldstable-security
APT policy: (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages routine-update depends on:
ii cme 1.041-1
ii debputy-lsp 0.2.2
ii devscripts 2.25.22
ii dpkg-dev 1.22.21
ii fakeroot 1.37.1.2-1
ii git 1:2.51.0-1
ii git-buildpackage 0.9.38
ii gobject-introspection 1.86.0-6
ii jq 1.8.1-4
ii libconfig-model-dpkg-perl 3.015
ii licenserecon 8.1
ii lintian-brush 0.162
ii pristine-tar 1.50+nmu2
ii quilt 0.68-1
routine-update recommends no packages.
routine-update suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> https://salsa.debian.org/science-team/arrow/-/blob/master/debian/watch?ref_type=heads
>
> Had not thought about that, have not seen anything immediate at fault either,
> though :-/
$ uscan --verbose --report
...
$newfile =
https://dist.apache.org/repos/dist/release/arrow/arrow-22.0.0/apache-arrow-22.0.0.tar.gz
$mangled_newversion = 22.0.0.22.0.0
$newversion = 22.0.0.22.0.0
$lastversion = 21.0.0
uscan info: Matching target for downloadurlmangle:
https://dist.apache.org/repos/dist/release/arrow/arrow-22.0.0/apache-arrow-22.0.0.tar.gz
uscan info: Upstream URL(+tag) to download is identified as
https://dist.apache.org/repos/dist/release/arrow/arrow-22.0.0/apache-arrow-22.0.0.tar.gz
uscan info: Filename (filenamemangled) for downloaded file:
apache-arrow-22.0.0.tar.gz
Newest version of apache-arrow on remote site is 22.0.0.22.0.0, local version
is 21.0.0
=> Newer package available from:
=>
https://dist.apache.org/repos/dist/release/arrow/arrow-22.0.0/apache-arrow-22.0.0.tar.gz
So that's definitely not routine-update's fault thus closing the bug.
Watch file is fixed in latest commit.
Hope his helps
Andreas.
--
https://fam-tille.de
--- End Message ---
