replace negativo17 with rpmfusion?
recently, it seems that the upstream ublue main images replaced the
rpmfusion repo with negativo17. my issue is that this repository only includes a really small set of applications, mostly just being used by ublue for patched mesa and the like. my issue is that this repo doesn't provide as many applications as rpmfusion or the ones i use, such as mpd, and from the repo directly:
This repository is NOT compatible with RPMFusion, nor it does attempt to replace it as I have no interest in adding any software out there.so i'm trying to figure out, is there a clean way to remove
negativo17 and readd rpmfusion? since it seems like they did replace some components with packages from that repo, and i'm not sure if simply removing the negativo repo and dropping in rpmfusion would mess around with anything.
repo link if requiredGitHub
GitHub - sneexy-boi/bluebuild-custom
Contribute to sneexy-boi/bluebuild-custom development by creating an account on GitHub.
Solution:Jump to solution
- You can install RPMFusion like this:
```
rpm-ostree install \
https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-${OS_VERSION}.noarch.rpm \
https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-${OS_VERSION}.noarch.rpm...
21 Replies
Solution
- You can install RPMFusion like this:
- Then disable Negativo 17 repo before installing RPMFusion packages, like this:
sed -i 's@enabled=1@enabled=0@g' /etc/yum.repos.d/negativo17-fedora-multimedia.repo
- Do the install of RPMFusion packages.
- Then enable multimedia repo after that with:
sed -i '0,/enabled=0/{s/enabled=0/enabled=1/}' /etc/yum.repos.d/negativo17-fedora-multimedia.repoI agree that this move is the disadvantage to downstream users which rely on RPMFusion.
It helps Ublue to avoid occasional RPMFusion package skews, but downstream users need to do this workaround if they wish to use RPMFusion
What if we add this as an option in the
bling module that would enable RPMFusion?do i have to redisable rpmfusion repos or is it just reenabling the negativo repos
https://github.com/sneexy-boi/bluebuild-custom/actions/runs/11206075203/job/31146327300#step:2:6202 it appears some akmods attempts to reinstall rpmfusion
GitHub
chore(wuzetka): fix sddm theme config · sneexy-boi/bluebuild-custom...
Contribute to sneexy-boi/bluebuild-custom development by creating an account on GitHub.
workaround by not using the akmods module and just manually installing the packages
I will fix this
GitHub
fix(akmods): Don't install RPMFusion if it's already installed · bl...
Otherwise, it complains about package conflict.
i've been thinking about how much effort it would take to fork ublue's main and hwe to undo these changes
it seems they've gone ahead with this without regard to it breaking locally layered packages from rpmfusion
although maybe they just need the other negativo repos as well
multimedia is the biggest negativo repo, so I think that nothing can be done to improve that
hmm
mostly trivial I would say
there is some benefit though in that negativo's steam and other packages skew less
the other question would be: is negativo17 more or less trustworthy than rpmfusion
or the same
that & mesa
yep
1 man vs rpmfusion maintainers
scaronni (Negativo repo maintainer) seems to handle stuff well
cool
there are some other negativo repos though that have a couple useful packages
idk if they would get added to main
Just checked, all subrepos packages are basically merged into
multimedia
so multimedia contains everything of Negativooh you're right actually
didn't notice
interesting, negativo packages signal desktop for some reason
im trying to find other small packages that would be useful in the main repo
@RoyalOughtness let's not pollute this question thread & go to general
oh right my bad