Le sam. 7 mars 2026 à 14:23, Andrew Bauer via rpmfusion-developers <[email protected]> a écrit : > > Thank you Sérgio for setting that up. Perhaps this is a dumb question, but > how exactly do we request the new EPEL 10 branches? They are not visible in > pkgdb and that's the only tool I know to use in rpmfusion, since we can't > "rfpkg request-branch epel10.1" like we do in fedora
Please discard what Sergio said, we are using a different setup than epel 10 in that we do not have dedicated branches for el10.1 el10.2 and el10-next or whatever the name. > Note also there seems to be a related problem with mythtv EL10 build. The > build system tried to pull in qt6-qtwebengine-devel-6.10.1-2.1.el10_2 rather > than qt6-qtwebengine-devel-6.10-2.1.el10_1. > > Error: > Problem: conflicting requests > - nothing provides libQt6Core.so.6(Qt_6.10)(64bit) needed by > qt6-qtwebengine-devel-6.10.1-2.1.el10_2.x86_64 from build > (try to add '--skip-broken' to skip uninstallable packages) The error was because the epel10 external repo was set to https://dl.fedoraproject.org/pub/epel/10/Everything/ which currently point to a repos that is suitable for CentOS next. while our current repo is https://dl.fedoraproject.org/pub/epel/10.1/Everything/. I've only fixed the default el10 case. > So the build system appears to be using alma 10.1 now, which explains why it > (correctly) pulled in qt6-qtbase-6.10 rather than qt6-qtbase6.10.1. However, > it also pulled in epel10.2 rather than epel10.1. > > I'm not sure if this gets back to my question about checking out the right > el10 dbranch, or if there is a legitimate issue going on with the > infrastructure. > > Note that I tried rfpkg build --target epel 10_1 and that failed with unknown > build target. As I said, there is no such thing as --target epel10_1 for rpmfusion Only rfpkg build # implicit to el10-free (or nonfree) and rfpkg build --target el10-next-free (or nonfree) for centos stream. Thanks. _______________________________________________ rpmfusion-developers mailing list -- [email protected] To unsubscribe send an email to [email protected]
