Discussion:
Bug#1093081: rsync: please package rsync 3.4.0
Add Reply
Jing Luo
2025-01-15 07:00:01 UTC
Reply
Permalink
Package: rsync
Version: 3.3.0+ds1-2
Severity: wishlist

Hi!

Please package rsync 3.4.0 because 3.3.0 is a little old.


-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.11.7-amd64 (SMP w/128 CPU threads; PREEMPT)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 rsync depends on:
ii init-system-helpers 1.68
ii libacl1 2.3.2-2+b1
ii libc6 2.40-5
ii liblz4-1 1.9.4-4
ii libpopt0 1.19+dfsg-2
ii libssl3t64 3.3.2-2
ii libxxhash0 0.8.2-2+b2
ii libzstd1 1.5.6+dfsg-2
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1

rsync recommends no packages.

Versions of packages rsync suggests:
ii openssh-client 1:9.9p1-3
ii openssh-server 1:9.9p1-3
ii python3 3.12.8-1
pn python3-braceexpand <none>

-- no debconf information
Samuel Henrique
2025-03-02 20:10:01 UTC
Reply
Permalink
Hello Arnaud,
do we still have time for that before trixie, or is it too rushed?
The changes between what we ship (a patched 3.3.0) and 3.4.1 are minimal, so we
are fine updating this up until the soft freeze at 2025-04-15.

I should be able to do it by then.
I can probably update the package, it doesn't seem too hard. Do you usually
upload to experimental first?
If you'd like to help, feel free to open an MR for the debian branch on salsa,
I would like to review it at least.

Just pay attention to the fact that we need to update d/u/signing-key.asc with
the new key being used by upstream.

We will also need to do a full re-check of d/copyright now that upstream added
the "XXHASH exception" to "COPYING" and updated some years.

The current d/copyright should be 100% correct for 3.3.0, so we're only looking
at the diff introduced by the new release, although the new changes on
"COPYING" requires re-checking all files again since any file that explicitly
mentions a license without the exception should not fall under what's in
"COPYING".

Cheers,


--
Samuel Henrique <samueloph>
Samuel Henrique
2025-03-03 21:10:01 UTC
Reply
Permalink
Hello Arnaud,
I see that the upstream branch was messed up, two old versions were
imported on top of 3.3.0+ds1 (3.1.2 and 3.1.1).
Ouch, we've had an issue with a contribution where the person had trouble
importing a dsc into the repo, I did not realize that the upstream branch got
messed up as well, it also looks like the tags for old releases are gone :(.

The thing I said about changes to COPYING is wrong, as I was looking at a diff
between 3.4.1 and 3.1.2, so forget about that.
Do you want to remove those two commits and force-push? Alternatively I
can re-import 3.3.0 on top of it, before importing 3.4.1.
Otherwise when I import 3.4.1, what I see with git is the diff between
3.1.1 and 3.4.1 -- not helpful.
I've pushed a commit that manually reverts the last 2 upstream commits, let me
know if that is enough.

Cheers,
--
Samuel Henrique <samueloph>
Loading...