Bug 13621

Summary: Final step of openldap package building fails
Product: Mageia Reporter: Gilles Allard <gilles.allard21>
Component: RPM PackagesAssignee: Buchan Milne <bgmilne>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Normal CC: luigiwalser
Version: 3Keywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: openldap-2.4.33-7.mga3.src.rpm CVE:
Status comment:

Description Gilles Allard 2014-06-30 08:58:10 CEST
Description of problem:
If rpm variable "db_internal" is set to 1 (the default value) the final step of install (between real install and packages processing (i.e. the binaries stripping)) fails for some files.
The slapd_db_* files are installed with 555 permission so that "strip" cannot rewrite them. This "555" permission is setup by the "emode" variable in db-5.1.29/build_unix/Makefile.
Possible fix:
- on line 808 of spec file, force "emode" value to 755 as an extra argument of "makeinstall_std" so that strip can process slapd_db_* files
- reset "555" permision using "%attr(555,root,root)%{_bindir}/slapd_db*" in the list of files in "openldap-servers" package.

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

How reproducible:
Easy

Steps to Reproduce:
1.Build & install openldap pkg.
2.Check error messages printed by "strip" during the "post-install" phase
3.


Reproducible: 

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

CC: (none) => luigiwalser
Assignee: bugsquad => bgmilne
Summary: Final step of package building fails => Final step of openldap package building fails

Comment 1 David Walser 2014-07-01 21:25:40 CEST
I'm tempted to mark this as INVALID, as package building definitely does not fail, as we've issued a security update for this package in the past and it built then.  In the description you posted, it sounds like you aren't saying that it actually fails, it's just that something isn't quite working as it should.  Are you saying that some of the binaries are being left with debugging symbols in them?  I ran the file command on all of the /usr/bin/slapd_db* executables from an installed openldap-servers package on Mageia 3, and it reports that they are all stripped.  What exactly is the issue here?
David Walser 2014-07-01 21:42:35 CEST

Keywords: (none) => NEEDINFO

Comment 2 Gilles Allard 2014-07-02 10:24:14 CEST
(In reply to David Walser from comment #1)
> I'm tempted to mark this as INVALID, as package building definitely does not
> fail, as we've issued a security update for this package in the past and it
> built then.  In the description you posted, it sounds like you aren't saying
> that it actually fails, it's just that something isn't quite working as it
> should.  Are you saying that some of the binaries are being left with
> debugging symbols in them?  I ran the file command on all of the
> /usr/bin/slapd_db* executables from an installed openldap-servers package on
> Mageia 3, and it reports that they are all stripped.  What exactly is the
> issue here?

Yes you are right. As a matter of fact, neither built not install failed (may be I wasn't clear enough on that point); but as I built Openldap pkg on my computer, I noticed the error message printed by strip at the end of the install procedure and tried to understand (and fix) the problem. That's the reason why I submitted this report and a suggestion for a solution (in case it might be of some interest).
Obviously, I should have mark it as "minor" instead of "normal".
Comment 3 David Walser 2014-07-02 13:50:25 CEST
That's fine, even a minor problem is worth fixing.  It still isn't clear what the problem is though.
Comment 4 Marja Van Waes 2015-03-31 16:06:19 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