Binaries reporting 404
mvaisakh opened this issue · 1 comments
mvaisakh commented
I was trying to get open264 codecs installed on my Fedora Desktop but I can't seem to do so because the binaries are reporting 404.
➜ ~ sudo dnf install openh264 mozilla-openh264
Fedora 39 openh264 (From Cisco) - x86_64 763 B/s | 989 B 00:01
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
mozilla-openh264 x86_64 2.3.1-2.fc39 fedora-cisco-openh264 427 k
openh264 x86_64 2.3.1-2.fc39 fedora-cisco-openh264 420 k
Transaction Summary
================================================================================
Install 2 Packages
Total download size: 847 k
Installed size: 2.2 M
Is this ok [y/N]: y
Downloading Packages:
[MIRROR] openh264-2.3.1-2.fc39.x86_64.rpm: Status code: 404 for http://ciscobinary.openh264.org/openh264-2.3.1-2.fc39.x86_64.rpm (IP: 172.16.16.250)
[MIRROR] mozilla-openh264-2.3.1-2.fc39.x86_64.rpm: Status code: 404 for http://ciscobinary.openh264.org/mozilla-openh264-2.3.1-2.fc39.x86_64.rpm (IP: 172.16.16.250)
[MIRROR] openh264-2.3.1-2.fc39.x86_64.rpm: Status code: 404 for http://ciscobinary.openh264.org/openh264-2.3.1-2.fc39.x86_64.rpm (IP: 172.16.16.250)
[MIRROR] mozilla-openh264-2.3.1-2.fc39.x86_64.rpm: Status code: 404 for http://ciscobinary.openh264.org/mozilla-openh264-2.3.1-2.fc39.x86_64.rpm (IP: 172.16.16.250)
[FAILED] mozilla-openh264-2.3.1-2.fc39.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
(2/2): openh264-2.3. 50% [========== ] 420 kB/s | 427 kB 00:01 ETA
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
mozilla-openh264-2.3.1-2.fc39.x86_64: Cannot download, all mirrors were already tried without success
Even trying to open binary links from past 2 releases (2.40 and 2.41) leads me to 404.
torokati44 commented
This was probably a transient network/server issue, the package URLs work for me now.