NetBSD Problem Report #36765
From martin@duskware.de Fri Aug 10 15:43:17 2007
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
by narn.NetBSD.org (Postfix) with ESMTP id 8244763B8EA
for <gnats-bugs@gnats.netbsd.org>; Fri, 10 Aug 2007 15:43:17 +0000 (UTC)
Message-Id: <20070810154221.ABA2963B8F0@narn.NetBSD.org>
Date: Fri, 10 Aug 2007 15:42:21 +0000 (UTC)
From: george@galis.org
Reply-To: george@galis.org
To: netbsd-bugs-owner@NetBSD.org
Subject: weekly netbsd-3.tar.bz2 on ftp.netbsd.org
X-Send-Pr-Version: www-1.0
>Number: 36765
>Category: misc
>Synopsis: weekly netbsd-3.tar.bz2 on ftp.netbsd.org
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: misc-bug-people
>State: analyzed
>Class: support
>Submitter-Id: net
>Arrival-Date: Fri Aug 10 15:45:00 +0000 2007
>Closed-Date:
>Last-Modified: Sat Jul 25 21:24:39 +0000 2009
>Originator: George Georgalis
>Release:
>Organization:
>Environment:
>Description:
It saves a ton of time to ftp the pkgsrc bz2
ftp://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2007Q2/pkgsrc-2007Q2.tar.bz2
then extract and do a cvs update on a new machine,
verses doing an initial cvs checkout.
Can a cron be setup to generate archives of netbsd source
tags to accelerate src checkout? Maybe it would reduce load
and bandwidth of the netbsd cvs servers, too?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
From: "George Georgalis" <george@galis.org>
To: netbsd-help@netbsd.org, gnats-bugs@NetBSD.org
Cc: Tobias Nygren <tnn@NetBSD.org>
Subject: Re: misc/36765 archive of netbsd-3 ?
Date: Sat, 11 Aug 2007 20:56:39 -0400
On Sat, Aug 11, 2007 at 09:49:52PM +0200, Tobias Nygren wrote:
>
>There are tarballs for the netbsd-3 branch available at:
>ftp://ftp.NetBSD.org/pub/NetBSD-daily/netbsd-3/pick_date/source/sets/
Thanks, that will be a big help.
I'm scripting out a process to bring a host up to a
local standard which includes pkgsrc and src trees.
With ${pick_date} there are some hoops to figure out
the url.
./pub/NetBSD-daily/netbsd-3/200708100002Z/source/sets/src.tgz
I wonder if there is any reason not to symlink
./pub/NetBSD-daily/netbsd-3/${pick_date} to
./pub/NetBSD-daily/netbsd-3/netbsd-3 every time a
new ${pick_date} comes out? Then we have a fixed url
for whatever most current snapshot of the tag is
available.
Yeah, that puts the tag in the url twice, maybe the
symlink could be called "snapshot"?
// George
--
George Georgalis, information system scientist <IXOYE><
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: misc-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org, george@galis.org
Subject: Re: misc/36765 archive of netbsd-3 ?
Date: Sun, 12 Aug 2007 13:17:03 +0200
On Sun, Aug 12, 2007 at 01:00:06AM +0000, George Georgalis wrote:
> The following reply was made to PR misc/36765; it has been noted by GNATS.
>
> From: "George Georgalis" <george@galis.org>
> To: netbsd-help@netbsd.org, gnats-bugs@NetBSD.org
> Cc: Tobias Nygren <tnn@NetBSD.org>
> Subject: Re: misc/36765 archive of netbsd-3 ?
> Date: Sat, 11 Aug 2007 20:56:39 -0400
>
> On Sat, Aug 11, 2007 at 09:49:52PM +0200, Tobias Nygren wrote:
> >
> >There are tarballs for the netbsd-3 branch available at:
> >ftp://ftp.NetBSD.org/pub/NetBSD-daily/netbsd-3/pick_date/source/sets/
>
> Thanks, that will be a big help.
>
> I'm scripting out a process to bring a host up to a
> local standard which includes pkgsrc and src trees.
> With ${pick_date} there are some hoops to figure out
> the url.
>
> ./pub/NetBSD-daily/netbsd-3/200708100002Z/source/sets/src.tgz
>
> I wonder if there is any reason not to symlink
> ./pub/NetBSD-daily/netbsd-3/${pick_date} to
> ./pub/NetBSD-daily/netbsd-3/netbsd-3 every time a
> new ${pick_date} comes out? Then we have a fixed url
> for whatever most current snapshot of the tag is
> available.
>
> Yeah, that puts the tag in the url twice, maybe the
> symlink could be called "snapshot"?
Or "last"
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
State-Changed-From-To: open->analyzed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 25 Jul 2009 21:24:39 +0000
State-Changed-Why:
Conclusion of releng is that because each port builds (and potentially fails)
independently, a single link wouldn't be adequate. There's a plan to put up
a build status thing on the releng web page to allow easily finding the last
successful build for each port, but AFAIK it isn't deployed yet.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.