Package: jigdo-file
Version: 0.8.1-1+b1
Severity: minor
X-Debbugs-Cc: budheal...@gmail.com
Dear Maintainer,
* What led up to the situation?
In bookworm, jigdo-lite messages are obviously changed. In bullseye, the most
obvious change was (see Bug#988120) the failure to reuse the scan cache, making
it worth to keep a machine running buster, which finishes much faster than
bullseye running on a SSD.
The changes for bookworm may help others but not my paltry bandwidth. I am not
about to offer a patch here, but it was worth a look at the sources.
* What exactly did you do (or not do) that was effective (or
ineffective)?
So I checked the versions (jigdo-file --version, jigdo-lite -v) and found the
versions on bookworm and bullseye are reported as 0.8.0. cmp quickly reports
that the respective binaries (and the jigdo-mirror scripts too) differ.
* What was the outcome of this action?
So I looked in the online sources and found only one apparent place
self-reporting the version:
jigdo.spec:%define version 0.8.0
* What outcome did you expect instead?
jigdo-file and jigdo-lite should report the right version.
I am noticing that such minor inaccuracies can compound to where in the next
major release, chaos can become difficult to rein in. Hence this report.
-- System Information:
Debian Release: 12.0
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages jigdo-file depends on:
ii libbz2-1.0 1.0.8-5+b1
ii libc6 2.36-9
ii libdb5.3 5.3.28+dfsg2-1
ii libgcc-s1 12.2.0-14
ii libstdc++6 12.2.0-14
ii wget 1.21.3-1+b2
ii zlib1g 1:1.2.13.dfsg-1
jigdo-file recommends no packages.
jigdo-file suggests no packages.
-- no debconf information
