Closed #788.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/788#event-2997089861___
Rpm-maint mailing list
Looks like neither patch -T nor -Z really does what's wanted here. As there
haven't been any other suggestions for half a year I am closing this for now.
Feel free to re-open if there are better options emerging.
--
You are receiving this because you are subscribed to this thread.
Reply to
Thanks for the info. I understand it.
I simply like the behavior like `cp -p` just to preserve the timestamp.
Because it always update the file as fixed date.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
_The --set-utc (-Z) option causes patch to set a patched file’s modification
and access times to the timestamps given in context diff headers._
=>
behavior of diff file without date header
_patch normally refrains from setting a file’s timestamps if the file’s
original last-modified timestamp
I tested `patch -Z` on my local using this repository's README file.
I created below 2 files based on a result of `diff -u`.
I expected the patched file is updated as fixed value.
But actually on below cases, it is updated as system date even when using
`patch -Z`.
Just implementing `patch -Z`
> The other question is whether this should be added to _default_patch_flags in
> the long run.
This is the best solution for me if we can add it to the _default_patch_flags.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
The other question is whether this should be added to _default_patch_flags in
the long run. So instead of packager adding it all over the place it can be
enabled globally. Probably in some distribution first before changing the
upstream default.
--
You are receiving this because you are
It seems `-Z` is better than `-T`.
```
$ man patch
...
-T or --set-time
Set the modification and access times of patched files from time
stamps given in
context diff headers. Unless specified in the time stamps, assume
that the con‐
text diff headers
I wonder if using -Z is the better option when it comes to reproducibility.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Or I want an option for %patch to preserve the timestamp of the patched file
like `cp -p`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I wanted to use `patch -T` option for %patch macro, to set fixed timestamp for
a patched file.
Because It is related to reproductive build. The timestamp is used as a gz
file's metadata modified date in a program.
Is it possible to support the option?
ruby.spec
```
-%patch20 -p1
+%patch20
11 matches
Mail list logo
