I tried emerging xmlrpc-c, and unfortunately, its distfile isn't on any mirror, nor on the library's official site. Reproducible: Always Steps to Reproduce: 1. emerge =dev-libs/xmlrpc-c-1.18.02 Actual Results: Emerge fails due to a failed fetch. Expected Results: Successful emerge. I selected the major severity because the specified atom isn't masked by any keyword and is the current latest version, so people are going to run into this.
Looks good here, what mirror are you using? %% wget http://distfiles.gentoo.org/distfiles/xmlrpc-c-1.18.02.tar.bz2 --2010-07-27 14:49:02-- http://distfiles.gentoo.org/distfiles/xmlrpc-c-1.18.02.tar.bz2 Resolving distfiles.gentoo.org... 149.20.20.135 Connecting to distfiles.gentoo.org|149.20.20.135|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.kernel.org/gentoo/distfiles/xmlrpc-c-1.18.02.tar.bz2 [following] --2010-07-27 14:49:02-- http://mirrors.kernel.org/gentoo/distfiles/xmlrpc-c-1.18.02.tar.bz2 Resolving mirrors.kernel.org... 204.152.191.39 Connecting to mirrors.kernel.org|204.152.191.39|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 552233 (539K) [application/x-bzip2] Saving to: `xmlrpc-c-1.18.02.tar.bz2' 100%[======================================>] 552,233 392K/s in 1.4s 2010-07-27 14:49:04 (392 KB/s) - `xmlrpc-c-1.18.02.tar.bz2' saved [552233/552233]
Created attachment 240363 [details] build.log
(In reply to comment #1) > Looks good here, what mirror are you using? > > %% wget http://distfiles.gentoo.org/distfiles/xmlrpc-c-1.18.02.tar.bz2 > --2010-07-27 14:49:02-- > http://distfiles.gentoo.org/distfiles/xmlrpc-c-1.18.02.tar.bz2 > Resolving distfiles.gentoo.org... 149.20.20.135 > Connecting to distfiles.gentoo.org|149.20.20.135|:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://mirrors.kernel.org/gentoo/distfiles/xmlrpc-c-1.18.02.tar.bz2 > [following] > --2010-07-27 14:49:02-- > http://mirrors.kernel.org/gentoo/distfiles/xmlrpc-c-1.18.02.tar.bz2 > Resolving mirrors.kernel.org... 204.152.191.39 > Connecting to mirrors.kernel.org|204.152.191.39|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 552233 (539K) [application/x-bzip2] > Saving to: `xmlrpc-c-1.18.02.tar.bz2' > > 100%[======================================>] 552,233 392K/s in 1.4s > > 2010-07-27 14:49:04 (392 KB/s) - `xmlrpc-c-1.18.02.tar.bz2' saved > [552233/552233] > I'm currently using the following mirror: rsync://rsync3.nl.gentoo.org. To be honest, I just got another fetch error on another package just now, so my mirror may be botched.
(In reply to comment #3) > I'm currently using the following mirror: rsync://rsync3.nl.gentoo.org. > To be honest, I just got another fetch error on another package just now, so my > mirror may be botched. > That doesn't make much sense, you are using a gentoo portage mirror (emerge --sync) instead of a distfile mirror. I recommend removing whatever you have in make.conf for GENTOO_MIRRORS and try again. Please report back.
(In reply to comment #4) > (In reply to comment #3) > > > I'm currently using the following mirror: rsync://rsync3.nl.gentoo.org. > > To be honest, I just got another fetch error on another package just now, so my > > mirror may be botched. > > > > That doesn't make much sense, you are using a gentoo portage mirror (emerge > --sync) instead of a distfile mirror. I recommend removing whatever you have in > make.conf for GENTOO_MIRRORS and try again. Please report back. > It appears you are right about a wrong mirror. I remember removing some mirrors a few days ago, and I thought I'd used mirrorselect to select that mirror, but apparently, I haven't. I'm sorry for the trouble I've caused, and I guess I'll mark this bug as invalid.
No worries. mirrorselect should give you a good mirror. Otherwise, official mirrors are listed here: http://www.gentoo.org/main/en/mirrors2.xml Glad we could work it out.
