Bug 8168

Summary: Build dependency error
Product: Mageia Reporter: Richard Houser <rick>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: rick
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: firefox-17.0-2.mga3.src.rpm CVE:
Status comment:

Description Richard Houser 2012-11-21 07:07:36 CET 
Description of problem:

I attempted to re-build this package use on a Mageia 2 distro, and it failed.  This box is fully patched from Mageia 2, plus a a few odds and ends from Cauldron.


checking for nss-config... /usr/bin/nss-config
checking for NSS - version >= 3.13.2... no
configure: error: you don't have NSS installed or your version is too old

I have 3.14 installed (release 1), and that's the same version that /usr/bin/nss-config reports.  I looked into the configure script, and it's trying to parse a non-existant micro version number, resulting in only the first digit getting read out of the minor.  To find the location in question, search for "nss_config_minor_version=".



How reproducible:

100%.


Steps to Reproduce:

1. rpmbuild --rebuild on an appropriate system
Richard Houser 2012-11-21 07:10:23 CET

CC: (none) => rick

Comment 2 Richard Houser 2012-11-21 17:44:16 CET 
Firefox 10.0 goes out of support before Mageia 3 gets released, so I would think the distro plan would be to follow the upgrade path to the next esr release.  If that is the case, the new firefox package should also build on Mageia 2 without a lot of hoops.

I had looked into upgrading nss to the -3 release from cauldron prior to submitting the report, but that requires an update to "filesystem", which in turn requires "rpmlib(X-CheckUnifiedSystemdir)", etc.

If the problem is actually with nss, I would think that should get an update backported to Mageia 2 and the firefox package should have a (Build)Requires or Conflicts that filters out the problem packages.

If the problem is just with the nss build-time detection in firefox (my suspicion), I think it would just be a simple patch to the configure script.  If that's the right approach, I could certainly submit something.


Btw, I'm looking for a mentor if any existing packagers have free time for vetting.  I didn't receive a response from the first three I contacted.
Comment 3 Manuel Hiebel 2012-11-25 11:55:58 CET 
firefox 17 is in testing, so the srpms from 2/updates_testing should works fine

>Btw, I'm looking for a mentor if any existing packagers have free time for
>vetting.  I didn't receive a response from the first three I contacted.

try again on the ml maybe.

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