Hide Forgot
Created attachment 1221153 [details] First (incomplete) patch To be inserted after all patches already present in RHEL7 rsync spec.
Trying to push this RFE forward, I'm testing a backport of upstream commit 839dbff2aaf0277471e1986a3cd0f869e0bdda24 on latest RHEL7 package (3.0.9 based). I'm attaching my latest test patch which adds further needed parts to the adapted patch from the commit above. It compiles and runs cleanly (tested as Patch100 on a locally modified src.rpm) but does not actually enable the nanosecond mtime functionality, probably because full advertised support for protocol 31 would be needed. Is it still considered an acceptable backport for RHEL7 if I go ahead and raise the advertised protocol level? If it is not, then the only other path forward would be a package rebase (but I would need to check all the additional RHEL patches against latest upstream sources).
Successfully verified by Case Runs #16374790 (rhel-7) and #16508770 (rhel-alt-7) of TC#560838 - /CoreOS/rsync/Sanity/higher-time-precision :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: Test if rsync transfer file with same mtime attribute :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ BEGIN ] :: Transfer file :: actually running 'rsync -r -t -vv src/ dst/' sending incremental file list delta-transmission disabled for local transfer or --whole-file testfile total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 107 bytes received 105 bytes 424.00 bytes/sec total size is 0 speedup is 0.00 :: [ PASS ] :: Transfer file (Expected 0, got 0) :: [ PASS ] :: File '/var/tmp/rlRun_LOG.eqbZ2zqb' should contain '^testfile$' :: [ BEGIN ] :: Running 'rm /var/tmp/rlRun_LOG.eqbZ2zqb' :: [ PASS ] :: Command 'rm /var/tmp/rlRun_LOG.eqbZ2zqb' (Expected 0, got 0) :: [ BEGIN ] :: Get Modified time of source file :: actually running 'srcMtime=$(stat -c %y src/testfile)' :: [ PASS ] :: Get Modified time of source file (Expected 0, got 0) :: [ BEGIN ] :: Get Modified time of destination file :: actually running 'dstMtime=$(stat -c %y dst/testfile)' :: [ PASS ] :: Get Modified time of destination file (Expected 0, got 0) :: [ PASS ] :: mtime of original and transferred files should be the same (Assert: '2017-10-19 00:48:27.357782842 +0200' should equal '2017-10-19 00:48:27.357782842 +0200') 'eb7df59e-ee51-4a71-ab01-fbff72b72c6a' Test-if-rsync-transfer-file-with-same-mtime-attribute result: PASS
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0692