Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 478548 - sys-devel/patch-2.7.1-r1 fails to remove empty directories if the wrong patch level is used
Summary: sys-devel/patch-2.7.1-r1 fails to remove empty directories if the wrong patch...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL: https://savannah.gnu.org/bugs/index.p...
Whiteboard:
Keywords: Tracker, UPSTREAM
: 478246 479362 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-07-29 08:52 UTC by Joshua Kinard
Modified: 2013-08-12 22:11 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Kinard gentoo-dev 2013-07-29 08:52:43 UTC
GNU Commit to 'patch' fixed part of the problem reported back in March 2013:
http://git.savannah.gnu.org/cgit/patch.git/commit/?id=2f40ef66bea54be23a24f616cde021d8d7fc25be

ML Report:
https://lists.gnu.org/archive/html/bug-patch/2013-03/msg00000.html

However, if the wrong patch level is specified when patching, patch will fail to clean up its temp working files.  This is triggered with kernel source unpacking/patching because unipatch() in kernel2.eclass takes a brute-force approach and tries to patch from -p0 until -p5 to see which patch level worked.  These empty directories are created even when --dry-run is used.

Being reported upstream and this is a tracking bug until upstream fixes.  Upstream Bug #39603.
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2013-08-01 08:56:50 UTC
*** Bug 479362 has been marked as a duplicate of this bug. ***
Comment 2 Doug Goldstein (RETIRED) gentoo-dev 2013-08-02 13:25:23 UTC
Fixed in patch-2.7.1-r2.
Comment 3 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2013-08-12 22:11:54 UTC
*** Bug 478246 has been marked as a duplicate of this bug. ***