ports/161703: portsnap: look: tINDEX.new: File too large Portsnap metadata appears bogus.
Oliver Hartmann
ohartman at zedat.fu-berlin.de
Sun Oct 16 09:30:17 UTC 2011
>Number: 161703
>Category: ports
>Synopsis: portsnap: look: tINDEX.new: File too large Portsnap metadata appears bogus.
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Oct 16 09:30:16 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator: Oliver Hartmann
>Release: FreeBSD 10.0-CURRENT/amd64 CLANG built
>Organization:
FU Berlin
>Environment:
FreeBSD 10.0-CURRENT #114 r226407 amd64
>Description:
Since for two days for now, my FreeBSD 10.0-CURRENT/amd64 boxes refuses updating the ports tree with the below shown error message. The message came out of the blue and I have no clue how to solve the problem.
What I did so far:
I deleted /etc/portsnap.conf and installed again from /usr/share/examples/etc/. I deleted /var/db/portsnap and all files contained therein. But the same at all.
Error message:
Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
look: tINDEX.new: File too large
Portsnap metadata appears bogus.
Cowardly refusing to proceed any further.
>How-To-Repeat:
Do not know. This happens on FreeBSD 10.0-CURRENT/amd64 boxes.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list