I can't update Fedora 17 (64 bits)

[DoomDeathMetal]

Hi, I have a problem updating with Fedora 17.

When I try to update Fedora 17 x86_64 it give me the next message: Error: Cannot retrieve metalink for repository: fedora. Please verify its path and try again


I installed Fedora 17 from a live CD and I did a partial format of hard disk to conserve my data.

-----------------------------------------------------------------------------------------------------------------

I copied, the files of /etc/yum.repos.d from my Fedora 16 of my desktop to Fedora 17 and it run.

[marko]

I copied, the files of /etc/yum.repos.d from my Fedora 16 of my desktop to Fedora 17 and it run.

It might be a good idea to do :

yum remove fedora-release
yum install fedora-release

and make sure you see that it's the Fedora 17 package that's installed in the second command

[DoomDeathMetal]

Thanks, but the repository files gets the version from variables.

[oboedad55]

BTW, what was the solution? It's important to post that information so others running across this topic with a similar problem will know what you did to resolve it.

[DoomDeathMetal]

How do you want I explain you the solution? I took the repos files of /etc/yum.repos.d from a Fedora 16 installed and I copied them to a flash memory.

After I copied the repos files from flash memory to /etc/yum.repos.d folder of Fedora 17.

I didn't anything more, serious.

[robgiorgi]

...I got the same problem ("Error: Cannot retrieve metalink for repository") while doing yum on a fresh installation of Fedora 17.

The solution was very simple after detecting the problem: the date was set to exactly 1 YEAR BEFORE !!

After updating the date, yum started to work perfectly !!

Hope it helps someone ;-)
Roberto.

[dasii]

After updating the date, yum started to work perfectly !!

Thanks for posting this.

Which date did you update? The system date?


Cheers,
David.

[robgiorgi]

I just updated the date to the current date.

[dasii]

I just updated the date to the current date.

Thank you, this appears not to be the problem I am having.

[M.e.M.O.]

Hello ,

Sorry for bumping an old thread , but i am having exactly the same issue .

"Error: Cannot retrieve metalink for repository: fedora/17/x86_64. Please verify its path and try again"

I read somehwere to put IP information of mirrors.fedoraproject.org into hosts , which did not work in my case. Also date is correct . The device can access any of the mirrors by Firefox , no problem .

Any ideas?

Here is my yum.conf . I don't think I have changed anything .

# cat /etc/yum.conf
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=5
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=3

#  This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
#  It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

Solved :

Sorry for bothering , a noob mistake was in motion .

I have changed the box's IP address which was also my proxy server. Somehow I missed to edit .bashrc and correct the IP addresses in there .

[cafetono]

I'd been experiencing the same problem (Error: Cannot retrieve metalink for repository: fedora/18/x86_64. Please verify its path and try again) with Fedora 18 and, while searching these postings, the automatic update program suddenly kicked in. Perhaps it's just a matter of waiting for an hour or so after installation to see whether yum corrects itself or not. (i.e., boot to the installation and go do something else for an hour or so.) I hope this works for anyone else who experiences this problem.