The emerge --sync fixed the problem. The previous emerge was looking for a slightly older version (6.3 instead of 6.4).
Thanks all! On 1/3/06, Shawn Singh <[EMAIL PROTECTED]> wrote: > thank's all ... I'll see what solution works the best. > > On 1/3/06, Ernie Schroder <[EMAIL PROTECTED]> wrote: > > > > Ernie Schroder wrote: > > > > > John Jolet wrote: > > > > > >> > > >> On Jan 3, 2006, at 2:02 PM, Shawn Singh wrote: > > >> > > >>> Hey all, > > >>> > > >>> When trying to emerge vi, emerge fails on step 1 of 3 because it > > >>> cannot find vim-6.3.068-netrw.tar.bz2. Here is a snippet from the > > >>> last bit of the run of emerge: > > >>> > > >>> 09:55:37 ERROR 404: Not Found. > > >>> > > >>> !!! Couldn't download vim-6.3.068-netrw.tar.bz2. Aborting. > > >>> > > >> try an emerge --sync. > > >> > > >>> I've been getting the same results for the past week and a half. > > >>> Any suggestions? > > >>> > > >>> Thanks, > > >>> > > >>> Shawn Singh > > >> > > >> > > >> From time to time, I find packages that I can't d'load from the site > > >> named in the ebuild. What I do in that case, is to google the package > > >> and dload it from another source. I then move it to > > >> /usr/portage/distfiles. Then a normal emerge <PACKAGE_NAME> will run. > > > > > > here is a source for it: > > > > > > http://cvsup.de.openbsd.org/mirrors/gentoo/distfiles/vim-6.3.068-netrw.tar.bz2 > > > > > > -- > > gentoo-user@gentoo.org mailing list > > > > > > > -- > Shawn Singh > > -- Shawn Singh -- gentoo-user@gentoo.org mailing list
