Bug 39294 - unowned directories under /usr/src/linux-%{kversion}in kernel-source RPM
unowned directories under /usr/src/linux-%{kversion}in kernel-source RPM
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
All Linux
medium Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-05-06 22:52 EDT by Ganesh Sittampalam
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-06 22:52:32 EDT
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 Ganesh Sittampalam 2001-05-06 22:52:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; I; Linux 2.4.4 i586; Nav)

Description of problem:
In kernel 2.4.2-2 (also 2.4.3-2.14.10 from rawhide), the kernel-source
binary RPM
does not own the directories /usr/src/linux-2.4.2-2/arch and include
(despite owning directories under these). Since it does own the directory
/usr/src/linux-2.4.2-2 itself, this causes an error that it cannot delete
this directory when removing the RPM.

How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh kernel-source-foo.rpm
2. rpm -e kernel-source

	

Actual Results:  [ganesh@urchin ganesh]$ sudo rpm -hiv
/archive/redhat/7.1/RedHat/RPMS/kernel-source-2.4.2-2.i386.rpm 
Password:
Preparing...                ###########################################
[100%]
   1:kernel-source          ###########################################
[100%]
[ganesh@urchin ganesh]$ sudo rpm -e kernel-source
error: cannot remove /usr/src/linux-2.4.2 - directory not empty


Expected Results:  the final error message should not happen.

Additional info:
Comment 1 Arjan van de Ven 2001-05-10 06:38:32 EDT
Ok.. I found the cause + fixed this for our next build. Thanks for the report!

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