Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
--- Comment #8 from Elio Maldonado Batiz <emaldona(a)redhat.com> 2009-07-27 18:44:00
I can change spec to follow the guidelines but this has nothing to do with the
problem I reported. An email sent to release-engineering automatically created
this bug report.
----- Original Message -----
From: "Dennis Gregorovic" <dgregor(a)redhat.com>
To: "Elio Maldonado" <emaldona(a)redhat.com>
Cc: "David Malcolm" <dmalcolm(a)redhat.com>, jorris(a)redhat.com,
kengert(a)redhat.com, "Scott Haines" <shaines(a)redhat.com>,
Sent: Thursday, July 23, 2009 10:25:06 AM GMT -08:00 US/Canada Pacific
Subject: Re: Changed Errata Request [RHBA-2009:8601-02] nss bug fix update
On Mon, 2009-07-20 at 12:16 -0700, Elio Maldonado wrote:
> Correcting a prior reply and adding Release Enginnering as this problem seems to be
caused by the rpm build tools.
> The URL for the latest report is
> Clicking on the Symbolic Links brings up
> which lists three dangling symbolic links. There are actually fifteen or dangling
symbolic links as I was able to verify. Nothing wrong with rpmdiff as it just detects
differences with the base for comparison.
> Kai and I investigated and found out that even the prior release had this problem
with thirty one dangling symbolic links as per his inspection!
> I did the same build but on a RHEL-5 system and the problem does not happen there.
Of course, the build must be done on a RHEL 4 machine as this is tne intended target but
we needed to investigate and rule out differences in the spec file as the cause. The tool
doing the copy is /usr/lib/rpm/find-debuginfo.sh. We believe this is a problem with the
older older version of the rpm build tools that ships with RHEL-4. The find-debuginfo.sh
doesn't seem to handle well the case where some files are copied twice which me must
do in order to replace the softoken that normally comes with the latest NSS with the older
softokn that's FIPS certified. If you wish more details Kai will be able to explain
his diagnostic more clearly than I can.
> From our investigation we think that the problem is caused by the older version of
the RPM build tools in RHEL-4.
To get this fixed, we would need to get a bug filed against the RPM
component and for that bug to get approved. Given that RHEL 4 is
nearing its end of life and that this issue does not affect most
packages, I think our best course of action is to live with the dangling
symlinks. However, if the dangling symlinks present too much of a
problem, we can see about getting RPM fixed.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.