From owner-freebsd-questions@FreeBSD.ORG Mon Sep 4 13:56:59 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DDBE16A4DF for ; Mon, 4 Sep 2006 13:56:59 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C45A43D58 for ; Mon, 4 Sep 2006 13:56:56 +0000 (GMT) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-248-202.51-151.net24.it [151.51.202.248]) (authenticated bits=128) by parrot.aev.net (8.13.7/8.13.6) with ESMTP id k84ECe6S019412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 4 Sep 2006 16:12:47 +0200 (CEST) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.13.8/8.13.3) with ESMTP id k84DuRR2097953 for ; Mon, 4 Sep 2006 15:56:27 +0200 (CEST) (envelope-from ml.diespammer@netfence.it) Message-ID: <44FC309D.6040706@netfence.it> Date: Mon, 04 Sep 2006 15:56:45 +0200 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.5 (X11/20060801) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <44F5B851.9080701@netfence.it> <44FBB65C.30707@ez.pereslavl.ru> In-Reply-To: <44FBB65C.30707@ez.pereslavl.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 212.31.247.179 Subject: Re: apache22 Checksum mismatch X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2006 13:56:59 -0000 Alexey Mikhailov wrote: > If you trust to content of file "apache22/apr_dbd_mysql.rev-50.c" you > can even use "make NO_CHECKSUM=1 install". > But if I were at your place I tried to update "apache22" port and if > this will happen again I would submit PR. Hello. Thanks for the answer. I repeatedly updated my port tree before writing this. I contacted the maintainer, who said it could not reproduce the error. I tried this again after a few days and it worked. I really don't know the reason. I might suspect some sort of caching (transparent proxy?) somewhere between me and the master site, possibly at my ISP, but these are really only speculations. bye & Thanks av.