Date: Tue, 6 Jan 2009 03:26:21 -0800 (PST) From: fsw <fredscali@yahoo.fr> To: freebsd-questions@freebsd.org Subject: Re: Portsnap "Not Found" Issues Message-ID: <21308723.post@talk.nabble.com> In-Reply-To: <C103E0EE-D83A-44F2-AEB2-AB135C6A2B7F@goldmark.org> References: <27ade5280901050902r4422b740r9fb7fc473c7fbb70@mail.gmail.com> <20090105181040.84f0e888.cyb.@gmx.net> <EEB5DAD7-6086-4443-9A17-61C927985439@conundrum.com> <C103E0EE-D83A-44F2-AEB2-AB135C6A2B7F@goldmark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, thank for the tip! portsnap3 just worked good right now for me, it surely has to do with the release of FreeBSD 7.1 as said in this post: http://www.nabble.com/FYI%2C-portsnap-problems-td21301895.html Jeffrey Goldberg wrote: > > On Jan 5, 2009, at 2:40 PM, Matthew Pounsett wrote: > >> I'm seeing a similar error on a different metadata file from >> portsnap1. portsnap3 seems to be working for me at the moment. > > I'm having problems on 2 and 3 (haven't tried 1). But I did get much > further when portsnap3. > > $ sudo portsnap -s portsnap3.freebsd.org fetch update > Looking up portsnap3.freebsd.org mirrors... none found. > Fetching snapshot tag from portsnap3.freebsd.org... done. > Fetching snapshot metadata... done. > Updating from Sun Jan 4 11:29:12 CST 2009 to Mon Jan 5 13:49:44 CST > 2009. > Fetching 3 metadata patches.. done. > Applying metadata patches... done. > Fetching 0 metadata files... done. > Fetching 530 patches..... > 10 > .... > 20 > .... > 30 > .... > 40 > .... > 50 > .... > 60 > .... > 70 > .... > 80 > .... > 90 > .... > 100 > .... > 110 > .... > 120 > .... > 130 > .... > 140 > .... > 150 > .... > 160 > .... > 170 > .... > 180 > .... > 190 > .... > 200 > .... > 210 > .... > 220 > .... > 230 > .... > 240 > .... > 250 > .... > 260 > .... > 270 > .... > 280 > .... > 290 > .... > 300 > .... > 310 > .... > 320 > .... > 330 > .... > 340 > .... > 350 > .... > 360 > .... > 370 > .... > 380 > .... > 390 > .... > 400 > .... > 410 > .... > 420 > .... > 430 > ....440....450....460....470....480....490....500....510....520....530 > done. > Applying patches... done. > Fetching 90 new ports or files... /usr/sbin/portsnap: cannot open > e12e83e8518a445d192fa06546e06cfd4eee82824a1a5d36e508ac7cb78968f8.gz: > No such file or directory > snapshot is corrupt. > > Anyway, I'll wait a day or two before trying again. > > Cheers, > > -j > > > -- > Jeffrey Goldberg http://www.goldmark.org/jeff/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > -- View this message in context: http://www.nabble.com/Portsnap-%22Not-Found%22-Issues-tp21294899p21308723.html Sent from the freebsd-questions mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21308723.post>