Copr repo for PyCharm owned by phracek 292 B/s | 341 B 00:01
Errors during downloading metadata for repository 'phracek-PyCharm':
- Status code: 404 for https://copr-be.cloud.fedoraproject.org/results/phracek/PyCharm/fedora-35-aarch64/repodata/repomd.xml
Error: Failed to download metadata for repo 'phracek-PyCharm': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
RPM Fusion for Fedora 35 - Nonfree - Steam 49 kB/s | 98 kB 00:01
Errors during downloading metadata for repository 'rpmfusion-nonfree-steam':
- Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-steam-35&arch=aarch64
- Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-steam-35&arch=aarch64
Error: Failed to download metadata for repo 'rpmfusion-nonfree-steam': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-steam-35&arch=aarch64
Ignoring repositories: phracek-PyCharm, rpmfusion-nonfree-steam
Last metadata expiration check: 3:30:40 ago on Fri 04 Feb 2022 07:26:49 PM GMT
Is this still a bug ? Or am i missing something here ?
That tells you the system was unable to connect to the repo. If the internet seems to be working then it likely is a transient error somewhere in the path between you and those repos. If you do not have a good internet connection then you would need to establish a good connection from that system and try again.
Sometimes the network issue may be at your end, or it may be between you and the other end, or it may be at the other end. The fact that you got that error on a copr repo and on rpmfusion both would help identify where the error actually is.
This is not a bug, it is dnf telling you it had a network problem and skipped the repos it could not reach…
My network works perfectly fine… the issue started after enabling third part repo from the gnome-software-tool.
A dnf update prior enabling third part repos didn’t produce any error, so is definitely an issue with the repo server. So was wondering when this will be fixed
Or is there anywhere where we can report this problem ?
I think there is something wrong with the servers got this when trying to do a dnf upgrade --refresh. The error occurs with both ipv4 and ipv6.
Errors during downloading metadata for repository 'fedora':
- Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 209.132.190.2)
- Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 152.19.134.198)
- Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 140.211.169.196)
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 140.211.169.196)
After 2½ months this problem is still present and is not caused by network flakiness. THere is no aarch64 available on that mirror.
We should address this because any user trying Fedora on his M1 machine will be quite annoyed. I do not remember seeing similar errors with… the african alternative
Just ran into this exact same error while trying to rpm-ostree install on the latest (today’s) Fedora Silverblue on a Pinebook Pro.
(I’m trying to install the a third-party ap6256 firmware driver to get WiFi and Bluetooth working.)
Fedora SIlverblue is otherwise running amazingly well on this $200 ARM laptop. Would be so wonderful to have it run properly out of the box. (Imagine the uses for education. I’m writing this from within it using a wired ethernet connection via a USB adapter at the moment.)
A gateway Timeout, what ever that means. Could probably the server or infrastructure teame tell why this happens frequently?
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>504 Gateway Timeout</title>
</head><body>
<h1>Gateway Timeout</h1>
<p>The gateway did not receive a timely response
from the upstream server or application.</p>
</body></html>
