#11751 libssh2-devel seems to be missing from the EPEL7 x86_64 buildroot
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by orion.

  • Describe the issue

Tried to build zabbix6.0 in EPEL7. Build failed on x86_64 with:

DEBUG util.py:448: Error: No Package found for libssh2-devel

https://koji.fedoraproject.org/koji/taskinfo?taskID=108341647

Build completes fine on ppc64le.

Tried twice.

  • When do you need this? (YYYY/MM/DD)
    Soon

  • When is this no longer needed or useful? (YYYY/MM/DD)
    EL7 EOL - 2024/06/20

  • If we cannot complete your request, what is the impact?
    Cannot build anything that depends on libssh2-devel


So the package should have been available:
ppc64le/rhel-7-server-optional-rpms/Packages/l/libssh2-devel-1.8.0-4.el7_9.1.ppc64le.rpm
x86_64/rhel-7-server-rpms/x86_64/rhel-7-optional-for-x86_64-server-rpms/Packages/l/libssh2-devel-1.8.0-4.el7_9.1.x86_64.rpm

I don't know why it wasn't found, so I wonder if it was a transient problem or not.

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

ok. I think I found the problem.

There is a tboot package with control characters in it's changelog.
This cases creatrerepo_c to barf:

C_CREATEREPOLIB: Critical: Cannot dump XML for tboot (286d5c46ce71772d3d8597f58f1d548ef83bf3278ca60b3c6ac6729ff3ed1d5e): Forbidden control chars found (ASCII values <32 except 9, 10 and 13).

Due to logic in our sync script this causes it to just go on to syncing the next repo, but not in the right place. It synced it under the server repo, then it runs createrepo_c on the other repos in the right place and they have no changed content.

I have excluded the tboot package and also tweaked the script to handle this failure.

I have re-run it and regened the repo in koji.

Can you try again now?

Build completes fine now. Thank you!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog