From nobody@FreeBSD.org Wed Feb 4 11:10:46 2009 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6831D106567B for ; Wed, 4 Feb 2009 11:10:46 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 5515A8FC2B for ; Wed, 4 Feb 2009 11:10:46 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n14BAjgs034916 for ; Wed, 4 Feb 2009 11:10:45 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n14BAj4e034915; Wed, 4 Feb 2009 11:10:45 GMT (envelope-from nobody) Message-Id: <200902041110.n14BAj4e034915@www.freebsd.org> Date: Wed, 4 Feb 2009 11:10:45 GMT From: "Ben C. O. Grimm" To: freebsd-gnats-submit@FreeBSD.org Subject: Update servers for freebsd-update are out-of-sync X-Send-Pr-Version: www-3.1 X-GNATS-Notify: >Number: 131358 >Category: bin >Synopsis: freebsd-update(8): Update servers for freebsd-update are out-of-sync >Confidential: no >Severity: serious >Priority: high >Responsible: cperciva >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 04 11:20:01 UTC 2009 >Closed-Date: >Last-Modified: Sat Feb 28 04:00:47 UTC 2009 >Originator: Ben C. O. Grimm >Release: 7.1-RELEASE-p2 >Organization: None >Environment: FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: The update servers for freebsd-update have been out-of-sync for quite a while now. The server update1.freebsd.org has the latest patches (7.1-REL p2), server update2.freebsd.org is (currently) one patch-level behind (7.1-REL p1). This confuses freebsd-update quite a lot, and it usually takes quite a few retries to get update1.freebsd.org instead of update2.freebsd.org (unless forced by the config). >How-To-Repeat: >Fix: Sync the update servers. >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-bugs->cperciva Responsible-Changed-By: remko Responsible-Changed-When: Wed Feb 4 20:50:01 UTC 2009 Responsible-Changed-Why: reassign to colin http://www.freebsd.org/cgi/query-pr.cgi?pr=131358 From: Colin Percival To: bug-followup@FreeBSD.org, freebsd@bengrimm.net Cc: Subject: Re: bin/131358: freebsd-update: Update servers for freebsd-update are out-of-sync Date: Wed, 04 Feb 2009 13:44:34 -0800 This is working fine for me -- update2 is providing exactly the same bits as update1 is. Is it possible that you have a misbehaving proxy which is giving you some out-of-date bits? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From: "Ben C. O. Grimm" To: Colin Percival Cc: bug-followup@freebsd.org Subject: Re: bin/131358: freebsd-update: Update servers for freebsd-update are out-of-sync Date: Wed, 04 Feb 2009 23:52:49 +0100 Colin Percival wrote: > This is working fine for me -- update2 is providing exactly the same > bits as update1 is. Is it possible that you have a misbehaving proxy > which is giving > you some out-of-date bits? I am behind a transparent Squid proxy, though it never misbehaves under these circumstances. For example portsnap always produces correct results on a wide range of servers behind this proxy. I've never had portsnap alerting me about an older or out-of-date ports tree or anything like that. Perhaps the update servers react differently to HEAD commands issued by Squid when it is checking whether a particular cached object is stale? Anyway, if there are no complaints except mine I will treat this as a local quirk I'll have to deal with in some way. Thanks for your reply! BG From: "Charles Loengard" To: Cc: Subject: Re: bin/131358: freebsd-update: Update servers for freebsd-update are out-of-sync Date: Tue, 24 Feb 2009 10:24:20 -0500 For at least the past few days, update.freebsd.org and update1.freebsd.org have forbidden http navigation below [release]/[arch]. In contrast Update2.freebsd.org does allow full http navigation of the tree. Is this by design? >Unformatted: