Does anyone know when the new release of Cygwin (for Windows) will come out?
Thanks.
Lubica
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
Cverckova, Lubica wrote:
Does anyone know when the new release of Cygwin (for Windows) will come
out?
When someone reminds me to build it 
I'll look into making a package for 6.4.0-RC5.
--
Glynn Clements <glynn@gclements.plus.com>
On Thu, Sep 24, 2009 at 5:46 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Cverckova, Lubica wrote:
Does anyone know when the new release of Cygwin (for Windows) will come
out?When someone reminds me to build it
I'll look into making a package for 6.4.0-RC5.
Great. Please ping me for the transfer once ready.
Markus
On Wed, Sep 23, 2009 at 9:58 PM, Cverckova, Lubica
<Lubica.Cverckova@hatchmott.com> wrote:
Does anyone know when the new release of Cygwin (for Windows) will come out?
Lubica,
yesterday Glynn has made available 6.4.0.RC5 as Cygwin package:
http://grass.osgeo.org/grass64/binary/mswindows/cygwin
Please test it - perhaps more packages than the setup.ini file
currently suggests are needed. If so, please tell us which so
that we can complete the setup.ini file.
Why this? Because Cygwin has split a series of packages and
it is rather impossible to figure out a priori in which package
the program now are. From a clean installation (as you will have)
it is at least easier than on the fully installed machine which Glynn
is using.
@All: please test the package...
Markus
On Tue, Sep 29, 2009 at 9:50 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Wed, Sep 23, 2009 at 9:58 PM, Cverckova, Lubica
<Lubica.Cverckova@hatchmott.com> wrote:Does anyone know when the new release of Cygwin (for Windows) will come out?
Lubica,
yesterday Glynn has made available 6.4.0.RC5 as Cygwin package:
http://grass.osgeo.org/grass64/binary/mswindows/cygwinPlease test it - perhaps more packages than the setup.ini file
currently suggests are needed.
I have updated the install instructions.
Trying with "wine" on Linux, it looks ok besides the fact that it
wants a "setup.ini.sig" file for the GRASS installation.
How to generate that?
Markus
Markus Neteler wrote:
On Tue, Sep 29, 2009 at 9:50 AM, Markus Neteler <neteler@osgeo.org> wrote:
> On Wed, Sep 23, 2009 at 9:58 PM, Cverckova, Lubica
> <Lubica.Cverckova@hatchmott.com> wrote:
>> Does anyone know when the new release of Cygwin (for Windows) will come out?
>
> Lubica,
>
> yesterday Glynn has made available 6.4.0.RC5 as Cygwin package:
> http://grass.osgeo.org/grass64/binary/mswindows/cygwin
>
> Please test it - perhaps more packages than the setup.ini file
> currently suggests are needed.I have updated the install instructions.
Trying with "wine" on Linux, it looks ok besides the fact that it
wants a "setup.ini.sig" file for the GRASS installation.
How to generate that?
Recent versions of Cygwin's setup.exe verify that setup.ini has been
signed by the Cygwin maintainers.
You can run setup.exe with the -X switch to disable signature
verification.
You can sign setup.ini with your own GPG private key, but you then
have to distribute the corresponding public key to users, and
setup.exe must still be run with the -U switch (allow untrusted keys).
More details:
http://www.cygwin.com/ml/cygwin-announce/2008-08/msg00001.html
--
Glynn Clements <glynn@gclements.plus.com>
On Sat, Oct 3, 2009 at 4:54 AM, Glynn Clements <glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
On Tue, Sep 29, 2009 at 9:50 AM, Markus Neteler <neteler@osgeo.org> wrote:
...
it looks ok besides the fact that it
wants a "setup.ini.sig" file for the GRASS installation.
How to generate that?Recent versions of Cygwin's setup.exe verify that setup.ini has been
signed by the Cygwin maintainers.You can run setup.exe with the -X switch to disable signature
verification.
That's a hard limit for the majority of the Windows users who
want nothing else than click...
You can sign setup.ini with your own GPG private key, but you then
have to distribute the corresponding public key to users, and
setup.exe must still be run with the -U switch (allow untrusted keys).More details:
http://www.cygwin.com/ml/cygwin-announce/2008-08/msg00001.html
Thanks for the background.
At this point I only see the possibility to split the previously
convenient one-pass installation into a two-pass installation:
1. install cygwin
2. start cmd.exe and run setup.exe with -X (needs full path I guess?)
Any better solution possible? Perhaps a grassinstall.bat which
would call setup.exe -X with the URL to setup.ini of GRASS?
Markus
Markus Neteler wrote:
Thanks for the background.
At this point I only see the possibility to split the previously
convenient one-pass installation into a two-pass installation:1. install cygwin
2. start cmd.exe and run setup.exe with -X (needs full path I guess?)Any better solution possible?
Create a shortcut for the setup program and add -X to the command.
This saves having to type out the full path to setup.exe in the
command prompt.
I don't think that we can automate this, as you don't know where
setup.exe will live; it doesn't get installed within the Cygwin tree.
--
Glynn Clements <glynn@gclements.plus.com>
On Sat, Oct 3, 2009 at 11:25 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
Any better solution possible?
Create a shortcut for the setup program and add -X to the command.
This saves having to type out the full path to setup.exe in the
command prompt.
Ah, ok. I have added it to the explanations at
http://grass.osgeo.org/grass64/binary/mswindows/cygwin
@Windows users:
It needs to be revised. Ideally tested by a novice with comments
to me/to the list... just tell us if it works and if it is clear like this.
If not (likely), please suggest how to improve it.
Markus
On Sun, Oct 4, 2009 at 6:57 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Sat, Oct 3, 2009 at 11:25 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:Markus Neteler wrote:
Any better solution possible?
Create a shortcut for the setup program and add -X to the command.
This saves having to type out the full path to setup.exe in the
command prompt.Ah, ok. I have added it to the explanations at
http://grass.osgeo.org/grass64/binary/mswindows/cygwin@Windows users:
It needs to be revised. Ideally tested by a novice with comments
to me/to the list... just tell us if it works and if it is clear like this.
If not (likely), please suggest how to improve it.
we have made some tests here and updated the setup.ini file
plus the instructions.
Starting grass64/cygwin with -tcltk leads to
13 [main] g.gisenv 2100 _cygtls::handle_exceptions: Exception:
STATUS_STACK_OVERFLOW
78803 [main] g.gisenv 2100 open_stackdumpfile: Dumping stack trace
to g.gisenv.exe.stackdump
Subsequently the GUI isn't started (the tcltk startup screen comes up well).
Running on command line:
g.gisenv
returns the settings as it should.
Running on command line:
g.region -p
returns to command line without printing anything.
Perhaps there is a version conflict with the proj libraries?
Markus
Markus Neteler wrote:
Starting grass64/cygwin with -tcltk leads to
13 [main] g.gisenv 2100 _cygtls::handle_exceptions: Exception:
STATUS_STACK_OVERFLOW
78803 [main] g.gisenv 2100 open_stackdumpfile: Dumping stack trace
to g.gisenv.exe.stackdumpSubsequently the GUI isn't started (the tcltk startup screen comes up well).
Running on command line:
g.gisenv
returns the settings as it should.Running on command line:
g.region -p
returns to command line without printing anything.Perhaps there is a version conflict with the proj libraries?
All of the above work for me.
--
Glynn Clements <glynn@gclements.plus.com>