From owner-freebsd-stable@freebsd.org Sun May 27 14:33:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFD74F75F35 for ; Sun, 27 May 2018 14:33:01 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 297A582113 for ; Sun, 27 May 2018 14:33:00 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sun, 27 May 2018 16:31:46 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B0FA5ADE-BF26-4925-86DC-780603F66F94.1 envelope-from (authenticated bits=0); Sun, 27 May 2018 16:31:32 +0200 From: Rainer Duffner Message-Id: <0811992D-9ADE-4B46-BA2C-0198149930EE@ultra-secure.de> Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: freebsd-update: cannot open patchlist Date: Sun, 27 May 2018 16:32:43 +0200 In-Reply-To: Cc: FreeBSD Stable To: Randy Bush References: <623D218F-A36F-40DD-9BD2-592E476051E8@ultra-secure.de> X-Mailer: Apple Mail (2.3445.6.18) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=12 total_conn=2 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 5737, bad: 3, connections: 6286, history: 5734, asn_score: 711, asn_connections: 781, asn_good: 712, asn_bad: 1, pass:asn, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2018 14:33:01 -0000 > Am 27.05.2018 um 16:28 schrieb Randy Bush : >=20 > indeed, that fixes it. thank you. ;-) BTDTGTT This is (or was) especially a problem with ezjail=E2=80=99s use of = freebsd-update. Most of the time, freebsd-update works - but when it gets confused, the = quickest solution is often to start from scratch. Which is a real pain if you need to download through a proxy that = doesn=E2=80=99t do http-pipelining (like the Sophos UTM n=C3=A9e Astaro = devices). IIRC, there=E2=80=99s still no way to disable that behavior.