• 50 Posts
  • 5.16K Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle


  • Layering isn’t bad, but what happens is with each update, the system tries to re-layer each of those packages. If some are missing from the next deployment’s rpm database or have been superceded by another package, you’ll run into these kinds of issues.

    In my case, for example, my next deployment was missing java-17-openjdk, because it had been superceded by other metapackages.



  • Technically they don’t own the code itself (because it’s open source), but if that’s your metric then no FOSS project can be meaningfully owned by anyone.

    That’s what I mean. You could fork the entire codebase today and start your own thing. Yes, that would be a massive undertaking, but we’re not talking about volunteers trying their hand at being Red Hat, we’re talking about governments with real resources to throw at it.

    And I agree that no FOSS project can be meaningfully owned by anyone. That’s kinda the point. The larger community allows “ownership” for various reasons, but many projects can be and do get forked and spun into different things.


  • For the “none of the providers can be installed” errors, there’s likely been a package name change or removal in 42. I ran into a similar issue with Bazzite. I uninstalled the offending package, then reinstalled after the update.

    The last one says there’s a package conflict. You’ll need to remove the one you have in order to proceed.








  • Telorand@reddthat.comtoBuy European@feddit.ukEU OS
    link
    fedilink
    arrow-up
    14
    arrow-down
    3
    ·
    5 days ago

    Nobody has yet provided a good reason why this matters. Red Hat doesn’t own Fedora, and RHEL is downstream from Fedora. You could fork it in whatever country you live in and start a new project if you wanted to.

    What is so important about these downstream ties that it taints the entire project? (I’m really asking, by the way.)