Bug 1408964
| Summary: | RFE: Add Provides: nss_db to the glibc rpm | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Piyush Bhoot <pbhoot> |
| Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
| Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> |
| Severity: | low | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | low | ||
| Version: | 7.4 | CC: | ashankar, codonell, cww, fweimer, mcermak, mnewsome, pfrankli, vslavik |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glibc-2.17-256 | Doc Type: | Enhancement |
| Doc Text: |
_nss_db_ packaging dependency now provided by _glibc_ package
To enable an easier transition from the _nss_db_ component in RHEL 6 to the newer `nss_db` service module provided by the *glibc* package in RHEL 7, the _glibc_ package now provides `nss_db` in order to satisfy the dependencies of any packages that previously depended on _nss_db_.
Note that it is still necessary to rebuild the `nss_db` database after migration, because the on-disk format changed:
$ cd /var/db
$ rm -f *.db
$ make
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-30 09:36:24 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1420851, 1473733, 1477664, 1505884, 1546815 | ||
|
Description
Piyush Bhoot
2016-12-28 14:40:17 UTC
The request seems reasonable, but there is a caveat: The implementation and the file format differ radically between the versions in Red Hat Enterprise Linux 6 and 7. Therefore, installations using nss_db will not have a completely seamless upgrade path even if we add the provides. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3092 |