Back to bug 1393543

Who When What Removed Added
RHEL Program Management 2016-11-10 00:30:38 UTC Keywords FutureFeature
Giuseppe Ragusa 2016-11-10 11:15:19 UTC CC giuseppe.ragusa
Tomáš Hozza 2016-11-11 12:52:01 UTC CC thozza
Assignee luhliari mruprich
Tomáš Hozza 2016-11-21 08:31:18 UTC Priority unspecified medium
Filip Krska 2016-11-28 13:01:08 UTC Blocks 1298243
Tomáš Hozza 2017-01-12 10:39:18 UTC Priority medium high
Blocks 1393869
Tomáš Hozza 2017-02-01 10:59:49 UTC Doc Type If docs needed, set a value Release Note
Tomáš Hozza 2017-03-20 08:58:32 UTC Depends On 1432899
Kotresh HR 2017-04-05 07:32:02 UTC Depends On 1439072
Rejy M Cyriac 2017-04-05 07:37:22 UTC Depends On 1439072
Lenka Špačková 2017-04-27 18:59:40 UTC Docs Contact lkimlick
Chris Van Hoof 2017-07-21 14:17:17 UTC Blocks 1473733
Chris Van Hoof 2017-08-04 16:00:15 UTC Blocks 1473733
Chris Van Hoof 2017-08-04 16:04:57 UTC Blocks 1473733
Ondrej Moriš 2017-08-18 08:36:12 UTC CC omoris
Ondrej Moriš 2017-08-28 11:52:04 UTC QA Contact qe-baseos-security mzeleny
Tomáš Hozza 2017-11-03 14:30:26 UTC Status NEW MODIFIED
Tomáš Hozza 2017-11-03 14:36:03 UTC CC salmy
Flags needinfo?(salmy)
Steve Almy 2017-11-07 16:53:21 UTC Flags needinfo?(salmy)
errata-xmlrpc 2017-11-08 08:49:05 UTC Status MODIFIED ON_QA
Lenka Špačková 2017-11-14 10:06:28 UTC Docs Contact lkimlick
Lenka Špačková 2017-11-15 14:12:50 UTC Docs Contact lmanasko
Martin Zelený 2017-11-21 15:10:35 UTC Status ON_QA VERIFIED
Fixed In Version rsync-3.1.2-4.el7
Lucie Vařáková 2017-12-01 14:03:30 UTC CC mruprich
Flags needinfo?(mruprich)
Michal Ruprich 2017-12-08 13:55:56 UTC Doc Text * Cause
Nanosecond part of the timestamp of a file was ignored when transferred with rsync.

* Consequence
The nanosecond timestamp was always zeroed out on the receiver.

* Fix
Nanosecond part of the data structure containing the timestamp is now used.

* Result
On systems, where nanoseconds are supported in timestamps, it will be transferred with the file and set appropriately.
Flags needinfo?(mruprich)
Vladimír Slávik 2017-12-11 14:42:42 UTC CC vslavik
Docs Contact lmanasko akvitek
Vladimír Slávik 2017-12-11 14:46:00 UTC CC lmanasko
Adam Kvitek 2017-12-18 15:53:27 UTC Flags needinfo?(mruprich)
Michal Ruprich 2017-12-19 09:34:03 UTC Flags needinfo?(mruprich)
Adam Kvitek 2017-12-20 13:09:11 UTC Doc Text * Cause
Nanosecond part of the timestamp of a file was ignored when transferred with rsync.

* Consequence
The nanosecond timestamp was always zeroed out on the receiver.

* Fix
Nanosecond part of the data structure containing the timestamp is now used.

* Result
On systems, where nanoseconds are supported in timestamps, it will be transferred with the file and set appropriately.
The *rsync* utility now copies files with their original nanosecond part of the time stamp

Previously, the *rsync* utility ignored the nanosecond part of the time stamp of files. As a consequence, the nanosecond time stamp of newly created files was always zero. With this update, the *rsync* utility recognizes the nanosecond part. As a result, the newly copied files keep their original nanosecond time stamp on systems that support it.
Adam Kvitek 2018-01-02 15:37:32 UTC Doc Type Release Note Bug Fix
Pasi Karkkainen 2018-01-24 20:23:31 UTC CC pasik
Lenka Špačková 2018-02-05 15:42:13 UTC Doc Type Bug Fix Release Note
Chris Van Hoof 2018-02-19 16:25:39 UTC Blocks 1546815
Chris Van Hoof 2018-02-19 16:30:04 UTC Blocks 1546815
errata-xmlrpc 2018-04-10 00:26:21 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2018-04-10 10:06:32 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2018-04-10 06:06:32 UTC
errata-xmlrpc 2018-04-10 10:07:17 UTC Link ID Red Hat Product Errata RHEA-2018:0692

Back to bug 1393543