Bug 13623 - Wrong permission for mount.nfs during install
Summary: Wrong permission for mount.nfs during install
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-30 11:18 CEST by Gilles Allard
Modified: 2015-03-31 16:05 CEST (History)
0 users

See Also:
Source RPM: nfs-utils-1.2.7-3.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Gilles Allard 2014-06-30 11:18:49 CEST
Description of problem:
Install of nfs-utils package creates a "%{buildroot}/sbin/mount.nfs" with permission 4555 so that strip cannot rewrite it during post %install phase : stripping fails
Possible solution :
- add "chmod 755 %{buildroot}/sbin/mount.nfs" at the end of spec file
- restore the initial 4555 permission using "%attr" in files list of the main package ("%attr(4555,root,root)	/sbin/mount.nfs")

Version-Release number of selected component (if applicable):
nfs-utils-1.2.7-3.mga3

How reproducible:
Easily during install

Steps to Reproduce:
1. Build & install nfs-utils package
2. Check error message printed by strip during post %install phase
3.


Reproducible: 

Steps to Reproduce:
David Walser 2014-06-30 13:31:41 CEST

Assignee: bugsquad => guillomovitch

Comment 1 Marja Van Waes 2015-03-31 16:05:30 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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