the problem is that linuxprinting.org/download/foomatic only keeps the foomatic-db tarball from the current day (eg today is 20040305, so the foomatic-db tarball on linuxprinting at that location is www.linuxprinting.org/download/foomatic-db-20040305.tar.gz which means that the "frozen" copies in portage (20040302 is the current one, 20031231 was the last i believe) fail to emerge because they fail to download their respective tarball if you try to emerge it on any day after the exact day for the tarball (eg, i did not emerge foomatic-db-20040302 on 03/02, so it is gone now). the fix is to cp the ebuild to the newest name for today's data of course, but then it gets blown away when you sync and stuff and is really not for users to do. perhaps it would be better to always rely on foomatic-db-current.tar.gz, and then periodically issue -r1, -r2 to upgrade users systems. Reproducible: Always Steps to Reproduce: 1.put a new ebuild for today's foomatic into portage, with the date based naming 2. wait until tomorrow to emerge it as part of your next update or whatever. Actual Results: foomatic-db failed to install and thus my emerge -u world was halted Expected Results: foomatic-db should have installed, and the emerge should have continued. Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.0) ================================================================= System uname: 2.6.0 i686 AMD Athlon(tm) MP 2000+ Gentoo Base System version 1.4.3.13p1 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-mp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-mp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache noauto noclean sandbox userpriv usersandbox" GENTOO_MIRRORS="http://128.213.5.34/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X alsa apm arts avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm gif gpm gtk gtk2 gtkhtml guile imap imlib java jpeg kde libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nls oggvorbis opengl pam pdflib perl pic png python qt qtmt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tiff truetype usb x86 xml2 xmms xv zlib"
There is no problem with that since the file is always on the gentoo mirrors.
>>> emerge (2 of 39) net-print/foomatic-db-20040302 to / >>> Downloading http://128.213.5.34/gentoo/distfiles/foomatic-db-20040302.tar.gz --04:31:56-- http://128.213.5.34/gentoo/distfiles/foomatic-db-20040302.tar.gz => `/usr/portage/distfiles/foomatic-db-20040302.tar.gz' >>> Downloading http://www.linuxprinting.org/download/foomatic/foomatic-db-20040302.tar.gz --04:31:56-- http://www.linuxprinting.org/download/foomatic/foomatic-db-20040302.tar.gz => `/usr/portage/distfiles/foomatic-db-20040302.tar.gz' Resolving www.linuxprinting.org... 216.129.135.176 Connecting to www.linuxprinting.org[216.129.135.176]:80... connected. HTTP request sent, awaiting response... 404 Not Found 04:31:56 ERROR 404: Not Found. !!! Couldn't download foomatic-db-20040302.tar.gz. Aborting. then, that mirror is at fault. (now that i think about it i think this 'mirror' just redirects to the publicized download sites. I just set it by using the mirrorselect tool with the option that says 'download a 100k file to determine speed'. and let it pick the fastest one. but if that 'mirror' just does redirects wouldn't it always be the fastest, since it would redirect to sites that, in general, have lots of bandwidth?. I'll change my mirror, certainly, but...something is up, here.
i downloaded exactly this file and it is completly correct, maybe you have a problem with the route to this server?
