2010/12/28 Istvan Galgand <[email protected]> > On Tue, Dec 28, 2010 at 07:51:58AM -0500, Jerry wrote: > > For the past few days, I have been having problems updating my ports > > tree via 'portsnap'. It continually gives errors similar to the > > following: > > > > <quote> > > Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. > > Fetching snapshot tag from portsnap2.FreeBSD.org... failed. > > Fetching snapshot tag from portsnap6.FreeBSD.org... failed. > > Fetching snapshot tag from portsnap1.FreeBSD.org... failed. > > Fetching snapshot tag from portsnap5.FreeBSD.org... failed. > > Fetching snapshot tag from portsnap4.FreeBSD.org... done. > > Fetching snapshot metadata... fetch: > http://portsnap4.FreeBSD.org/t/4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a: > No address record > > sha256: 4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a: > No such file or directory > > [: !=: unexpected operator > > mv: rename > 4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a to > tINDEX.new: No such file or directory > > done. > > grep: tINDEX.new: No such file or directory > > look: tINDEX.new: No such file or directory > > > > Portsnap metadata appears bogus. > > Cowardly refusing to proceed any further. > > </quote> > > > > Dear All, > > For the past two days I experienced exactly the same phenomena. By this > morning (CET, Tuesday) the normal operation has been restored. > > Istvan > > Istvan,
What was your solution? _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
