On Fri, 2019-12-06 at 18:51 -0600, Richard Shaw wrote: > After reading this thread I think this is a more serious problem than just > this package. I had "assumed" modules were just normal, so I didn't > question them being installed. They are normal. You're not wrong. The problem is well understood at this point: a module was given a stream default - meaning it becomes the default source of packages it contains. That module includes protobuf, meaning it takes over from the non-modular repo as the default source of protobuf. The build of protobuf it contains was missing some bits that other packages depend on, which broke those packages. > I have not intentionally enabled/installed any modules but through regular > updates I now have the following installed: Well, yes. That's what happens. If this didn't actually break anything for you, you don't really need to panic, but if you want to sync with the current state (where the module stream default has been removed at least temporarily), just disable the modules that were enabled and then run 'dnf distro-sync'. That should return you to the non-modular builds. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
