Bug 73995 - [kdenetwork-devel] Does not work when installed with an umask of 077 and messes filesystem
Summary: [kdenetwork-devel] Does not work when installed with an umask of 077 and mess...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdenetwork
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL: http://www.tu-chemnitz.de/~ensc/dirch...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-13 17:12 UTC by Enrico Scholz
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-14 13:59:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Enrico Scholz 2002-09-13 17:12:19 UTC
Description of Problem:

Because this package contains unowned directories, they will be created
with the current umask. When having restrictive administrator settings
(umask 077) ordinary user will not have access to them and can not use
the package.

Another problem occurs when removing packages. Then orphaned directories
are remaining.

| $ rpm -qf /usr/include/kde /usr/include/kde/kmailIface.h
| file /usr/include/kde is not owned by any package
| kdenetwork-devel-3.0.3-1

IMO kdenetwork-devel should require the kdelibs-devel package which
provides /usr/include/kde.


Version-Release number of selected component (if applicable):

kdenetwork-devel-3.0.3-1


How Reproducible:

100%


Steps to Reproduce:
1. umask 077
2. make sure that kdenetwork-devel is uninstalled completely
   (rm -rf /usr/include/kde)
3. rpm -U kdenetwork-devel-3.0.3-1.i386.rpm
4. ls -l /usr/include/kde
5. try to use the programs/scripts/libraries/data of the package as
   non-root user
6. rpm -e kdenetwork-devel-3.0.3-1

Actual Results:

* at 4:
  | drwx------    2 root     root         4096 Sep 13 18:37 /usr/include/kde
* files can not be found/read at 5 and
* /usr/include/kde still exists after 6.

Comment 1 Ngo Than 2003-02-14 13:59:31 UTC
it's fixed in 3.1-2 or later.


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