Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1050163

Summary: Same files in two rpms create rpm conflict
Product: Red Hat Enterprise Linux 7 Reporter: Zenon Panoussis <redhatbugs>
Component: nssAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED CURRENTRELEASE QA Contact: Aleš Mareček <amarecek>
Severity: low Docs Contact:
Priority: medium    
Version: 7.0CC: gentoo.integer, rrelyea, tis
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nss-3.15.4-5.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 09:31:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Change spec file to move 3 manpage tar archives to the main %files section
rrelyea: review+
Move sharedb files to the main package where the belong none

Description Zenon Panoussis 2014-01-08 19:20:38 UTC
rpm -qpl http://ftp.redhat.com/pub/redhat/rhel/beta/7/x86_64/os/Packages/nss-3.15.2-8.el7.i686.rpm |grep /man
/usr/share/man/man5/cert8.db.5.gz
/usr/share/man/man5/cert9.db.5.gz
/usr/share/man/man5/key3.db.5.gz
/usr/share/man/man5/key4.db.5.gz
/usr/share/man/man5/pkcs11.txt.5.gz
/usr/share/man/man5/secmod.db.5.gz

rpm -qpl http://ftp.redhat.com/pub/redhat/rhel/beta/7/x86_64/os/Packages/nss-sysinit-3.15.2-8.el7.x86_64.rpm |grep /man
/usr/share/man/man1/setup-nsssysinit.1.gz
/usr/share/man/man5/cert9.db.5.gz
/usr/share/man/man5/key4.db.5.gz
/usr/share/man/man5/pkcs11.txt.5.gz

yum will refuse to install nss-sysinit because it requires nss and the two packages conflict. rpm can only install them with --force.

Comment 2 Elio Maldonado Batiz 2014-01-09 18:54:45 UTC
This problem didn't get detected as we normally install nss and nss-sysinit together. It's very unusual that soeone would install nss without nss-sysinit and then install the attter later but it turns out it's possible and that's when this problem occurs. The files endup patched on both the nss and nss-sysinit rpm's. 

The cert9.db.5.gz, key4.db.5.gz, and pkcs11.txt.5.gz files are listed only once in nss.spec. I place them in the %files nss-sysinit section because that's where the files they document were located. If I move the files in question from the %files nss-sysinit to the main %files I that solves the problem.

Comment 3 Elio Maldonado Batiz 2014-01-09 18:57:16 UTC
Created attachment 847753 [details]
Change spec file to move 3 manpage tar archives to the main %files section

Comment 4 Zenon Panoussis 2014-01-09 21:43:17 UTC
(In reply to Elio Maldonado Batiz from comment #2)

> This problem didn't get detected as we normally install nss and nss-sysinit
> together. 

They are installed by anaconda on every new system, so yum won't ever see them unless there's an update. Or you try to initialise mock, which is how I found out.

Comment 5 Bob Relyea 2014-01-10 23:09:53 UTC
Comment on attachment 847753 [details]
Change spec file to move 3 manpage tar archives to the main %files section

r+ the man pages for these file shouldn't be in nsssysinit anyway.

Comment 6 Kanstantsin Shautsou 2014-01-12 00:24:52 UTC
This packages are pulled by BuildRequire: deps from different source packages. Such inconsistency

Comment 7 Kanstantsin Shautsou 2014-01-12 00:26:19 UTC
Please, ignore my comment or delete if you can. Save button affected not just CC. Sorry.

Comment 9 Tuomo Soini 2014-01-22 19:39:51 UTC
Actually the fix was wrong I think.

The problem is this line:

%attr(0644,root,root) %doc /usr/share/man/man5/*

Removing that fixes the issue - all man pages are listed with name so there shouldn't be wildcard inclusion.

Same problem is in fedora nss package and seame fix will remove the conflict.

Comment 10 Tuomo Soini 2014-02-03 08:58:11 UTC
I'd comment this fix is still no good. Now cert9.db and it's man page are on different package - those three man pages should be moved back to correct sub-package. Just removing the wildcard inclusion is the correct fix.

Comment 11 Elio Maldonado Batiz 2014-02-04 18:26:22 UTC
(In reply to Tuomo Soini from comment #10)
> I'd comment this fix is still no good. Now cert9.db and it's man page are on
> different package - those three man pages should be moved back to correct
> sub-package. Just removing the wildcard inclusion is the correct fix.

I agree that Just removing the wildcard inclusion is the correct fix. 

I originally placed the man pages in nss-sysinit to be next to the databses they document which are in nss-sysint.  I can move them back thre and just keep the removal of the wildcard entry.  


I'm puzzled as to why cert9.db, key4.db, and pkcs11.txt are in the nss-sysinit section rather than on main package itsef. They are part of the support for shared dn format itself and not a feature of the introduction of nss-syinit which is for a system-wide shared db. This was done years ago on fedora-12 timeframe. On F12 sysinit was disabled by default as it was considered technology preview and F-13 we enabled it by default.  Could that played part in the decision for their location on spec file?  I have searched on old fedora bugs and I haven't found one that would shed light on this. This is something I must have consulted with Bob about. 

Bob, can you think any reason for having cert9.db, key4.db, and pkcs11.txt list as files provided by the subpackage rather that the main package itself? 

By the way, I'am not proposing to change the locations now, there may be side-effects of moving files around I haven't analized. The prudent thing is to stick to Tuomo's proposal.

Comment 12 Bob Relyea 2014-02-19 01:38:57 UTC
No, they should be in the main package. That is where they are used. I think it's a mistake that they are in nss-sysinit

Comment 13 Elio Maldonado Batiz 2014-02-19 02:39:53 UTC
Created attachment 864909 [details]
Move sharedb files to the main package where the belong

Comment 15 Ludek Smid 2014-06-13 09:31:08 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.