Do we have known build issues with EPEL-8? I'm unable to build pdns-4.3.1 as security update for EPEL-8. https://koji.fedoraproject.org/koji/packageinfo?packageID=2744
It fails on x86_64. But this must be an issue with koji building servers? https://koji.fedoraproject.org/koji/taskinfo?taskID=52397144 GenericError: hash changed for external rpm: tinycdb-devel-0.78-9.el8.x86_64@rhel8-base (601e1d742755077687cfaa42b4f19 -> 601e1d7427d59077687cefaaa42b4f19
I've tried to build it several times, always the same error.
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
I looked at this some and was unable to figure it out.
Odd things tho:
It complains about hash changing, but... it's the same in the message?
This package hasn't changed in ages.
@mikem / @tkopecek Any ideas? Have you ever seen this or can think of when it could happen?
Even size doesn't fits here (db says 10656, while downloaded rpm is 17576 bytes). Hash differs a bit if you compares them. I can't find any version of this package with such small size. In brew we have correct data for this rpm (10656/601e1d742755077687cfaa42b4f19 - unsigned version) Buildtime is the same, so it should be that rpm. Can you download it and check the content? (https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/ is not reachable for me)
File: tinycdb-devel-0.78-9.el8.x86_64.rpm Size: 18680 Blocks: 40 IO Block: 4096 regular file Device: fd00h/64768d Inode: 587610267 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Context: unconfined_u:object_r:admin_home_t:s0 Access: 2020-10-05 19:51:34.069842485 +0000 Modify: 2020-10-05 19:51:30.660517196 +0000 Change: 2020-10-05 19:51:30.660517196 +0000 Birth: -
# rpm -qlip tinycdb-devel-0.78-9.el8.x86_64.rpm Name : tinycdb-devel Version : 0.78 Release : 9.el8 Architecture: x86_64 Install Date: (not installed) Group : Development/Libraries Size : 10656 License : Public Domain Signature : RSA/SHA256, Sat 15 Dec 2018 01:12:57 AM GMT, Key ID 199e2f91fd431d51 Source RPM : tinycdb-0.78-9.el8.src.rpm Build Date : Sun 12 Aug 2018 06:34:32 PM GMT Build Host : x86-vm-07.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://www.corpit.ru/mjt/tinycdb.html Summary : Development files for tinycdb Description : tinycdb is a small, fast and reliable utility set and subroutine library for creating and reading constant databases. This package contains tinycdb development library and header file for developing applications that use tinycdb. /usr/include/cdb.h /usr/lib64/libcdb.so /usr/lib64/pkgconfig/libcdb.pc /usr/share/man/man3/cdb.3.gz
Yes, it looks like correct one (signed version, so size is bigger but payload has is the same). I'm afraid that the only solution is to manually update rpm record in the db. But I've no idea from where these data came from. It doesn't look, that there is such version of rpm. It could have been some scratch build used in some early phase in some testing compose, but it is highly unlikely. I'm quite suspicious about checksum which differs only in one or two bytes.
@mikem any idea?
Btw, I've checked other archs and there are correct data.
Strange. Well, I guess I am game to fix it in the db (can you tell me where?) but it would sure be nice to know why it happened... I wonder if it was incompletely synced when the repo got regenerated?
Strange thing is that it was already used in some buildroots. So it must have passed the check before.
UPDATE rpminfo SET payloadhash = '601e1d7427d59077687cefaaa42b4f19', size = 17576 WHERE name = 'tinycdb-devel' AND version = '0.78' AND release = '9.el8' AND arch = 'x86_64
(or 'WHERE id = 18541812' according to 'koji rpminfo tinycdb-devel-0.78-9.el8.x86_64.rpm')
ok, done.
I guess we will just hope that this was some strange one off error for now...
Thanks for all the help @tkopecek
@mstevens your build should go through now...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@kevin
Thank you. It's now building fine. https://koji.fedoraproject.org/koji/buildinfo?buildID=1614682
Login to comment on this ticket.