From: r2-d2@outer.space   
      
   R2-D2 wrote on 2/27/22 21:39:   
   > Lew Pitcher wrote on 2/25/22 14:55:   
   >> On Thursday, 24 February 2022 at 04:02:27 UTC-5, R2-D2 wrote:   
   >>> Local machine just upgraded from 14.2 to 15.0. Rsync package version   
   >>> 3.2.3-x86_64-4.   
   >>>   
   >>> Remote machine still on 14.2, rsync package version   
   >>> 3.1.3-x86_64-1_slack14.2.   
   >>>   
   >>> I have a directory on the remote machine that has always been backed up   
   >>> locally with rsync. After switching to 15 every single file "is newer" on   
   >>> the local machine, where it has always been "is uptodate".   
   >>>   
   >>> $ rsync -arvvtu --delete user@remote:/remotedir/ /localdir   
   >>>   
   >>> The files are identical, their timestamps are identical to the nanosecond.   
   >>> Any clue? Idiosyncrasies between different rsync versions?   
   >>>   
   >>> Thanks.   
   >>   
   >>   
   >> Apparently, idiosyncratic behavior that is corrected in the next upstream   
   >> release of rsync.   
   >>   
   >> See https://download.samba.org/pub/rsync/NEWS   
   >>   
   >> "Fixed --update -vv to output "is uptodate" instead of "is newer" messages   
   >> for files that are being skipped due to an identical modify time. (This was   
   a   
   >> new output quirk in 3.2.3.)"   
   >   
   > Excellent news, thanks. I'll sit tight, looking forward to see   
   > http://ftp.slackware.com/pub/slackware/slackware-15.0/slackwar   
   /n/rsync-3.2.3-i586-4.txz   
   > replaced by 3.2.4.   
      
   3.2.4 came out a month ago:   
   https://download.samba.org/pub/rsync/NEWS#3.2.4   
   but it hasn't made its way into the slackware-15.0 repo yet. I guess it's time   
   to learn to build my own packages. :-)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)