Comments
carlwgeorge
provided feedback
on mock-6.2-1.fc42, …
9 months ago
I can confirm this resolves #2367431, thanks!
This is not installable.
Error:
Problem: package R-4.5.0-3.el10_1.x86_64 from epel requires R-devel(x86-64) = 4.5.0-3.el10_1, but none of the providers can be installed
- conflicting requests
- nothing provides R-rpm-macros needed by R-devel-4.5.0-3.el10_1.x86_64 from epel
Files as https://bugzilla.redhat.com/show_bug.cgi?id=2367431
This seems to be missing a dependency.
Error:
Problem: conflicting requests
- nothing provides telepathy-mission-control needed by spacebar-1:6.3.5-1.el10_0.x86_64 from epel-testing
This seems to be missing a dependency.
Error:
Problem: conflicting requests
- nothing provides telepathy-mission-control needed by spacebar-1:6.3.5-1.el10_1.x86_64 from epel-testing
This has an uninstallable package.
Error:
Problem: conflicting requests
- nothing provides liblzfse.so.1()(64bit) needed by python3-asahi_firmware-0.7.8-4.el10_1.x86_64 from epel
I see this isn't a regular soname dependency, but is explicit in the spec file. Please consider adding that as a buildrequires also to ensure this can't be built without lzfse available.
carlwgeorge
commented & provided feedback
on redhat-lsb-5.0-0.16.20231006git8d00acdc.el9
10 months ago
This package is missing a dependency. This can be fixed with a dependency on /usr/bin/getopt or on the util-linux package that contains it.
root@c9:~# lsb_release --help
/usr/bin/lsb_release: line 162: getopt: command not found
This summary and last paragraph of the description still do not align with the FESCo guidance to remove any information that implies support for LSB.
Summary : Implementation of Linux Standard Base specification
Description :
...
The lsb package provides utilities, libraries etc. needed for LSB Compliant
Applications. It also contains requirements that will ensure that all
components required by the LSB are installed on the system.
Just like tor-0.4.8.14-1.el10_1, this does not install.
Error:
Problem: conflicting requests
- nothing provides torsocks needed by tor-0.4.8.16-1.el10_1.x86_64 from @commandline
Works well to build python-httpcore with tests enabled, thanks!
For posterity, I also manually tagged this build into epel10.1.
For posterity, I just manually tagged this build into epel10.1. This is necessary to avoid repeating the problem in epel#318.
This update has been unpushed.
I've manually tagged epel-release-10-4.el10_0 for epel10.1, so unpushing this build now since we won't use it.
The automated installability failure looks to be incorrect. It shows the message Failed to fetch ./result.json: TypeError: checks is undefined. Meanwhile a manual check shows the RPMs install as expected.
Ah, it's the python3-uvicorn+standard subpackage, which will fail to install until python-httptools-0.6.4-2.el10_1 and python-uvloop-0.21.0-1.el10_1 move to stable. Autopush is already disabled on this update to ensure it doesn't get promoted to stable before those updates.
The automated test failure seems to be having a problem rendering. I manually verified this package installs.
With FEDORA-EPEL-2025-65e100abca it looks like this is now installable.
This resolves the nexus installation issue.
Of course, happy to help.
Just so you're aware we did get installability checks enabled for the leading EPEL 10 minor version. If you look at the "Automated Tests" tab above there is a red indicator next to it, and if you switch to the tab it shows what the failure is. It isn't perfect, but it's a start to help catch things like this before they move to stable.
This does not install.
Error:
Problem: conflicting requests
- nothing provides torsocks needed by tor-0.4.8.14-1.el10_1.x86_64 from epel-testing