Bug 442672 - Evolution28 needs to build against system nss package in rhel-4.7
Evolution28 needs to build against system nss package in rhel-4.7
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: evolution28 (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Martin Stransky
Matthew Barnes
Depends On:
Blocks: 442690
  Show dependency treegraph
Reported: 2008-04-16 03:11 EDT by Martin Stransky
Modified: 2008-04-17 11:44 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-17 11:44:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Stransky 2008-04-16 03:11:37 EDT
Description of problem:

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

NSS has been moved from seamonkey to stand-alone package in RHEL-4.7 and updated
to 3.12. All applications what build against it have to be updated.

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 RHEL Product and Program Management 2008-04-16 03:49:36 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 2 Matthew Barnes 2008-04-16 06:17:49 EDT
Cloned this bug for evolution28-evolution-data-server (bug #442690).
Comment 3 Martin Stransky 2008-04-16 12:06:01 EDT
Evolution28 seems to build fine against the new nss/nspr packages. We don't need
to rebuild it then...
Comment 4 Kai Engert (:kaie) 2008-04-17 11:05:53 EDT
Martin, do you want to close this bug?
Comment 5 Martin Stransky 2008-04-17 11:44:37 EDT
Yes, we can close it.

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