This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
packages:rpm [2021-01-30 23:57] baggins |
packages:rpm [2021-02-01 10:38] glen preserve double slashes |
||
---|---|---|---|
Line 21: | Line 21: | ||
* The rpm database format changes from Berkeley DB to SQLite, conversion is automatic after rpm package set update. Backup of the old database is saved as ''/var/lib/rpm.rpmbackup-VERSION-RELEASE'', using version and release of the package that is installed (not the old one). Ex. if the old package was rpm-5.4.15-58 and the new one is rpm-4.16.1.2-1, the backup of the database will be in ''/var/lib/rpm.rpmbackup-4.16.1.2-1''. | * The rpm database format changes from Berkeley DB to SQLite, conversion is automatic after rpm package set update. Backup of the old database is saved as ''/var/lib/rpm.rpmbackup-VERSION-RELEASE'', using version and release of the package that is installed (not the old one). Ex. if the old package was rpm-5.4.15-58 and the new one is rpm-4.16.1.2-1, the backup of the database will be in ''/var/lib/rpm.rpmbackup-4.16.1.2-1''. | ||
* Users who have a particular need to stay on Berkeley DB backend can still do so by overriding the configuration manually (eg. ''echo '%_db_backend bdb' >> /etc/rpm/macros'') before updating rpm package. | * Users who have a particular need to stay on Berkeley DB backend can still do so by overriding the configuration manually (eg. ''echo '%_db_backend bdb' >> /etc/rpm/macros'') before updating rpm package. | ||
- | * It is also possible to convert back bu overriding ''_db_backend'' and running ''rpm --rebuilddb''. | + | * It is also possible to convert back bu overriding ''_db_backend'' and running %%''rpm --rebuilddb''%%. |
<note warning>Staying with or converting back to Berkeley DB backend is discouraged as rpm upstream plans to reduce Berkeley DB support to read-only. | <note warning>Staying with or converting back to Berkeley DB backend is discouraged as rpm upstream plans to reduce Berkeley DB support to read-only. | ||
Line 37: | Line 37: | ||
* Suggests are now [[http://rpm.org/user_doc/dependencies.html|Recommends]], | * Suggests are now [[http://rpm.org/user_doc/dependencies.html|Recommends]], | ||
- | * ''noautoreq*'' and ''noautoprov*'' must be converted to [[https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/|__requires_exclude* and __provides_exclude*]] respectively. | ||
- | <note>The above is not yet integrated into [[packages:rpm-pld-macros|rpm-pld-macros]]</note> | ||
* ''Obsoletes''/''Provides'' must follow the package naming rules, they cannot contain characters like ''()'' or ''/'', what means packages cannot depend on path/files or same virtual dependency names (ex. ''perl::Foo'' is not accepted). | * ''Obsoletes''/''Provides'' must follow the package naming rules, they cannot contain characters like ''()'' or ''/'', what means packages cannot depend on path/files or same virtual dependency names (ex. ''perl::Foo'' is not accepted). | ||
* Minor spec syntax changes | * Minor spec syntax changes |