Your message dated Thu, 26 Feb 2015 00:14:54 +0100
with message-id <54ee576e.30...@xs4all.nl>
and subject line Re: Bug#648357: grass: segfault with -l flag in r.proj
has caused the Debian Bug report #648357,
regarding grass: segfault with -l flag in r.proj
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
648357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 6.4.1-1
Severity: normal
Dear Maintainer,
Doing 'r.proj -l location=ANY_LOCATION' gives a segmentation fault in
that program, even though grass session is not affected.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'proposed-updates'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grass depends on:
ii konsole [x-terminal-emulator] 4:4.6.5-1
ii lesstif2 1:0.95.2-1
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libfftw3-3 3.2.2-1
ii libfreetype6 2.4.7-2
ii libgcc1 1:4.6.2-4
ii libgdal1-1.7.0 1.7.3-6+b1
ii libgl1-mesa-glx [libgl1] 7.11-6
ii libglu1-mesa [libglu1] 7.11-6
ii libice6 2:1.0.7-2
ii libmysqlclient16 5.1.58-1
ii libncurses5 5.9-4
ii libpng12-0 1.2.46-3
ii libpq5 9.1.1-3
ii libproj0 4.7.0-1
ii libreadline6 6.2-7
ii libsm6 2:1.2.0-2
ii libsqlite3-0 3.7.9-2
ii libstdc++6 4.6.2-4
ii libtiff4 3.9.5-2
ii libx11-6 2:1.4.4-3
ii libxext6 2:1.3.0-3
ii libxmu6 2:1.1.0-3
ii libxrender1 1:0.9.6-2
ii libxt6 1:1.1.1-2
ii python 2.7.2-9
ii python-numpy 1:1.5.1-3
ii python-opengl 3.0.1~b2-1
ii python-wxgtk2.8 2.8.12.1-2
ii tcl8.5 8.5.10-1
ii tk8.5 8.5.10-1
ii unixodbc 2.2.14p2-5
ii xterm [x-terminal-emulator] 276-1
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages grass recommends:
ii ghostscript 9.04~dfsg-2
Versions of packages grass suggests:
ii avce00 2.0.0-2
ii curl 7.21.7-3
ii e00compr 1.0.1-2
ii gdal-bin 1.7.3-6+b1
ii gnuplot 4.4.0-1.1
ii gpsbabel <none>
ii gpstrans <none>
ii grass-doc 6.4.1-1
ii netpbm 2:10.0-15
ii proj-bin 4.7.0-1
ii wget 1.13.4-1
ii xml2 0.4-3
-- no debconf information
--
Seb
--- End Message ---
--- Begin Message ---
fixed 648357 grass/6.4.4-1
thanks
On Fri, 11 Nov 2011 08:27:53 -0600 Sebastian P. Luque
<splu...@gmail.com> wrote:
> On Fri, 11 Nov 2011 13:53:45 +0100,
> "Francesco P. Lovergine" <fran...@debian.org> wrote:
>
> > On Thu, Nov 10, 2011 at 01:11:12PM -0600, Sebastian Luque wrote:
> >> Doing 'r.proj -l location=ANY_LOCATION' gives a segmentation fault in
> >> that program, even though grass session is not affected.
>
> > It does not seem so even if having to specify an explicit existing
> > mapset seems annoying and counter-intuitive (but it is not the only
> > case):
>
> [...]
>
> I get the same results when specifying the mapset argument, but if I
> don't supply it, then I see:
>
> GRASS 6.4.1 > r.proj -l location=spearfish60
> Segmentation fault
This is fixed in 6.4.4-1:
GRASS 6.4.4 (spearfish60):~ > r.proj -l location=spearfish60
WARNING: Input and output locations are the same
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
