Package: git-remote-gcrypt
Version: 1.3-1
Severity: normal
rsync URIs
Note that the URI format for the rsync backend is, regretably,
non-standard. git-remote-gcrypt uses rsync://user@host:path
whereas plain rsync uses either user@host:path or
rsync://user@host/path.That needs to be supported for backwards compatability, I suppose, but is there any reason not to let gcrypt::rsync://user@host/path be used too? -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 git-remote-gcrypt depends on: ii git 1:2.30.0-1 ii gpg 2.2.20-1 Versions of packages git-remote-gcrypt recommends: ii curl 7.74.0-1 ii gnupg 2.2.20-1 ii rsync 3.2.3-3 Versions of packages git-remote-gcrypt suggests: pn rclone <none> -- no debconf information -- see shy jo
signature.asc
Description: PGP signature
