Bug 20202 - patch-2.5.4-4 breaks traditional backup behaviour
patch-2.5.4-4 breaks traditional backup behaviour
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: patch (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-11-02 06:25 EST by mikpe
Modified: 2007-04-18 12:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-11-02 06:25:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mikpe 2000-11-02 06:25:37 EST
Traditionally, patch -b would produce a backup file with suffix .orig.
According to the patch-2.5.4-4 man page, this is still true.
However, /usr/bin/patch (as shipped in RH7) instead uses an ugly
unnumbered "~" suffix; i.e. foo's backup file is foo~ not foo.orig.
This occurs on an ext2 file system, so the name length rule doesn't apply.
And no, I don't have SIMPLE_BACKUP_SUFFIX set in my environment.

As someone who has been doing a _lot_ of diff and patch the last
12+ years, I find this change extremely distasteful.
Comment 1 Tim Waugh 2000-11-02 07:08:44 EST
Indeed.  Fixed in patch-2.5.4-7, which should show up in Rawhide next time it's
generated.

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