You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is difficult to decide which package from a repository was installed, because repodata created by createrepo contains only checksum of the whole package and rpmdb contains only checksum of a header. What about to store such an information in RPMDB?
The text was updated successfully, but these errors were encountered:
The header is the data by which a package should be identified, because the whole can differ due to uncompressed vs compressed payload, both of which are acceptable to rpm as long as the bits are identical.
The generic case here would be permitting storage of auxiliary data in rpmdb, which has been requested for various purposes for as long as I remember. I think mostly everybody agrees that there are legitimate cases for it, but the devil is in the details.
pmatilai
changed the title
Store an alternative package checksums in rpmdb
RFE: Store auxiliary data in rpmdb
Aug 17, 2021
It is difficult to decide which package from a repository was installed, because repodata created by createrepo contains only checksum of the whole package and rpmdb contains only checksum of a header. What about to store such an information in RPMDB?
The text was updated successfully, but these errors were encountered: