Bug 64895 - Build of ncpfs writes to /sbin directory
Summary: Build of ncpfs writes to /sbin directory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ncpfs
Version: 7.3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-13 23:24 UTC by Steve Snyder
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-06-11 10:37:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Snyder 2002-05-13 23:24:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2)
Gecko/20020510

Description of problem:
In the course of building (not installing) the ncpfs-2.2.0.18-6 package, a file
is written to the /sbin directory.  Worse, it is a dangling symlink that
overwrites a valid symlink.

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


How reproducible:
Always

Steps to Reproduce:
1.On a RedHat v7.3 system run this command:

  rpm --rebuild ncpfs-2.2.0.18-6.src.rpm

2. When the build is complete you will see a new file in /sbin.  I recommend
sort the directory listing by date.


Actual Results:  After the build is complete, this file is observed in /sbin:

lrwxrwxrwx    1 root     root           45 May 12 06:09 mount.ncp ->
/var/tmp/ncpfs-2.2.0.18-root/usr/bin/ncpmount

Expected Results:  No process should write to /sbin during the build of a SRPM
package.

Additional info: The ncpfs-2.2.0.18-6.src.rpm package was gotten from the
standard RH v7.3 distribution CD.

Comment 1 Steve Snyder 2002-06-11 10:37:28 UTC
The build of this packages also writes to /usr/lib.  Specifically, the file
"libncp.a" is written to this directory in the course of the build.


Comment 2 Florian La Roche 2002-06-17 10:43:41 UTC
Fixed in release 9 or newer rpms.

Thanks,

Florian La Roche



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