Bug 20202 - patch-2.5.4-4 breaks traditional backup behaviour
Summary: patch-2.5.4-4 breaks traditional backup behaviour
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: patch   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-02 11:25 UTC by mikpe
Modified: 2007-04-18 16:29 UTC (History)
0 users

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


Attachments (Terms of Use)

Description mikpe 2000-11-02 11:25:37 UTC
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 12:08:44 UTC
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.