This started happening last night. I worked around it then with 42, and started doing it again now in 41, by changing from e.g.
#baseurl=http://download.example/pub/fedora/linux/updates/$releasever/Everything/$basearch/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch to baseurl=http://mirrors.us.kernel.org/fedora/updates/$releasever/Everything/$basearch/ #metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch I'm surprised to have seen no previous mention of this here already. Actually, I've seen nothing posted here since midnight at least. Using normal URLs, every standard repo SSL connection timed out metalinks with curl errors. While last night it worked right away, today after running my customary pre script successfully: #!/bin/sh echo "time dnf upgrade --releasever=41 dnf* rpm* libsol* glib* systemd* fedor* dracu* hawk*" time dnf upgrade --releasever=41 dnf* rpm* libsol* glib* systemd* fedor* dracu* Everything was timing out again, and yet, 157 packages upgraded successfully, while 4 were skipped, in 4.5 minutes. Is there a better workaround for when this happens, and keeps on happening? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
