Bug 129411
Summary: | Newer compat-db provides a db4 version without an explicit Provides | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeff Pitman <symbiont> |
Component: | pam | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | jbj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-10 10:33:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Pitman
2004-08-08 14:56:04 UTC
Pam should do Requires: libddb-4.1.so rather than Requires: db4 = 4.1.25 so that the requirement can be satisfied by either db4 or compat-db. Adding an additional Provides: to compat-db is likely to confuse the issue further. Hmm... the question is how the format of the db files change. See this comment in pam.spec: # 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). It means that the only reason of the Requires in the pam package is compatibility of the database files created. What db versions are file compatible? As pam doesn't really require libdb to be functional there is now rather Conflict: db4 >= 4.4.0 in the devel pam. |