#10732 rawhide repo on dl.fp.o is missing files
Closed: Fixed 2 years ago by dustymabe. Opened 2 years ago by dustymabe.

  • Describe the issue

Trying to do a build with the rawhide repo and getting errors:

error: Cannot download Packages/k/kernel-modules-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37.x86_64.rpm: All mirrors were tried; Last error: Status code: 404 for http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/Packages/k/kernel-modules-5.18.0-0.rc0.20220331gi t787af64d05cd.13.fc37.x86_64.rpm (IP: 10.3.163.49)

Looks like some issue with the repo or maybe missing files on the server?

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

Today preferrably.


I don't see any kernel files with 20220331 in them in rawhide

kernel-core-5.18.0-0.rc0.20220325git34af78c4e616.7.fc37.x86_64.rpm

Did you request this package specifically or was this looked for by mock/dnf for your build?

But it was tagged to f37 yesterday

$ koji list-history --build=kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37
Thu Mar 31 21:43:38 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 tagged into f37-updates-candidate by jforbes
Thu Mar 31 21:43:43 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 tagged into f37-signing-pending by bodhi
Thu Mar 31 21:46:13 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 untagged from f37-signing-pending by autopen
Thu Mar 31 21:46:13 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 tagged into f37-updates-testing-pending by autopen
Thu Mar 31 21:49:05 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 untagged from f37-updates-testing-pending by bodhi
Thu Mar 31 21:49:07 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 untagged from f37-updates-candidate by bodhi
Thu Mar 31 21:49:09 2022 kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37 tagged into f37 by bodhi [still active]

Ah I see.. yeah looks like the push to rawhide failed? The repodata says 2022-04-01 and was built at 07:38 UTC but the files in the directories don't look like they were updated.

I'm seeing the same error trying to download the boost package during a mock build. The current repodata references boost <version epoch="0" ver="1.76.0" rel="10.fc37"/>, but the file available is boost-1.76.0-9.fc36.x86_64.rpm.

This is due to a bug in koji 1.28.0.

https://pagure.io/koji/issue/3260

It was writing out signed rpms with mode 0600. Since we use a seperate non priv user to sync those rpms around, it was just getting permission denied. ;(

Updates composes should be fixed now and syncing correctly.

For rawhide/branched, I am identifying all affected rpms, then will fix those and we will run new composes to get everything synced out properly.

Oh, I forgot to mention we patched the hubs with the upstream fix, so moving forward it should not do this. :)

this problem is fixed at least for me

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

2 years ago

Login to comment on this ticket.

Metadata