Re: check mirror s3-mirror-eu-west-1.fedoraproject.org

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/10/2018 02:35 PM, Eg. Bo. wrote:
> 
> Hello,
>  
> who could help in resolving an issue with an AWS S3 mirror ?
> I'd like to download the epel release package using this URL: 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'.
> On my PC (proxy) I can download the file however if I run wget on EC2 instances (tried different accounts) in region eu-west-1 this ends up in 404.
> 
> 
> [ec2-user@ip ~]$ wget 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'
> --2018-03-10 03:30:12--  http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> Resolving download.fedoraproject.org (download.fedoraproject.org)... 185.141.165.254, 8.43.85.67, 152.19.134.142, ...
> Connecting to download.fedoraproject.org (download.fedoraproject.org)|185.141.165.254|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [following]
> --2018-03-10 03:30:12--  http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> Resolving s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)... 52.218.64.194
> Connecting to s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)|52.218.64.194|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2018-03-10 03:30:12 ERROR 404: Not Found.
> [ec2-user@ip ~]$
> 
> The link http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm isn't also valid on my PC.
> 
> 
> Please help/fix.

Yeah, this is because that url points to just a link on our master
mirrors to help folks install the latest version of that package.

Where did you get the download.fedoraproject.org url for it?

You can use:

https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

which will use the master mirrors for it.

As for fixing it on AWS, I suppose we could add some logic to our
mirroring to also copy up the latest epel-release version as that
'latest' link. We should make sure it auto updates though so we aren't
publishing a stale package.

Ricky: can you look into adding that to the existing sync script?

kevin

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux