Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 357439

Summary: Unable to find tar balls for new KDE-4.6.1 ebuilds "404 Not Found" & "No such directory"
Product: Gentoo Linux Reporter: Robert Cabrera <robcab666>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Robert Cabrera 2011-03-04 21:47:48 UTC
I synced my ~x86 laptop this morning and saw KDE-4.6.1 had been released. For the last 4-5 hours I've been trying to update, but have been unable to download any of the tarballs from any Gentoo mirror or from KDE. Portage fails on every single ebuild with error mesgs "404 Not Found" referring to the files not found on the servers and "No such directory" error mesgs referring to these directories not existing on the Gentoo mirrors or KDE hosting sites.

Were the Devs perhaps a little too eager to release and did so before KDE? I don't know. All I do know is that I've wasted several hours in a futile attempt to update and not a single package is yet available to download many hours later.

Reproducible: Always

Steps to Reproduce:
1.emerge --sync
2.emerge -uavND @world
3.

Actual Results:  
Every new KDE package fails to build because none of the source tarballs are available anywhere to download.

Expected Results:  
I expected at the very least to be able to download the source tarballs and ideally be able to compile and install them.

The source tarballs should have been readily available to download simultaneously or within a reasonable amount of time after the new ebuilds were released into the portage tree. As of the time of this report over 5 hours has elapsed yet none of the required files are available anywhere.
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2011-03-04 21:58:21 UTC

*** This bug has been marked as a duplicate of bug 357425 ***