Bug 1486364 - cpio does not preserve soft link time
Summary: cpio does not preserve soft link time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cpio
Version: 32
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Dubaj
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1487673
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-29 15:00 UTC by Pat Riehecky
Modified: 2020-09-24 06:11 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-24 06:11:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Riehecky 2017-08-29 15:00:37 UTC
Description of problem:
When extracting a cpio archive and attempting to preserve timestamps, the timestamps of soft links are not preserved.

This results in erroneous date differences between the cpio archive and its extracted content.

Version-Release number of selected component (if applicable):
cpio-2.12-4.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
1.cd /usr/lib
2.find . -depth -print0 | cpio --null -pmvd /tmp/test.cpio
3.ls -l /usr/lib
4.ls -l /tmp/test.cpio

Actual results:
timestamp for normal files and directories is preserved, but not for soft links

Expected results:
timestamp for all files preserved

Additional info:
Example file /usr/lib/issue

Comment 1 Pavel Raiskup 2017-08-29 16:58:39 UTC
Hi Pat, confirmed.  Thanks for the report.

Comment 2 Pavel Raiskup 2017-09-02 08:27:34 UTC
Upstream proposal:
http://www.mail-archive.com/bug-cpio@gnu.org/msg00605.html

Comment 3 Pavel Raiskup 2018-01-03 08:41:11 UTC
Ping here:
https://www.mail-archive.com/bug-cpio@gnu.org/msg00613.html

Comment 4 Fedora End Of Life 2018-02-20 15:21:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 5 Pavel Raiskup 2018-08-23 13:37:33 UTC
Ping again:
https://www.mail-archive.com/bug-cpio@gnu.org/msg00620.html

Comment 6 Ben Cotton 2019-05-02 19:47:18 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2019-08-13 17:09:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 8 Ben Cotton 2019-08-13 19:21:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 9 Ondrej Dubaj 2020-04-09 09:04:24 UTC
This issue is not fixed in upstream yet, as this bug appears also in fedora-rawhide, which has the current released version.

Comment 10 Ondrej Dubaj 2020-08-25 05:41:50 UTC
Issue already fixed in f32, f33, f34, no response from upstream yet

Comment 11 Ondrej Dubaj 2020-08-25 05:44:50 UTC
No issues seemed to occur with this downstream patch in fedora

Comment 12 Ondrej Dubaj 2020-09-24 06:11:04 UTC
Working


Note You need to log in before you can comment on or make changes to this bug.