NetBSD Problem Report #46482

From reed@reedmedia.net  Sat May 26 23:24:39 2012
Return-Path: <reed@reedmedia.net>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 572D763B882
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 26 May 2012 23:24:39 +0000 (UTC)
Message-Id: <19271-1338074678@reedmedia.net>
Date: Sat, 26 May 2012 18:24:38 -0500
From: reed@reedmedia.net
Reply-To: reed@reedmedia.net
To: gnats-bugs@gnats.NetBSD.org
Subject: wrong directory to pkgsrc tarball in sysinst
X-Send-Pr-Version: 3.95

>Number:         46482
>Category:       install
>Synopsis:       wrong directory to pkgsrc tarball in sysinst
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 26 23:25:00 +0000 2012
>Last-Modified:  Thu Jun 14 14:25:01 +0000 2012
>Originator:     reed@reedmedia.net
>Release:        NetBSD 6.0_BETA2
>Organization:
>Environment:
>Description:
In sysinst...

The download and extract step for pkgsrc fails because 
http://ftp.netbsd.org/pub/pkgsrc/stable/pkgsrc.tgz  does not exist. See
http://ftp.netbsd.org/pub/pkgsrc/stable/ for other options
like tar.gz , tar.bz2 , and tar.xz

The menu does not allow choosing file name.

Not a quick fix for me as I saw it uses dist_postfix which is wrong
in this case.

>How-To-Repeat:

>Fix:


>Audit-Trail:
From: Julian Fagir <gnrp@komkon2.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
Date: Sun, 27 May 2012 01:55:26 +0200

 Hi,

 > The download and extract step for pkgsrc fails because 
 > http://ftp.netbsd.org/pub/pkgsrc/stable/pkgsrc.tgz  does not exist. See
 > http://ftp.netbsd.org/pub/pkgsrc/stable/ for other options
 > like tar.gz , tar.bz2 , and tar.xz
 > 
 > The menu does not allow choosing file name.
 this could be changed. But should it? We don't allow choosing the rest of the
 filenames, though you could argue that choosing an older pkgsrc release would
 be useful.

 > Not a quick fix for me as I saw it uses dist_postfix which is wrong
 > in this case.
 I'm rather interested in what caused this... For pkgsrc-2011Q4, apparently
 there were symlinks created, for the latter ones not.
 Which policy should go first, filenames or namings in sysinst?

 Regards, Julian

From: "Jeremy C. Reed" <reed@reedmedia.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
Date: Sat, 26 May 2012 19:17:21 -0500 (CDT)

 >  > The menu does not allow choosing file name.
 >  this could be changed. But should it? We don't allow choosing the rest of the
 >  filenames, though you could argue that choosing an older pkgsrc release would
 >  be useful.

 No it is not needed. I am not requesting it.

 >  I'm rather interested in what caused this... For pkgsrc-2011Q4, apparently
 >  there were symlinks created, for the latter ones not.
 >  Which policy should go first, filenames or namings in sysinst?

 I guess symlinks can be made and then some tool to check them daily to 
 make sure exists.

 I see now that the current/ directory does have the symlinks but the 
 stable/ directory does not.

 I can probably make the symlinks myself, but I don't know if something 
 will end up replacing them.

From: Jeff Rizzo <riz@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: "Jeremy C. Reed" <reed@reedmedia.net>, install-manager@netbsd.org
Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
Date: Sun, 27 May 2012 09:20:35 -0700

 On 5/26/12 5:20 PM, Jeremy C. Reed wrote:
 > The following reply was made to PR install/46482; it has been noted by GNATS.
 >
 > From: "Jeremy C. Reed"<reed@reedmedia.net>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
 > Date: Sat, 26 May 2012 19:17:21 -0500 (CDT)
 >
 >   >   >  The menu does not allow choosing file name.
 >   >   this could be changed. But should it? We don't allow choosing the rest of the
 >   >   filenames, though you could argue that choosing an older pkgsrc release would
 >   >   be useful.
 >
 >   No it is not needed. I am not requesting it.
 >
 >   >   I'm rather interested in what caused this... For pkgsrc-2011Q4, apparently
 >   >   there were symlinks created, for the latter ones not.
 >   >   Which policy should go first, filenames or namings in sysinst?
 >
 >   I guess symlinks can be made and then some tool to check them daily to
 >   make sure exists.
 >
 >   I see now that the current/ directory does have the symlinks but the
 >   stable/ directory does not.
 >
 >   I can probably make the symlinks myself, but I don't know if something
 >   will end up replacing them.
 >

 This would be my fault;  I created the symlinks by hand when adding the 
 pkgsrc functionality, but did not ensure they existed in all 
 directories.  The correct fix would be to make sure they exist (and that 
 any automated processes re-create them when new directories are made).


From: "Jeremy C. Reed" <reed@reedmedia.net>
To: gnats-bugs@NetBSD.org
Cc: install-manager@netbsd.org
Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
Date: Thu, 14 Jun 2012 09:22:49 -0500 (CDT)

 On Sun, 27 May 2012, Jeff Rizzo wrote:

 > This would be my fault;  I created the symlinks by hand when adding 
 > the pkgsrc functionality, but did not ensure they existed in all 
 > directories.  The correct fix would be to make sure they exist (and 
 > that any automated processes re-create them when new directories are 
 > made).

 I created the symlinks:

 $ ln -s pkgsrc.tar.bz2 pkgsrc.tbz
 $ ln -s pkgsrc.tar.gz pkgsrc.tgz                                               
 $ ln -s pkgsrc.tar.xz pkgsrc.txz 
 $ pwd
 /pub/pkgsrc/stable

 http://ftp.netbsd.org/pub/pkgsrc/stable/pkgsrc.tgz  now exists.

>Unformatted:

Home	PR Database Search