#8988 EPEL-8 builds failing
Closed: Fixed 2 months ago by kevin. Opened 2 months ago by cra.


Yes sorry. This is breakage as part of the move of datacentre's. Breakages like this will be occurring fairly regular for the next 3 weeks.

Metadata Update from @smooge:
- Issue assigned to smooge

2 months ago

I believe I have put in a fix for this. Could you test ?

Metadata Update from @smooge:
- Issue priority set to: Waiting on Reporter (was: Needs Review)
- Issue tagged with: groomed, high-gain, koji, low-trouble

2 months ago

Looks better. But my package still fails to build--there are two packages that should be in the epel8-override buildroot but they aren't being found:

https://kojipkgs.fedoraproject.org//work/tasks/1472/45521472/root.log

DEBUG util.py:600: No matching package to install: 'perl(Crypt::ECB) >= 1.45'
DEBUG util.py:600: No matching package to install: 'perl(Crypt::Twofish) >= 2.14'

I think they should be in the buildroot:

https://koji.fedoraproject.org/koji/builds?tagID=10323

1519628 perl-Bytes-Random-Secure-0.29-14.el8 epel8-override ppisar 2020-06-03 08:14:52 complete
1518921 perl-Crypt-Twofish-2.17-22.el8 epel8-override jplesnik 2020-06-01 13:53:44 complete
1517093 perl-Crypt-ECB-2.22-1.el8 epel8-override cra 2020-05-28 18:27:07 complete

I haven't used buildroot overrides much, did I do something wrong?

Thanks.

That sadly I can't really help much on sorry. I do those so infrequently I usually have to ask first... make sure I did it right twice and then still correct something I did.

When you create an override the build is tagged into a override tag. This tag is used to create the buildroot, the next time it's regenerated.

You can see if it's there by using koji wait-repo...

➜ ~ koji wait-repo --build perl-Crypt-Twofish-2.17-22.el8 epel8-build
Successfully waited 0:00 for perl-Crypt-Twofish-2.17-22.el8 to appear in the epel8-build repo
➜ ~ koji wait-repo --build perl-Crypt-ECB-2.22-1.el8 epel8-build
Successfully waited 0:00 for perl-Crypt-ECB-2.22-1.el8 to appear in the epel8-build repo

so, they both should be there now. buildroot regens have been slow lately, and we have had no cycles to debug it... you can follow along with that in ticket 8922

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

2 months ago

Login to comment on this ticket.

Metadata