Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 103296 - emerge glibc dies with 404 errors
Summary: emerge glibc dies with 404 errors
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2005-08-21 17:15 UTC by Bob
Modified: 2010-06-30 03:25 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Bob 2005-08-21 17:15:50 UTC
tux / # emerge glibc -v
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-libs/glibc-2.3.5-r1 to /
>>> Downloading
           => `/usr/portage/distfiles/glibc-2.3.5-patches-1.8.tar.bz2'
Connecting to[]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
23:59:26 ERROR 404: Not Found.

>>> Downloading
           => `/usr/portage/distfiles/glibc-2.3.5-patches-1.8.tar.bz2'
Connecting to[]:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
           => `/usr/portage/distfiles/glibc-2.3.5-patches-1.8.tar.bz2'
Connecting to[]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
23:59:29 ERROR 404: Not Found.

>>> Downloading
           => `/usr/portage/distfiles/glibc-2.3.5-patches-1.8.tar.bz2'
Connecting to[]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
23:59:29 ERROR 404: Not Found.

>>> Downloading
           => `/usr/portage/distfiles/glibc-2.3.5-patches-1.8.tar.bz2'
Connecting to[]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
23:59:30 ERROR 404: Not Found.

!!! Couldn't download glibc-2.3.5-patches-1.8.tar.bz2. Aborting.
tux / #                                                                          

Reproducible: Always
Steps to Reproduce:
1.  emerge glibc

Actual Results:  
server issues 404 error when portage attempts to download files

Expected Results:  
successful emerge

emerge --info:

Portage (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r0,
2.6.12-ck4 i686)
System uname: 2.6.12-ck4 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.4.16
dev-lang/python:     2.3.4-r1
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.4
sys-devel/libtool:   1.5.14
virtual/os-headers:  2.6.11-r2
CFLAGS="-march=pentium4 -mtune=pentium4 -pipe -O3 -fweb -frename-registers
-fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -mtune=pentium4 -pipe -O3 -fweb -frename-registers
-fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer
FEATURES="autoconfig distlocks sandbox sfperms"
USE="x86 X alsa apm arts avi berkdb bitmap-fonts crypt cups eds emboss encode
foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg kde
libg++ libwww mad mikmod motif mp3 mpeg ncurses nls nptl ogg oggvorbis opengl
oss pam pdflib perl png python qt quicktime readline sdl spell ssl tcpd truetype
truetype-fonts type1-fonts vorbis xml2 xmms xv zlib userland_GNU kernel_linux


sys-devel/gcc ~x86
sys-devel/gcc-config ~x86
sys-libs/libstdc++-v3 ~x86
sys-libs/glibc ~x86
Comment 1 Jeremy Huddleston (RETIRED) gentoo-dev 2005-08-21 20:52:40 UTC
uhm... I never did a 1.8 release of the patchset, and the current ebuild uses
1.9.  emerge --sync and try again.  Some other dev made a 1.8 release, and I
guess your mirror didn't pick it up.  1.9 is in my devspace, though.
Comment 2 Bob 2005-08-22 03:15:34 UTC
well, it turns out that there *IS* a 1.8 release version of the patch set, so
something about this situation is funny.  after all, it strikes me as odd that
the developer would have more than 10 sequentially numbered patches on his
devspace but that the one file that is missing from the array is the one that is
referenced in this bug report.

i have been using the 1.8 version of the patchset that has been in the portage
tree since my snapshot was loaded on 20050808.  (portage snapshot
portage-20050808.tar.bz2).  the missing file has been in the portage tree for
most of this month -- until it disapeared when the glibc ebuild was updated by
eradicator on Aug 21 at 04:25 UTC.

interestingly, i examined the contents of /usr/portage/distfiles on a number of
my development testbeds which had the 20050808 portage snapshot installed and
had undergone a complete toolkit rebuild a few days ago -- and i found the
following file on them:


this is the file that supposedly never existed.  i have since uploaded this file
to my personal web space.  if you'd like to examine the file to see who the
responsible developer is, you can access the file at:

hopefully this will clarify the situation so that this bug report is not
inappropriately dismissed as invalid.

on the subject of my mirror not picking it up, please examine the contents of
the bug report.  the referenced mirrors include OSUOSL and IBIBLIO. ;-)  one
would expect that those mirrors are up to date, and that the problem isn't
attributable to a mirror that is not up to date.
Comment 3 Bob 2005-08-22 03:30:18 UTC
reopening so that this bug is not dismissed as invalid.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2005-08-22 03:49:05 UTC
grep -C1 patchset /usr/portage/sys-libs/glibc/glibc-2.3.5-r1.ebuild

# Gentoo patchset

Did you emerge sync again? You glibc ebuild is not what's in CVS.
Comment 5 Bob 2005-08-22 11:55:33 UTC
this problem is not related to a problem in an ebuild or to a need to resync. 
this bug is attributable to a patchset file for version 1.8 that has been
inappropriately deleted from the devspace where it is supposed to be maintained.

official policy (as stated in the Repository Markup of the ebuild) is that the
patches are supposed to be maintained on the devspace.  review of the Repository
Markup for ebuild version 1.14 clearly states that the file
"glibc-2.3.5-patches-1.8.tar.bz2" is supposed to remain located here:

looking at the eradicator devspace, all of the glibc-2.3.5 patches except the
1.8 version are indeed located there -- only 1.8 is missing.  it seems obvious
that the resolution of this bug is to restore the missing file.  i've even
posted the file in an easily accessible space to facilitate the fix for you.  ;-)

please stop closing this bug and resolving it without taking appropriate steps
to actually fix the problem.  extensive review of CVS has clearly elucidated the
nature of the problem:  a file that belongs on the devspace has gone Missing In
Action, I've found it, and I'm offering it to the appropriate parties to provide
an accurate resolution to this problem:
Comment 6 Jakub Moc (RETIRED) gentoo-dev 2005-08-22 11:59:55 UTC
(In reply to comment #5)
> this problem is not related to a problem in an ebuild or to a need to resync. 
> this bug is attributable to a patchset file for version 1.8 that has been
> inappropriately deleted from the devspace where it is supposed to be maintained.

No, you completely misunderstood the issue. glibc-2.3.5-r1 does NOT use 1.8
patchset now, it uses 1.9.

So please would you finally try to emerge sync so that we can find out if (and
which) mirrors are outdated?!

Comment 7 Bob 2005-08-22 13:04:20 UTC
> No, you completely misunderstood the issue. 
>glibc-2.3.5-r1 does NOT use 1.8 patchset now, it uses 1.9. 

Actually, I do completely understand the issue.  The reality of the situation is
that there are TWO issues, and that you are only willing to acknowledge one of them.

Issue 1:  whether or not the current ebuild works.  You seem to be focused on
this, but its not a part of the bug report.

Issue 2:  that the devspace patch library is corrupted by the absence of a file
that was inadvertently deleted.  this is the issue related to the bug.

although in your eyes the first issue is relevant and the second issue is moot,
  in my eyes the situation is reversed.  re-syncing and re-emerging will not
make the missing file come back to join the rest of the patch library that is
being maintained on the devspace, will it?

looking at Repository Markups relevant to the issue i'm reporting:

the file is supposed to be maintained:

# This sets the base URI for all gentoo-specific patch files. Note
# that this variable is only important for a brief period of time,
# before your source files get picked up by mirrors. However, it is
# still highly suggested that you keep files in this location
# available.

the file is supposed to be maintained on the eradicator devspace:


get_glibc_src_uri() {
# This variable should be set to the devspace of whoever is currently
# maintaining GLIBC. Please dont set this to mirror, that would just
# make the files unavailable until they get mirrored.
local devspace_uri="" 

and ALL of the other historical patch files are being maintained on the
eradicator devspace *except* the one that is listed in the bug report:

Index of /~eradicator/glibc

Icon  Name                                        Last modified      Size 
Description[DIR] Parent Directory                                              
[   ] c_stubs-2.1.2.tar.bz2                       16-Feb-2005 04:17   10K 
[   ] emul-linux-x86-glibc-1.2-lt.tar.bz2         02-Feb-2005 00:00  3.3M 
[   ] emul-linux-x86-glibc-1.2-nptl.tar.bz2       01-Feb-2005 23:48  4.5M 
[   ] emul-linux-x86-glibc-1.2-nptlonly.tar.bz2   01-Feb-2005 23:44  3.3M 
[   ] emul-linux-x86-glibc-2.3.5-lt.tar.bz2       12-Jul-2005 08:40  7.7M 
[   ] emul-linux-x86-glibc-2.3.5-nptl.tar.bz2     12-Jul-2005 08:45  9.0M 
[   ] emul-linux-x86-glibc-2.3.5-nptlonly.tar.bz2 12-Jul-2005 09:28  6.9M 
[   ] glibc-2.3.4-patches-1.0.tar.bz2             05-Feb-2005 23:45   31K 
[   ] glibc-2.3.4-patches-1.1.tar.bz2             07-Feb-2005 06:36   31K 
[   ] glibc-2.3.4-patches-1.2.tar.bz2             16-Feb-2005 03:46   31K 
[   ] glibc-2.3.4-patches-1.3.tar.bz2             19-Feb-2005 20:08   31K 
[   ] glibc-2.3.4-patches-1.4.tar.bz2             04-Mar-2005 10:35   32K 
[   ] glibc-2.3.4-patches-1.5.tar.bz2             07-Mar-2005 11:24   32K 
[   ] glibc-2.3.4-patches-1.6.tar.bz2             15-Mar-2005 12:45   33K 
[   ] glibc-2.3.4-patches-1.7.tar.bz2             15-Mar-2005 23:02   37K 
[   ] glibc-2.3.5-patches-1.0.tar.bz2             11-Apr-2005 23:43   31K 
[   ] glibc-2.3.5-patches-1.1.tar.bz2             12-Apr-2005 03:06   31K 
[   ] glibc-2.3.5-patches-1.2.tar.bz2             14-Apr-2005 07:24   31K 
[   ] glibc-2.3.5-patches-1.4.tar.bz2             30-Jul-2005 03:56   19K 
[   ] glibc-2.3.5-patches-1.5.tar.bz2             15-Jul-2005 20:23   19K 
[   ] glibc-2.3.5-patches-1.6.tar.bz2             22-Jul-2005 19:24   20K 
[   ] glibc-2.3.5-patches-1.7.tar.bz2             26-Jul-2005 19:58   21K 
[   ] glibc-2.3.5-patches-1.9.tar.bz2             11-Aug-2005 09:37   24K 
[   ] glibc-fedora-20041219T2331.tar.bz2          04-Mar-2005 10:30  744K 
[   ] glibc-fedora-20050524T1606.tar.bz2          14-Jul-2005 08:18  748K 
[   ] glibc-infopages-2.3.4-r1.tar.bz2            10-Feb-2005 23:07  1.2M 
[   ] glibc-infopages-2.3.5.tar.bz2               25-Jul-2005 19:39  1.2M 
[   ] glibc-manpages-2.3.4-r1.tar.bz2             07-Feb-2005 06:36   22K 
[   ] glibc-manpages-2.3.5.tar.bz2                11-Apr-2005 23:43   22K 

Apache Server at Port 80 

This bug report is not about patch version 1.9 and its current status in the
portage tree.  Its not about resyncing and emerging the lastest glibc ebuild. 
Its about patch version 1.8 being absent from the devspace patch library -- in
spite of the requirement that the files in that location be kept available.  it
is evident that there is a glitch in the devspace patch library that needs to be
fixed.  the solution to the problem is quite simple, actually.  just restore the
file.  to make this job easier, i'm even providing the missing file.

I find it quite comical that you keep closing this bug as either
resolved/invalid or resolved/needinfo.  while repeatedly closing the threads
does serve to make the core-system bugzilla statistics look good, it does
absolutely nothing to help users of Gentoo.  if you insist on closing this bug
report without addressing the real problem, please be honest about it and use
Comment 8 Jakub Moc (RETIRED) gentoo-dev 2005-08-22 13:13:52 UTC
There is no missing file, your glibc ebuild in your local portage tree is
outdated. So emerge sync and stop reopening this bug until you do so. If you
*still* experience problems with files missing on mirrors *after* emerge sync,
then reopen this bug and post which mirrors have outdated glibc-2.3.5-r1 ebuild
so that we can fix them.

Closing INVALID.
Comment 9 Bob 2005-08-22 13:28:16 UTC
file added to devspace library.  resolved, valid, and verified.  thanks for your
Comment 10 Alexander Hartner 2010-06-30 03:25:17 UTC
I am getting this error again with glibc-2.11.2-patches-2.tar.bz2 missing. I have tried on two different computers and updated my portage tree.