Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 215234 - pam conflicts with system db4 even though it doesn't use it
pam conflicts with system db4 even though it doesn't use it
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Depends On:
Blocks: 198038
  Show dependency treegraph
Reported: 2006-11-12 13:31 EST by Jindrich Novy
Modified: 2013-07-02 19:18 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-13 16:53:47 EST
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 Jindrich Novy 2006-11-12 13:31:49 EST
Description of problem:
pam spec file contains "Conflicts: db4 >= %{db_conflicting_version}" even though
it uses its own db4, which is independent on system db4.

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

How reproducible:

Steps to Reproduce:
1. Try to install db4 with higher or equal version than is listed in the pam
spec file.
Actual results:
Update of system db4 fails due to useless conflict defined in spec file.

Expected results:
The "Conflicts:" tag is removed from the spec file. Update of system db4 passes
so that pam won't block other packages that need to be rebuilt against new
system db4.

Additional info:
The conflicts tag also makes testing of new db4 releases very hard, because
every time I want to test new db4 package in a chroot, I need to remove/update
this conflict and reinstall pam into chroot by hand.
Comment 1 Robert Scheck 2006-11-12 16:25:45 EST
Well the conflict IMHO makes sense, but the db4 copy inside of the pam package 
should be updated in Rawhide just _before_ any update of db4:

# We internalize libdb to get a non-threaded copy, but we should at least try
# to coexist with the system's copy of libdb, which will be used to make the
# files for use by pam_userdb (either by db_load or Perl's DB_File module).
Comment 2 Tomas Mraz 2006-11-13 16:53:47 EST
The conflict cannot be removed for the reasons given above.

pam- in tomorrow's rawhide contains updated db4 with the conflict
moved to 4.6.x so hopefully this problem is resolved for now.
Comment 3 Jindrich Novy 2006-11-14 00:55:00 EST
Thanks. I'm going to ping releg guys so that they move the db4/compat-db back to

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