I'm trying to install gmic on my Fedora 32 system, which requries opencv, which requires protobuf 3.11
DNF refuses to install any of them though, because protobuf 3.11 is blocked by modularity:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering - package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
All I can see with "dnf list" is a seriously outdated version from an unknown module:
protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 fedora-modular protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 updates-modular
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled, and more importantly which is providing this bogus outdated protobuf ?
Regards, Daniel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Mon, 2020-06-15 at 11:31 +0100, Daniel P. Berrangé wrote:
I'm trying to install gmic on my Fedora 32 system, which requries opencv, which requires protobuf 3.11
DNF refuses to install any of them though, because protobuf 3.11 is blocked by modularity:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering - package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
All I can see with "dnf list" is a seriously outdated version from an unknown module:
protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 fedora-modular protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 updates-modular
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled, and more importantly which is providing this bogus outdated protobuf ?
dnf module reset eclipse
Regards, Daniel --
: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| : https://libvirt.org -o- https://fstop138.berrange.com :| : https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
- -- Igor Raits ignatenkobrain@fedoraproject.org
On Mon, Jun 15, 2020 at 12:43:37PM +0200, Igor Raits wrote:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering - package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled, and more importantly which is providing this bogus outdated protobuf ?
dnf module reset eclipse
Could you please explain the steps how to arrive to this "magic" invocation?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Mon, 2020-06-15 at 13:52 +0200, Tomasz Torcz wrote:
On Mon, Jun 15, 2020 at 12:43:37PM +0200, Igor Raits wrote:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering - package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled, and more importantly which is providing this bogus outdated protobuf ?
dnf module reset eclipse
Could you please explain the steps how to arrive to this "magic" invocation?
dnf list on Daniel's system shows only one protobuf build - protobuf- 3.6.1-6.module_f32+6163+c0e6dcb2. Doing koji list-tags --build protobuf-3.6.1-6.module_f32+6163+c0e6dcb2 shows:
module-eclipse-2019-06-3220190902131726-a48fff9b module-eclipse-2019-06-3220190902131726-a48fff9b-build
- From where it is easy to figure out which module it is coming from :)
-- Tomasz Torcz “God, root, what's the difference?” tomek@pipebreaker.pl “God is more forgiving.” _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
- -- Igor Raits ignatenkobrain@fedoraproject.org
On Mon, Jun 15, 2020 at 12:43:37PM +0200, Igor Raits wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Mon, 2020-06-15 at 11:31 +0100, Daniel P. Berrangé wrote:
I'm trying to install gmic on my Fedora 32 system, which requries opencv, which requires protobuf 3.11
DNF refuses to install any of them though, because protobuf 3.11 is blocked by modularity:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering - package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
All I can see with "dnf list" is a seriously outdated version from an unknown module:
protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 fedora-modular protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 updates-modular
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled, and more importantly which is providing this bogus outdated protobuf ?
dnf module reset eclipse
Thank you, that solves it. I'm still wondering how I was supposed to find out that "eclipse" was the module providing this bogus outdated "protobuf" RPM to start with ? Is there some query command that would do it ? I tried "dnf module repoquery" and "dnf module provides" with no luck, but perhaps I got wrong syntax ?
I then had a problem with "dnf install scala" reporting that "scala" was blocked by a module. Strangely disabling the "scala" module let me install the "scala" RPM.
Regards, Daniel
On Mon, Jun 15, 2020 at 11:31:09AM +0100, Daniel P. Berrangé wrote:
I'm trying to install gmic on my Fedora 32 system, which requries opencv, which requires protobuf 3.11
DNF refuses to install any of them though, because protobuf 3.11 is blocked by modularity:
- package protobuf-3.11.2-2.fc32.i686 is filtered out by modular filtering
- package protobuf-3.11.2-2.fc32.x86_64 is filtered out by modular filtering
All I can see with "dnf list" is a seriously outdated version from an unknown module:
protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 fedora-modular protobuf.x86_64 3.6.1-6.module_f32+6163+c0e6dcb2 updates-modular
What is the right way to fix this ? dnf module list shows me loads of modules, but I'm not seing how to determine which of them are enabled vs disabled,
"dnf module list" marks enabled streams with "[e]" in a Stream column. (There also used to be "[d]" for the default streams that were active (read "pre-enabled") by default, but default streams are now banned and should not exist in Fedora repositories (since Fedora 32?).)
"dnf module list --enabled" restricts the list to enabled modules only.
and more importantly which is providing this bogus outdated protobuf ?
"dnf module provides protobuf-3.6.1-6.module_f32+6163+c0e6dcb2" returns eclipse:2019-06:3220190902131726:a48fff9b:x86_64 module. Thus you need to unenable eclipse:2019-06 stream ("dnf module reset eclipse:2019-06"), or disable the eclipse module completely ("dnf module disable eclipse").
-- Petr
-
Daniel P. Berrangé -
Igor Raits -
Petr Pisar -
Tomasz Torcz