-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rpmdb: Also detect rpmdb.sqlite in /usr/share/rpm #386
Conversation
See: https://bugzilla.redhat.com/show_bug.cgi?id=1838691 This is obviously adding to a tower of hacks; what we really want is for this logic to live in librpm and be standardized. But in order to fix the immediate issue of detecting the rpmdb on rpm-ostree based systems (and any others that use `/usr/share/rpm`), add the sqlite path to detection. See also http://lists.rpm.org/pipermail/rpm-maint/2017-October/006681.html
FWIW, the bug is private… |
Something must have changed in BZ to more aggressively default to private bugs. That one was marked Anyways, fixed, thanks! |
I wonder if we should just check for the |
Is there no way in the libsolv API to override the dbpath? I thought OpenSUSE switched to |
@cgwalters They maintain a symlink in |
Doing it that way is gross though in I think the cleanest fix though per the above BZ is to get the "find the rpmdb location" in rpm itself and have it support the sysimage dir, now that libsolv uses librpm. |
Right, it should just pull the information from |
Following on to: - http://lists.rpm.org/pipermail/rpm-maint/2017-October/006681.html - coreos#1142 - openSUSE/libsolv#386 Write a symlink in `/usr/lib/sysimage/rpm` pointing to our current `/usr/share/rpm` - this way clients can start looking for it there, and then at some point we'll flip the symlink around and have `/usr/share/rpm` pointing to the new location. (Doing a hard swap now has upgrade implications)
Following on to: - http://lists.rpm.org/pipermail/rpm-maint/2017-October/006681.html - coreos#1142 - openSUSE/libsolv#386 Write a symlink in `/usr/lib/sysimage/rpm` pointing to our current `/usr/share/rpm` - this way clients can start looking for it there, and then at some point we'll flip the symlink around and have `/usr/share/rpm` pointing to the new location. (Doing a hard swap now has upgrade implications)
Following on to: - http://lists.rpm.org/pipermail/rpm-maint/2017-October/006681.html - #1142 - openSUSE/libsolv#386 Write a symlink in `/usr/lib/sysimage/rpm` pointing to our current `/usr/share/rpm` - this way clients can start looking for it there, and then at some point we'll flip the symlink around and have `/usr/share/rpm` pointing to the new location. (Doing a hard swap now has upgrade implications)
See: https://bugzilla.redhat.com/show_bug.cgi?id=1838691
This is obviously adding to a tower of hacks; what we really
want is for this logic to live in librpm and be standardized.
But in order to fix the immediate issue of detecting the rpmdb
on rpm-ostree based systems (and any others that use
/usr/share/rpm
),add the sqlite path to detection.
See also http://lists.rpm.org/pipermail/rpm-maint/2017-October/006681.html