Thank you. This is indeed a bug in the configure script. We shouldn't apply the
`OPENMP_CFLAGS` macro if we just evaluated that the required version of OpenMP
is not available. Let me fix that quickly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email dire
I've no problem allowing probing for read-only mode now that it wont go and
create new databases in that mode, but I don't think we should ever write based
on guessing. Change this to test for read-only dbmode and I'll happily merge.
That should work for rpmdb2solv I think...
--
You are receiv
the commit message was talking about the perl and python macros.
%requires_eq is not related to either of those.
so what was the rational to remove it?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm
Removing it was no accident...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1452#issuecomment-736559600___
Rpm-maint mailing
it was killed by accident in ba85c95963f9b62f237c0442f6b5aca3e355fa83
and I would be glad if it could also be backported to the fedora 33 rpm version
again. so i can remove the copy of %requires_eq in the spec files.
Thank you in advance.
--
You are receiving this because you are subscribed to
In case you're wondering where this is coming from: libsolv's rpmdb2solv
currently does not work anymore because it does not read in the rpm macros.
I'm aware that this is a somewhat unsupported way of operating with librpm, but
maybe the change is small enough so that you'll merge it anyway ;)
There is no harm in allowing read access in this case. We still
error out in the database rebuild case, just to be on the safe
side.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1451
-- Commit Summary --
* Allow database
