From owner-freebsd-questions@FreeBSD.ORG Tue May 4 20:29:47 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F99A106566B for ; Tue, 4 May 2010 20:29:47 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 918248FC0A for ; Tue, 4 May 2010 20:29:46 +0000 (UTC) Received: by fxm15 with SMTP id 15so4066117fxm.13 for ; Tue, 04 May 2010 13:29:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=pCt2xVvNN0gtwk0dpenGQab4xH76yKFYgI96rvIQ/3E=; b=HBM+UyPAqcZdA1QVnyOHzUoP/hvmVuywYK8Nt9i0LuZb0GXSIh7156Z1HqNolz9EhW aQJwcKVJo2jnadpQ90inh5ZJ+eq2i2KBqRpqe6DxCqrlg3BeUyHOASg3BZrcqoadjTZe hI3Pr2ecEP1kqW5J6QwcMJVt1xJ4dca2XauJQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=oP+yPj+EFtocQMl5Zl6iq3eZ98gHpirpqS2IkKY6zmtRA/8s8OgqtDHRLS2VO0uu8m Ve6oLdLGECf9ziHLlfhiP1IxqxJIXBsoxs18RtfO7HMuvUqh1g4hwuUUTf1JzrDu/O9W dg3nKBBbnw/imGzfsSzHR+EwA+SwBWfEEe5g0= Received: by 10.239.156.84 with SMTP id l20mr467246hbc.2.1273004978170; Tue, 04 May 2010 13:29:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.193.77 with HTTP; Tue, 4 May 2010 13:29:18 -0700 (PDT) In-Reply-To: <20100423001025.3138d003@gumby.homeunix.com> References: <20100423001025.3138d003@gumby.homeunix.com> From: Eitan Adler Date: Tue, 4 May 2010 23:29:18 +0300 Message-ID: To: RW Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Portsnap metadata is correctly signed, but contains at least one line which appears bogus. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 20:29:47 -0000 Woops - I missed this email > Eitan Adler wrote: > >> I've been getting the following message a lot lately. >> >> Portsnap metadata is correctly signed, but contains >> at least one line which appears bogus. >> I'm still getting this error even after a complete removal of /var/db/ports= nap > If the metadata is correctly signed then it sounds like it should be a > server-side problem. OTOH =C2=A0no-one else is mentioning it, are you > running portsnap from a reasonably recent release? Yeah - I'm running from 8-RELEASE > > It might be instructive to edit portsnap, look for the places where > fetch_metadata_freakout is called and have it make a copy of the > offending file. I added some echo lines to help if grep -qvE "^[0-9A-Z.]+\|[0-9a-f]{64}$" tINDEX.new; then fetch_metadata_freakout return 1 fi appears to be the part which goes nuts.