Your message dated Fri, 7 Oct 2016 11:39:48 +0200 with message-id <[email protected]> and subject line Re: Bug#815523: [rsync] New "copying unsafe symlink" warning after upgrade to 3.1.1 has caused the Debian Bug report #815523, regarding [rsync] New "copying unsafe symlink" warning after upgrade to 3.1.1 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.) -- 815523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815523 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: rsync Version: 3.1.1-3 Severity: normal Hello, After upgrade from 3.0.9 (Wheezy) to 3.1.1 (Jessie) my scripts started producing many "copying unsafe symlink" warnings; it is correct that all of those are unsafe symlinks, but I do use the explicit --copy-unsafe-links flag, and copying them is exactly what I want rsync to do. Why does it now spam the log about this? After some searching I found this old bug: https://bugzilla.samba.org/show_bug.cgi?id=3147 Back then the conclusion was that copying unsafe symlinks when "--copy-unsafe-links" is specified is just the normal operation of the program, and that no log message should be printed about it. So what happened here? How do I return the behavior back to how it was? -- With respect, Roman
pgpgqEHZvrmOC.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---On Mon 22 Feb 2016, Roman Mamedov wrote: > > After upgrade from 3.0.9 (Wheezy) to 3.1.1 (Jessie) my scripts started > producing many "copying unsafe symlink" warnings; > > it is correct that all of those are unsafe symlinks, but I do use the explicit > --copy-unsafe-links flag, and copying them is exactly what I want rsync to do. > Why does it now spam the log about this? >From the manpage: --info=FLAGS This option lets you have fine-grained control over the informa‐ tion output you want to see. An individual flag name may be followed by a level number, with 0 meaning to silence that out‐ put, 1 being the default output level, and higher numbers increasing the output of that flag (for those that support higher levels). Use --info=help to see all the available flag names, what they output, and what flag names are added for each increase in the verbose level. Some examples: rsync -a --info=progress2 src/ dest/ rsync -avv --info=stats2,misc1,flist0 src/ dest/ Note that --info=name’s output is affected by the --out-format and --itemize-changes (-i) options. See those options for more information on what is output and when. This option was added to 3.1.0, so an older rsync on the server side might reject your attempts at fine-grained control (if one or more flags needed to be send to the server and the server was too old to understand them). See also the "max verbosity" caveat above when dealing with a daemon. >From rsync --info=help : Options added for each increase in verbose level: 1) COPY,DEL,FLIST,MISC,NAME,STATS,SYMSAFE 2) BACKUP,MISC2,MOUNT,NAME2,REMOVE,SKIP So if you're using -v, SYMSAFE is turned on. Add --info=SYMSAFE=0 to silence messages about unsafe links. Paul
--- End Message ---
