[root@1656943212 BEEDELLROKEJULIANLOCKHART]# dnf install ffmpeg
Fedora 36 - x86_64 102 kB/s | 81 MB 13:34
^CFedora 36 - x86_64 - Debug 16 kB/s | 16 MB 16:32
Errors during downloading metadata for repository 'fedora-debuginfo':
- Curl error (28): Timeout was reached for http://ftp-stud.hs-esslingen.de/pub/fedora/linux/releases/36/Everything/x86_64/debug/tree/repodata/3246337fcef78a7d0451e3357edf6a5722fb86bdfacb9d9feed49784731ed121-filelists.xml.zck [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
- Curl error (28): Timeout was reached for https://ftp-stud.hs-esslingen.de/pub/fedora/linux/releases/36/Everything/x86_64/debug/tree/repodata/62c1e141f3bbd6e22ca27075e5f6ccd53d489b8373ecea65a034ca48f6bff785-primary.xml.zck [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
- Curl error (56): Failure when receiving data from the peer for https://ftp-stud.hs-esslingen.de/pub/fedora/linux/releases/36/Everything/x86_64/debug/tree/repodata/3246337fcef78a7d0451e3357edf6a5722fb86bdfacb9d9feed49784731ed121-filelists.xml.zck [OpenSSL SSL_read: Connection reset by peer, errno 104]
Error: Failed to download metadata for repo 'fedora-debuginfo': Librepo was interrupted by a signal
…Why so slow?
You’re simply hitting a mirror that does not seem to be up at the moment (or is running into issues on your network for some reason). Mirrors are managed by the organisations that provide them, so there’s not much the Fedora community can do here. It could just be a temporary networking issue.
If the mirror continues to throw errors, please inform the Fedora infrastructure team by filing a ticket here. They can then contact the mirror admins to see what the issue is
In the meantime, if you let it run, it’ll time out and then go to the next mirror. Once your cache has been made, it will not need to do this again until the cache expires.
Also—could you please check if you have the
debuginfo repository enabled? One does not need that repository in normal usage. It is enabled temporarily by abrt etc. when debug information is required to analyse crashes.
It is deliberately enabled because I occasionally download complementary diagnostic packages.
You don’t need to keep them enabled: you can use the
debuginfo-install command to install debuginfo when required. This enables the repo, finds the right debuginfo packages, and installs them.
This just uses the
dnf debuginfo-install command, so you can use that directly too.