Your message dated Mon, 18 May 2026 14:54:59 +0000
with message-id <[email protected]>
and subject line Solved by explaining behavior
has caused the Debian Bug report #605990,
regarding POSIX: the use of slash "/" is tremendously confusing for users
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.)
--
605990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605990
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsync
Version: 3.0.7-2
Severity: important
Hello,
This a report that most of users may have experienced, at least once, with rsync
the use of slash "/" for defining the folder is not trivial, or not without
consequences.
If the use use the regular folder rules, then one can end up into backing up or
losses of data or directory tree.
I would just like to notice it. I am worry about data losses for some users,
thus that explains this bug report.
Thanks for developing for Linux. It is great to give for all of us the chance
to use Linux.
Kind regards
F.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rsync depends on:
ii base-files 5.10 Debian base system miscellaneous f
ii libacl1 2.2.49-4 Access control list shared library
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libpopt0 1.16-1 lib for parsing cmdline parameters
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:5.5p1-6 secure shell (SSH) client, for sec
ii openssh-server 1:5.5p1-6 secure shell (SSH) server, for sec
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
it seems the issue is solved several years ago by explaining why the
behavior exists.
There is also no way this would change in the future.
Therefore, closing it.
Regards,
Christian Buhtz
--- End Message ---
