Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.slackware    |    I think its the one without Selinux crap    |    87,272 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 85,693 of 87,272    |
|    Lew Pitcher to All    |
|    Re: weird rsync behaviour after switch t    |
|    25 Feb 22 05:55:46    |
      From: lew.d.pitcher@gmail.com              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.)"              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca