From Fedora Project Wiki
< Changes
(Postponed to F25 https://bugzilla.redhat.com/show_bug.cgi?id=1303542#c3) |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= | = NewRpmDBFormat = | ||
== Summary == | == Summary == | ||
| Line 25: | Line 25: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/25 | Fedora 25 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 35: | Line 35: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303542 #1303542] | ||
Due to unexpected technical challenges we postpone this Change one release to F25. | |||
== Detailed Description == | == Detailed Description == | ||
| Line 86: | Line 88: | ||
* Update to (not yet available) rpm and libsolv version | * Update to (not yet available) rpm and libsolv version | ||
* Convert to new rpmdb format (details tbd) | * Convert to new rpmdb format (details tbd) | ||
* Check if package based operations still work in rpm, yum, dnf and all other tools | * Check if package based operations still work in rpm, yum, dnf, rpm-ostree and all other tools | ||
** Query installed packages | ** Query installed packages | ||
** Install, remove and update packages | ** Install, remove and update packages | ||
| Line 119: | Line 121: | ||
The format of the rpm database changed and can not be read by older rpm versions to convert back to the old format XXX. | The format of the rpm database changed and can not be read by older rpm versions to convert back to the old format XXX. | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 16:44, 26 February 2016
NewRpmDBFormat
Summary
Change format of the RPM Database from Berkeley DB to RPM's own format.
Owner
- Name: Florian Festi
- Email: ffesti@redhat.com
- Release notes owner:
Current status
Due to unexpected technical challenges we postpone this Change one release to F25.
Detailed Description
The current implementation of the RPM Database is based on Berkeley DB. There are doubts about the its future and level of maintenance. In addition rpm's use of the database has multiple issues on its own. As a result RPM upstream is working to replace the database format with a new implementation.
Benefit to Fedora
Getting rid of Berkeley DB as a dependency of one of the core components. (Actually not in F24 as we will keep the DBD support for now. But this is the required first step.)
Scope
- Proposal owners:
- Test and release the already implemented database format.
- Make sure it is supported by all important tools
- Tools using librpm should not be affected
- Libsolv is the most prominent tool accessing the rpmdb directly and needs adjustment
- Tooling for converting existing databases.
- Other developers:
- Release and update libsolv
- Release engineering: None (hopefully).
- List of deliverables: None
- Policies and guidelines: Not needed
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Conversion to the new format will make the RPM DB incompatible to older versions of rpm. The new version will be able to convert between the two formats.
How To Test
- Update to (not yet available) rpm and libsolv version
- Convert to new rpmdb format (details tbd)
- Check if package based operations still work in rpm, yum, dnf, rpm-ostree and all other tools
- Query installed packages
- Install, remove and update packages
User Experience
This change should influence the user experience.
Dependencies
None
Contingency Plan
- Contingency mechanism: Stay with the current format (which will continue to be supported). May need manual work for the testers to convert their rpmdb back.
- Contingency deadline: beta freeze
- Blocks release? Yes. If there are issues the default setting of the rpmdb format might be needed to be changed back before the release.
Documentation
tbd
Release Notes
The format of the rpm database changed and can not be read by older rpm versions to convert back to the old format XXX.