Package: backintime-common Version: 1.3.3-3 Severity: serious Tags: upstream Justification: Policy 3.2 X-Debbugs-Cc: fantonifa...@tiscali.it
-- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages backintime-common depends on: ii cron [cron-daemon] 3.0pl1-137 ii openssh-client 1:8.4p1-5+deb11u1 ii python3 3.9.2-3 ii python3-dbus 1.2.16-5 pn python3-keyring <none> ii rsync 3.2.3-4+deb11u1 Versions of packages backintime-common recommends: pn backintime-qt <none> Versions of packages backintime-common suggests: ii encfs 1.9.5-1+b2 ii powermgmt-base 1.36 Dear Fabio, dear Jonathan, My apologize. Because of line 65 in "config.py" [1] the binary of backintime- comman and backintime-qt will report "1.3.3-dev" as version number. The "-dev" shouldn't be there. The reasons is I misused the Release feature of GitHub. In the upstream repo the git tag "v1.3.3" do reflect the latest stable release. And that release do report the correct version string (without the "-dev" at the end). Only the source tarball in the GitHub-Release section does have the wrong version number. Please let us know how we could go on fixing this. I assume the easiest would be to clone the upstream git repo at tag "v1.3.3" and avoid using the source tarball. Beside the version number none of the code has changed. So it is just a cosmetic thing. Apologize again. We learned from this and will do it better the next time. [1] -- <https://sources.debian.org/src/backintime/1.3.3-3/common/config.py/>
