[GRASS-dev] location wizard borked

On Mar 10, 2009, at 5:50 AM, <grass-dev-request@lists.osgeo.org> wrote:

Date: Tue, 10 Mar 2009 11:54:50 +0100
From: Martin Landa <landa.martin@gmail.com>
Subject: Re: [GRASS-dev] location wizard borked
To: Vincent Bain <bain@toraval.fr>
Cc: grass-dev <grass-dev@lists.osgeo.org>
Message-ID:
  <f8fe65c40903100354y2d6cfdaanb70b663e639347cc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

2009/3/10 Vincent Bain <bain@toraval.fr>:

related to the location wizard, perhaps what follows does not deal with
any sort of bug but my misuse of the location creation process :

If you need to create from scratch a new gisdabe, located elsewhere than
the current one, the location wizard first writes your new location
directory in the /current/ gisdbase instead of the new one you've just
set. Then when you define a new mapset or want to start from within
PERMANENT, the application fails, with this message :

seems to work for me.

1. Create new directory for gisdbase (e.g. $HOME/grassdata1) - mkdir
2. Choose gisdbase
3. Run location wizard
4. New location created in $HOME/grassdata1

?

Martin

I can confirm this. Regardless of whether you browse to a new directory in the startup screen or put in a new gisdbase directory in the location wizard, it only makes a location in the "current" gisdbase.

Michael

Hi,

2009/3/10 Michael Barton <michael.barton@asu.edu>:

[...]

I can confirm this. Regardless of whether you browse to a new directory in
the startup screen or put in a new gisdbase directory in the location
wizard, it only makes a location in the "current" gisdbase.

mkdir $HOME/grassdata_test

grass65 -wx

set new gisdbase (enter / browse)

run location wizard

location created in new gisdbase

??

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

On Mar 10, 2009, at 8:37 AM, Martin Landa wrote:

Hi,

2009/3/10 Michael Barton <michael.barton@asu.edu>:

[...]

I can confirm this. Regardless of whether you browse to a new directory in
the startup screen or put in a new gisdbase directory in the location
wizard, it only makes a location in the "current" gisdbase.

mkdir $HOME/grassdata_test

grass65 -wx

set new gisdbase (enter / browse)

run location wizard

location created in new gisdbase

??

Martin

Yep. Just did this and it doesn't work for me. OS related? I'm trying to find out what OS Vincent is running.

Michael

Right now I'm switching to 65 develbranch...

I run grass on Ubuntu 8.04 on my PC and debian 5 on my laptop (not
accessible at the moment to test).

Vincent

Le mardi 10 mars 2009 à 08:39 -0700, Michael Barton a écrit :

On Mar 10, 2009, at 8:37 AM, Martin Landa wrote:

> Hi,
>
> 2009/3/10 Michael Barton <michael.barton@asu.edu>:
>
> [...]
>
>> I can confirm this. Regardless of whether you browse to a new
>> directory in
>> the startup screen or put in a new gisdbase directory in the location
>> wizard, it only makes a location in the "current" gisdbase.
>
> mkdir $HOME/grassdata_test
>
> grass65 -wx
>
> set new gisdbase (enter / browse)
>
> run location wizard
>
> location created in new gisdbase
>
> ??
>
> Martin

Yep. Just did this and it doesn't work for me. OS related? I'm trying
to find out what OS Vincent is running.

Michael

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Well, tried on a fresh grass65, the problem remains...

VB