Processed: grass-gui: function i.class does not run properly

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 763298 grass/7.0.0~rc1+ds1-1~exp1
Bug #763298 [grass-gui] Bug report about the package grass-gui 6.4.4-1 : 
function i.class does not run properly
Marked as fixed in versions grass/7.0.0~rc1+ds1-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#763298: marked as done (Bug report about the package grass-gui 6.4.4-1 : function i.class does not run properly)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 15:10:42 +0100
with message-id <563f57e2.8050...@xs4all.nl>
and subject line grass-gui: function i.class does not run properly
has caused the Debian Bug report #763298,
regarding Bug report about the package grass-gui 6.4.4-1 : function i.class 
does not run properly
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.)


-- 
763298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass-gui
Version: 6.4.4-1
Severity: Normal
Justification: some functionnality does not run properly


Good day,

When I try to start the module i.class in graphical mode, located in the
Imagery menu, I get the following message in the terminal :

=
If you wish to resize the X monitor, do so now. Window size is
locked while interactive modules are running.
=

/usr/lib/grass64/etc/grass-run.sh: 32: /usr/lib/grass64/etc/grass-run.sh:
i.class: not found

ERROR: "i.class" exited abnormally. Press  to continue.

I don't know how to resolve the problem. The module needs Xterm but it
functions properly on my XFCE desktop. I have tried to reinstall both grass
gis and Xterm but it does not resolve the problem.

Sincerely,
Etienne MAHE

--
--
-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64

Kernel: Linux 3.16.2 amd64
--- End Message ---
--- Begin Message ---
fixed 763298 grass/7.0.0~rc1+ds1-1~exp1
thanks

GRASS 7 is in testing/unstable for some time now,
and it doesn't include i.class any more.--- 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

Bug#620462: marked as done (grass: output of function g.mapsets -l truncated in two first caracteres)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 15:23:06 +0100
with message-id <563f5aca.9010...@xs4all.nl>
and subject line Re: output of function g.mapsets -l truncated in two first 
caracteres
has caused the Debian Bug report #620462,
regarding grass: output of function g.mapsets -l truncated in two first 
caracteres
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.)


-- 
620462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 6.4.0~rc6+42329-3
Severity: normal

In window 'Output - GIS.m', when I type de command

g.mapsets -l

it appears the list os mapsets, but the first element has the two first
characteres truncated (or hidden). For example, the output

sqlite user1 PERMANENT

appears that way:

lite user1 PERMANENT

If I click run several times, the old outputs correct, but the newer appears
truncated. if I select the output, with mouse, backwards, when I reach the
start of the  string, the hidden two first characters appears.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (100, 'testing'), (95, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grass depends on:
ii  gnome-terminal [x-termi 2.30.2-1 The GNOME terminal emulator applic
ii  lesstif2    1:0.95.2-1   OSF/Motif 2.1 implementation relea
ii  libc6   2.11.2-11    Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-6 The Cairo 2D vector graphics libra
ii  libfftw3-3  3.2.2-1  library for computing Fast Fourier
ii  libfontconfig1  2.8.0-2.1    generic font configuration library
ii  libfreetype6    2.4.4-1  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.5.2-4    GCC support library
ii  libgdal1-1.6.0  1.6.3-4+b1   Geospatial Data Abstraction Librar
ii  libgl1-mesa-glx [libgl1 7.7.1-4  A free implementation of the OpenG
ii  libglu1-mesa [libglu1]  7.7.1-4  The OpenGL utility library (GLU)
ii  libice6 2:1.0.7-1    X11 Inter-Client Exchange library
ii  libmysqlclient16    5.1.49-3 MySQL database client library
ii  libncurses5 5.7+20100313-5   shared libraries for terminal hand
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libpq5  9.0.3-1  PostgreSQL C client library
ii  libproj0    4.7.0-1  Cartographic projection library
ii  libpython2.6    2.6.6-8+b1   Shared Python runtime library (ver
ii  libreadline6    6.1-3    GNU readline and history libraries
ii  libsm6  2:1.2.0-1    X11 Session Management library
ii  libsqlite3-0    3.7.5-1  SQLite 3 shared library
ii  libstdc++6  4.5.2-4  The GNU Standard C++ Library v3
ii  libtiff4    3.9.4-7  Tag Image File Format (TIFF) libra
ii  libwxbase2.8-0  2.8.10.1-3+b1    wxBase library (runtime) - non-GUI
ii  libwxgtk2.8-0   2.8.10.1-3+b1    wxWidgets Cross-platform C++ GUI t
ii  libx11-6    2:1.4.1-5    X11 client-side library
ii  libxext6    2:1.2.0-2    X11 miscellaneous extension librar
ii  libxmu6 2:1.1.0-1    X11 miscellaneous utility library
ii  libxrender1 1:0.9.6-1    X Rendering Extension client libra
ii  libxt6  1:1.1.1-1    X11 toolkit intrinsics library
ii  tcl8.4  8.4.19-4 Tcl (the Tool Command Language) v8
ii  tk8.4   8.4.19-4 Tk toolkit for Tcl and X11, v8.4 -
ii  unixodbc    2.2.14p2-2   ODBC tools libraries
ii  xterm [x-terminal-emula 269-1    X terminal emulator
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages grass recommends:
ii  ghostscript 9.01~dfsg-2  interpreter for the PostScript lan
ii  python  2.6.6-3+squeeze6 interactive high-level object-orie
ii  python-numpy    1:1.4.1-5    Numerical Python adds a fast array

Versions of packages grass suggests:
pn  avce00     (no description available)
pn  e00compr   (no description available)
ii  gdal-bin  1.7.3-2    Geospatial Data Abstraction

Processed: Re: output of function g.mapsets -l truncated in two first caracteres

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 620462 upstream unreproducible
Bug #620462 [grass] grass: output of function g.mapsets -l truncated in two 
first caracteres
Added tag(s) upstream and unreproducible.
> forwarded 620462 https://trac.osgeo.org/grass/ticket/606
Bug #620462 [grass] grass: output of function g.mapsets -l truncated in two 
first caracteres
Set Bug forwarded-to-address to 'https://trac.osgeo.org/grass/ticket/606'.
> fixed 620462 grass/7.0.0~rc1+ds1-1~exp1
Bug #620462 [grass] grass: output of function g.mapsets -l truncated in two 
first caracteres
Marked as fixed in versions grass/7.0.0~rc1+ds1-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
620462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#379913: grass-doc: whatis parse errors in manpages

2015-11-08 Thread Markus Neteler 
(cc grass-dev)

On Sun, Nov 8, 2015 at 4:44 PM, Sebastiaan Couwenberg
 wrote:
> This issue is still present in GRASS 7.0.1.
...
> We need a lot more changes like r37865 [1] adding NAME sections to the
> HTML documentation to fix all these whatis issues.
>
> [1] https://trac.osgeo.org/grass/changeset/37865

A lot of these pages are auto-generated, so adding a "NAME" section is
now theoretically easy.

But before doing so, we need to understand how to deal with the 102
"topic_xxx.html" pages like e.g.

https://grass.osgeo.org/grass70/manuals/topic_sampling.html

In all those "NAME" does not really make sense. Likewise the 7
xxxintro.html pages like e.g.
https://grass.osgeo.org/grass70/manuals/imageryintro.html

Any ideas?

Markus

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#676190: grass-gui: gcpmanager fails to list source mapsets if non-ascii characters in grass data dir path

2015-11-08 Thread Sebastiaan Couwenberg 
Control: tags -1 upstream unreproducible moreinfo

Hi Torsti,

We've have GRASS 7 in testing/unstable for some time now, and while the
upstream issue is still open, it seems it has been fixed in GRASS 7.

I can successfully open a GRASS GIS database directory by selecting the
path /home/user/tmp/Työpöytä/grassdata/, selecting the 'spearfish60'
GRASS location, selecting either of the GRASS Mapsets and starting the
GRASS session.

Can you confirm that the issue is fixed in the GRASS 7 packages in
testing/unstable?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#341643: marked as done (grass-doc: manpage NAME sections often too long)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 14:21:20 +0100
with message-id <563f4c50.9060...@xs4all.nl>
and subject line Re: grass-doc: manpage NAME sections often too long
has caused the Debian Bug report #341643,
regarding grass-doc: manpage NAME sections often too long
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.)


-- 
341643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass-doc
Version: 6.0.1-1
Severity: wishlist

These should not be so long as to wrap on the screen. The worst
offenders are:
$ apropos -s 1grass .|perl -nlwe 'print length'|sort -rn|uniq -c
  1 472
  1 345
  1 342 ...
They should be like
$ apropos -e cat
cat (1)  - concatenate files and print on the standard output
nice and compact.

--- End Message ---
--- Begin Message ---
fixed 341643 grass/6.4.0~rc6+42329-3
thanks

On Sun, 28 Oct 2007 16:22:04 +0100 Markus Neteler wrote:
> This looks WAY better now:
> http://grass.itc.it/grass63/manuals/html63_user/full_index.html

For grass64 & grass70 it looks much better too.

I think we can consider this fixed since squeeze.

> Can you re-run the apropos command?
> apropos -s 1grass .|perl -nlwe 'print length'|sort -rn|uniq -c

Just for the record, here's the top 50 for GRASS 7.0.1:

$ apropos -s 1grass .|perl -nlwe 'print length'|sort -rn|uniq -c|head -50
  1 215
  1 198
  1 186
  1 178
  2 174
  2 164
  1 160
  1 154
  2 153
  1 152
  1 146
  1 145
  3 144
  2 142
  3 141
  1 140
  1 139
  1 138
  2 135
  3 133
  1 131
  4 130
  2 129
  2 128
  3 127
  2 126
  1 125
  2 123
  5 122
  1 121
  4 120
  1 119
  1 118
  2 117
  2 116
  3 115
  3 114
  3 113
  4 112
  5 111
  4 110
  4 109
  4 108
  4 107
  6 106
  4 105
  6 104
  2 103
  5 102
  4 101

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

Processed: Re: grass-doc: manpage NAME sections often too long

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 341643 grass/6.4.0~rc6+42329-3
Bug #341643 [grass-doc] grass-doc: manpage NAME sections often too long
Marked as fixed in versions grass/6.4.0~rc6+42329-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
341643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: wxpython: save of workspace on exit crasches on non-ascii layer name and corrupts workspace file

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 595910 upstream
Bug #595910 [grass] wxpython: save of workspace on exit crasches on non-ascii 
layer name and corrupts workspace file
Added tag(s) upstream.
> fixed 595910 grass/7.0.0~rc1+ds1-1~exp1
Bug #595910 [grass] wxpython: save of workspace on exit crasches on non-ascii 
layer name and corrupts workspace file
Marked as fixed in versions grass/7.0.0~rc1+ds1-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#595910: marked as done (wxpython: save of workspace on exit crasches on non-ascii layer name and corrupts workspace file)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 15:33:32 +0100
with message-id <563f5d3c.5090...@xs4all.nl>
and subject line Re: wxpython: save of workspace on exit crasches on non-ascii 
layer name and corrupts workspace file
has caused the Debian Bug report #595910,
regarding wxpython: save of workspace on exit crasches on non-ascii layer name 
and corrupts workspace file
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.)


-- 
595910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 6.4.0~rc6+42329-1+b1
Severity: normal

To replicate:

Open a workspace file under wxpython. Change a map layer name on the "map 
layers for each display" and include a non-ascii letter, like 'ä'. Exit gui. 
When 
asked to save changes to workspace, answer 'Yes'. result:

--
Writing current settings to workspace file failed ('ascii' codec can't encode 
character u'\xe4' in position 39: ordinal not in range(128)).
-

What should happen: the user is brought back to the layers display, and the 
error message should be somewhat more clear: "non-ascii / Unicode characters in 
layer names cannot be used."

What happens: gui closes anyway, and leaves a corrupted workspace file behind. 
Causes lots of irritation in case of a complex workspace setting.

Best,

Harri K.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grass depends on:
ii  eterm [x-terminal-emula 0.9.5-2  Enlightened Terminal Emulator
ii  gnome-terminal [x-termi 2.30.2-1 The GNOME terminal emulator applic
ii  lesstif21:0.95.2-1   OSF/Motif 2.1 implementation relea
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-5 The Cairo 2D vector graphics libra
ii  libfftw3-3  3.2.2-1  library for computing Fast Fourier
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-1  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.4.4-8GCC support library
ii  libgdal1-1.6.0  1.6.3-4  Geospatial Data Abstraction Librar
ii  libgl1-mesa-glx [libgl1 7.7.1-4  A free implementation of the OpenG
ii  libglu1-mesa [libglu1]  7.7.1-4  The OpenGL utility library (GLU)
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libmysqlclient165.1.49-1 MySQL database client library
ii  libncurses5 5.7+20100313-2   shared libraries for terminal hand
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libpq5  8.4.4-2  PostgreSQL C client library
ii  libproj04.7.0-1  Cartographic projection library
ii  libpython2.62.6.6~rc1-1  Shared Python runtime library (ver
ii  libreadline66.1-3GNU readline and history libraries
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libsqlite3-03.7.2-1  SQLite 3 shared library
ii  libstdc++6  4.4.4-8  The GNU Standard C++ Library v3
ii  libtiff43.9.4-3  Tag Image File Format (TIFF) libra
ii  libwxbase2.8-0  2.8.10.1-3   wxBase library (runtime) - non-GUI
ii  libwxgtk2.8-0   2.8.10.1-3   wxWidgets Cross-platform C++ GUI t
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxext62:1.1.2-1X11 miscellaneous extension librar
ii  libxmu6 2:1.0.5-1X11 miscellaneous utility library
ii  libxrender1 1:0.9.6-1X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  rxvt-unicode [x-termina 9.07-2   RXVT-like terminal emulator with U
ii  tcl8.4  8.4.19-4 Tcl (the Tool Command Language) v8
ii  tk8.4   8.4.19-4 Tk toolkit for Tcl and X11, v8.4 -
ii  unixodbc2.2.14p2-1   ODBC tools libraries
ii  xterm [x-terminal-emula 261-1X terminal emulator
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Bug#379913: grass-doc: whatis parse errors in manpages

2015-11-08 Thread Sebastiaan Couwenberg 
Control: tags -1 upstream
Control: found -1 grass/7.0.1-2

On Sun, 14 Jun 2009 15:42:06 +1200 Hamish  wrote:
> fwiw, these are all non-binary help pages & introductions which lack
> standardized module description that the conversion script uses to
> get the whatis name. Typically those are hand coded HTML.
> 
> hopefully fixed now upstream in grass 6.5 & 7, after testing it can be
> backported to 6.4.

This issue is still present in GRASS 7.0.1.

mandb -c reports 156 warnings for grass. See attached mandb_grass.log.

lintian reports 153 manpage-has-bad-whatis-entry issues [0] for grass
(7.0.2~rc2-1~exp1). See attached grass_manpage-has-bad-whatis-entry.log.

[0] https://lintian.debian.org/tags/manpage-has-bad-whatis-entry.html

We need a lot more changes like r37865 [1] adding NAME sections to the
HTML documentation to fix all these whatis issues.

[1] https://trac.osgeo.org/grass/changeset/37865

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
mandb: warning: /usr/share/man/man1/r.li.daemon.1grass.gz: whatis parse for r.li.daemon(1grass) failed
mandb: warning: /usr/share/man/man1/topic_projection.1grass.gz: whatis parse for topic_projection(1grass) failed
mandb: warning: /usr/share/man/man1/imageryintro.1grass.gz: whatis parse for imageryintro(1grass) failed
mandb: warning: /usr/share/man/man1/topic_classification.1grass.gz: whatis parse for topic_classification(1grass) failed
mandb: warning: /usr/share/man/man1/topic_category.1grass.gz: whatis parse for topic_category(1grass) failed
mandb: warning: /usr/share/man/man1/topic_cost_surface.1grass.gz: whatis parse for topic_cost_surface(1grass) failed
mandb: warning: /usr/share/man/man1/rasterintro.1grass.gz: whatis parse for rasterintro(1grass) failed
mandb: warning: /usr/share/man/man1/wxGUI.rlisetup.1grass.gz: whatis parse for wxGUI.rlisetup(1grass) failed
mandb: warning: /usr/share/man/man1/wxGUI.vnet.1grass.gz: whatis parse for wxGUI.vnet(1grass) failed
mandb: warning: /usr/share/man/man1/topic_support.1grass.gz: whatis parse for topic_support(1grass) failed
mandb: warning: /usr/share/man/man1/topic_timestamp.1grass.gz: whatis parse for topic_timestamp(1grass) failed
mandb: warning: /usr/share/man/man1/topic_surface.1grass.gz: whatis parse for topic_surface(1grass) failed
mandb: warning: /usr/share/man/man1/topic_landscape_structure_analysis.1grass.gz: whatis parse for topic_landscape_structure_analysis(1grass) failed
mandb: warning: /usr/share/man/man1/vectorascii.1grass.gz: whatis parse for vectorascii(1grass) failed
mandb: warning: /usr/share/man/man1/topic_transect.1grass.gz: whatis parse for topic_transect(1grass) failed
mandb: warning: /usr/share/man/man1/topic_algebra.1grass.gz: whatis parse for topic_algebra(1grass) failed
mandb: warning: /usr/share/man/man1/topic_profile.1grass.gz: whatis parse for topic_profile(1grass) failed
mandb: warning: /usr/share/man/man1/wxGUI.timeline.1grass.gz: whatis parse for wxGUI.timeline(1grass) failed
mandb: warning: /usr/share/man/man1/topic_geomorphology.1grass.gz: whatis parse for topic_geomorphology(1grass) failed
mandb: warning: /usr/share/man/man1/wxGUI.vdigit.1grass.gz: whatis parse for wxGUI.vdigit(1grass) failed
mandb: warning: /usr/share/man/man1/topic_volume.1grass.gz: whatis parse for topic_volume(1grass) failed
mandb: warning: /usr/share/man/man1/topic_map_management.1grass.gz: whatis parse for topic_map_management(1grass) failed
mandb: warning: /usr/share/man/man1/topic_connection_settings.1grass.gz: whatis parse for topic_connection_settings(1grass) failed
mandb: warning: /usr/share/man/man1/topic_multispectral.1grass.gz: whatis parse for topic_multispectral(1grass) failed
mandb: warning: /usr/share/man/man1/raster.1grass.gz: whatis parse for raster(1grass) failed
mandb: warning: /usr/share/man/man1/keywords.1grass.gz: whatis parse for keywords(1grass) failed
mandb: warning: /usr/share/man/man1/topic_mask.1grass.gz: whatis parse for topic_mask(1grass) failed
mandb: warning: /usr/share/man/man1/topic_series.1grass.gz: whatis parse for topic_series(1grass) failed
mandb: warning: /usr/share/man/man1/topic_terrain.1grass.gz: whatis parse for topic_terrain(1grass) failed
mandb: warning: /usr/share/man/man1/topic_dissolve.1grass.gz: whatis parse for topic_dissolve(1grass) failed
mandb: warning: /usr/share/man/man1/topic_metadata.1grass.gz: whatis parse for topic_metadata(1grass) failed
mandb: warning: /usr/share/man/man1/wxGUI.1grass.gz: whatis parse for wxGUI(1grass) failed
mandb: warning: /usr/share/man/man1/databaseintro.1grass.gz: whatis parse for databaseintro(1grass) failed
mandb: warning: /usr/share/man/man1/topic_vegetation_index.1grass.gz: whatis parse for topic_vegetation_index(1grass) failed
mandb: warning: /usr/share/man/man1/grass-dbf.1grass.gz: whatis parse for grass-dbf(1grass) failed
mandb: warning: /usr/share/man/man1/topic_cartography.1grass.gz: whatis parse for topic_cartography(1grass)

Processed: Re: grass-doc: whatis parse errors in manpages

2015-11-08 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 upstream
Bug #379913 [grass-doc] grass-doc: whatis parse errors in manpages
Added tag(s) upstream.
> found -1 grass/7.0.1-2
Bug #379913 [grass-doc] grass-doc: whatis parse errors in manpages
Marked as found in versions grass/7.0.1-2.

-- 
379913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: not yet fixed in upstream (Was: [Mayhem] Bug report on nco: ncap2 crashes with exit status 139)

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 716129 upstream
Bug #716129 [nco] [Mayhem] Bug report on nco: ncap2 crashes with exit status 139
Added tag(s) upstream.
> fixed 716129 nco/4.4.2-1
Bug #716129 [nco] [Mayhem] Bug report on nco: ncap2 crashes with exit status 139
Marked as fixed in versions nco/4.4.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
716129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#749859: netcdf: Please increase size of netcdf models for exodus

2015-11-08 Thread Sebastiaan Couwenberg 
notfound 749859 4.2.1+
found 749859 netcdf/1:4.3.3.1+ds-1~exp1
tags 749859 upstream
thanks

Hi Alastair,

On 30-05-14 11:36, Alastair McKinstry wrote:
> The netcdf library must be modified slightly in order to handle the
> exodus datamodel. The specific changes are:
> 
> 1. include/netcdf.h -- Modify the following defines:
> 
> #define NC_MAX_DIMS 65536/* max dimensions per file */
> #define NC_MAX_VARS 524288   /* max variables per file */
> #define NC_MAX_VAR_DIMS 8/* max per variable dimensions */
> 
> If these changes are not made, the exodus library will still function
> for "normal" size models, but it will fail for "large" models. The
> error message from exodus/netcdf should be somewhat clear when this
> happens...

As you know, we have NetCDF 4.4.0~rc2 in testing/unstable for some time
now. While that meets the 4.2.1 version requirements, but not the
NC_MAX_* values:

/**
Maximum for classic library.

In the classic netCDF model there are maximum values for the number of
dimensions in the file (\ref NC_MAX_DIMS), the number of global or per
variable attributes (\ref NC_MAX_ATTRS), the number of variables in
the file (\ref NC_MAX_VARS), and the length of a name (\ref
NC_MAX_NAME).

These maximums are enforced by the interface, to facilitate writing
applications and utilities.  However, nothing is statically allocated
to these sizes internally.

These maximums are not used for netCDF-4/HDF5 files unless they were
created with the ::NC_CLASSIC_MODEL flag.

As a rule, NC_MAX_VAR_DIMS <= NC_MAX_DIMS.
*/
/**@{*/
#define NC_MAX_DIMS 1024
#define NC_MAX_ATTRS8192
#define NC_MAX_VARS 8192
#define NC_MAX_NAME 256
#define NC_MAX_VAR_DIMS 1024 /**< max per variable dimensions */
/**@}*/


I'm not comfortable changing these values, because I cannot oversee the
impact.

How common are the "large" models? Is it not a very specialised use case?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: Bug#749859: netcdf: Please increase size of netcdf models for exodus

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> notfound 749859 4.2.1+
Bug #749859 [netcdf] netcdf: Please increase size of netcdf models for exodus
There is no source info for the package 'netcdf' at version '4.2.1+' with 
architecture ''
Unable to make a source version for version '4.2.1+'
No longer marked as found in versions 4.2.1+.
> found 749859 netcdf/1:4.3.3.1+ds-1~exp1
Bug #749859 [netcdf] netcdf: Please increase size of netcdf models for exodus
Marked as found in versions netcdf/1:4.3.3.1+ds-1~exp1.
> tags 749859 upstream
Bug #749859 [netcdf] netcdf: Please increase size of netcdf models for exodus
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
749859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#611338: marked as done (ncdump seems to support OpenDAP URI's only up to 55 characters long )

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 20:32:16 +0100
with message-id <563fa340.9080...@xs4all.nl>
and subject line Re: Bug#611338: ncdump seems to support OpenDAP URI's only up 
to 55 characters long
has caused the Debian Bug report #611338,
regarding ncdump seems to support OpenDAP URI's only up to 55 characters long 
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.)


-- 
611338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netcdf-bin
Version: 1:4.1.1-5

Apparently, ncdump doesn't support OpenDAP URI's of 56
characters or more in length.  Consider, e. g.:

$ ncdump -k 
http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd20110128/gfs_hd_00z 
ncdump: http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd20110128/gfs_hd_00z: 
NetCDF: I/O failure
$ 

I've checked the proxy logs, and no HTTP request is recorded
upon the command above.  The behavior is the same should the URI
be truncated to 56 characters:

$ ncdump -k http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd20110 
ncdump: http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd20110: NetCDF: I/O 
failure
$ 

On the other hand, the URI's of 55 characters and less are
handled differently, and the requests are being made:

$ ncdump -k http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd2011 
ncdump: http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd2011: NetCDF: DAP 
server error
$ ncdump -k http://test.opendap.org:8080/dods/dts/test.01 
64-bit offset
$ 

-- 
FSF associate member #7257


pgpf6HC4ycBl8.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 19-01-15 22:47, Ross Gammon wrote:
> I have tried to reproduce this in my old Debian Squeeze box
> (netcdf 1:4.1.1-5), and in Debian unstable (netcdf 1:4.1.3-7.2),
> and it seems to be working fine. It was not necessary for me to add
> the OCLOGFILE environment variable to achieve this. Of course the
> URL needs to updated to the latest 2014 data:
> 
> $ ncdump -k 
> http://nomads.ncep.noaa.gov:9090/dods/gfs_hd/gfs_hd20141216/gfs_hd_00z
>
> 
64-bit offset
> 
> Could you please confirm that you are still having this problem?

Closing this issue as unreproducible, probably fixed since squeeze.

Kind Regards,

Bas
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWP6M6AAoJEGdQ8QrojUrx/XgQAIsxqLVjteOLDV7oHu2BG/6C
rAFR1shaBWqHKl99l0enYwMRSm6EpcDxmVnVjXkKNQqVLCoGoaxLzeWUE3sd+Hpu
KuKogt9GbwmewX4bsP2l9lXph5ZmCMz8ihHJIUfIFbveefOyQYUx6Oqo7uCpgDM7
8o+chApZA3BXyl5BZq5FaF3D/ONtg0YJi/+rnDyL5shtqtIeFKJa6DD58dQSZpQW
7YMYP1y+XxxIVTZ19tOXN80tZJpISC7J5NVkMkhHfddqiUvaqYszUxffulGY2LgO
7eTdx2oFeGpIaim30NlS7Tlvyr9kxUwBq8zJWXsN/Nadu+TUQetr37XPTv5L0mTv
VU+bMQwpVf9KIC6N7Acbhay97YHRiY0oPIamFpHcvIKTdQFrULMeaQrCvZddeddc
lsX8j8/24DJ9v3G1mP9WFbp6w5rkD2OEjioXRW8bVcWZsRezUBtIDXxtk7jPC25V
WxXmXuhBLpDVSZPBkNyMem/5Vf3gP+uUaGyW+32b4C1Mkx/lWxn9lk5cke6y6cnO
AqBWPSgmiPeEKA8WKa5Ipc9CLkF2TNCW9TfCdCbFcdwg4CgsQk9dPKmIbqZjvEZt
gq4qxOrGtr+PedJCR0qx/Y7G83SDUehKbcZmWGNeY3uRbjelLkrVY0wb/v5EWv1g
8YXo9wZ4OHbpd21tlKIu
=un3d
-END PGP SIGNATURE 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

Bug#341643: grass-doc: manpage NAME sections often too long

2015-11-08 Thread Markus Neteler 
Thanks, upstream ticket created at

https://trac.osgeo.org/grass/ticket/2794

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#543162: [ncview] segfault when clicking on "Axes" button

2015-11-08 Thread Sebastiaan Couwenberg 
Control: found -1 ncview/2.1.6+ds-1

On 19-04-15 12:45, Sebastiaan Couwenberg wrote:
> Yesterday I finished updating the ncview packaging with the 2.1.5
> upstream release, but it unfortunately still suffers from this issue.
> 
> Upstream doesn't use a public bug tracker to forward this issue to, but
> I may be able to forward it by email to the upstream developer. I
> forwarded some patches developed while packaging version 2.1.5, so if
> that establishes a line of communication I'll also ask upstream to look
> into this issue.

Sadly the crash still occurs with ncview (2.1.6+ds-1), and upstream
still doesn't use a bugtracker.

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: tagging 543162

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 543162 + upstream
Bug #543162 [ncview] [ncview] segfault when clicking on "Axes" button
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
543162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#749511: netcdf: wrong quote characters

2015-11-08 Thread Sebastiaan Couwenberg 
Control: tags -1 upstream unreproducible moreinfo

Hi Michael,

We migrated away from NetCDF 4.1.3 to 4.4.0 in unstable, and I cannot
reproduce the issue with the current netcdf packages any more.

On Tue, 27 May 2014 15:58:24 +0100 Michael Tautschnig wrote:
> During a rebuild of all packages in a clean sid chroot (and 
> cowbuilder+pbuilder)
> the build failed with the following error. Please note that we use our 
> research
> compiler tool-chain (using tools from the cbmc package), which permits 
> extended
> reporting on type inconsistencies at link time.
> 
> [...]
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../fortran -I.. -I../libsrc 
> -DgFortran -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall -c curlfunctions.c  -fPIC -DPIC -o 
> .libs/liboc_la-curlfunctions.o
> curlfunctions.c: In function 'ocset_curl_flags':
> curlfunctions.c:30:66: warning: character constant too long for its type 
> [enabled by default]
>   cstat = curl_easy_setopt(curl, CURLOPT_ENCODING, 'deflate, gzip');
>   ^
> literals with 13 characters are not supported
> Makefile:388: recipe for target 'liboc_la-curlfunctions.lo' failed
> make[3]: *** [liboc_la-curlfunctions.lo] Error 1
> make[3]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-netcdf/netcdf-4.1.3/oc'
> Makefile:551: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> 
> Likely this should be double quotes here in order to set the accepted encoding
> to the desired value (the current code will set it to a value other than the
> desired one!) - and curl's documentation also suggests that the option has
> actually be renamed to CURLOPT_ACCEPT_ENCODING.

Double quotes are now used in oc2/occurlfunctions.c:

146 case CURLOPT_ENCODING:
147 #ifdef CURLOPT_ENCODING
148 if(state->curlflags.compress) {
149 CHECK(state, CURLOPT_ENCODING,"deflate, gzip");
150 }
151 #endif

It looks like this fixed the issue.

Can you confirm that this is now fixed, or can you still reproduce the
issue with netcdf (1:4.4.0~rc3-1)?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: netcdf: wrong quote characters

2015-11-08 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 upstream unreproducible moreinfo
Bug #749511 [netcdf] netcdf: wrong quote characters
Added tag(s) moreinfo, upstream, and unreproducible.

-- 
749511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: bug 341643 is forwarded to https://trac.osgeo.org/grass/ticket/2794

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 341643 https://trac.osgeo.org/grass/ticket/2794
Bug #341643 {Done: Sebastiaan Couwenberg } [grass-doc] 
grass-doc: manpage NAME sections often too long
Set Bug forwarded-to-address to 'https://trac.osgeo.org/grass/ticket/2794'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
341643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: grass: sqlite database update failure with Unicode characters in wxpython gui

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 595815 upstream
Bug #595815 [grass] grass: sqlite database update failure with Unicode 
characters in wxpython gui
Added tag(s) upstream.
> fixed 595815 grass/7.0.1-2
Bug #595815 [grass] grass: sqlite database update failure with Unicode 
characters in wxpython gui
Marked as fixed in versions grass/7.0.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: Bug#543162: [ncview] segfault when clicking on "Axes" button

2015-11-08 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 ncview/2.1.6+ds-1
Bug #543162 [ncview] [ncview] segfault when clicking on "Axes" button
Marked as found in versions ncview/2.1.6+ds-1.

-- 
543162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#595815: marked as done (grass: sqlite database update failure with Unicode characters in wxpython gui)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 19:03:34 +0100
with message-id <563f8e76.9030...@xs4all.nl>
and subject line Re: grass: sqlite database update failure with Unicode 
characters in wxpython gui
has caused the Debian Bug report #595815,
regarding grass: sqlite database update failure with Unicode characters in 
wxpython gui
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.)


-- 
595815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 6.4.0~rc6+42329-1+b1
Severity: normal

Hi!

I just noticed, that trying to update the attribute table data using non-ascii 
letters using the Query vector map (edit mode) in the
map display does not work; in fact, it hangs indefinitively until the 
db.execute running in the background is killed with 'kill -9'.

In the 'Command output' I get this:

--
Traceback (most recent call last):
  File "/usr/lib/grass64/etc/wxpython/gui_modules/dbm.py",
line 3152, in OnReset

self.FindWindowById(id).SetValue(str(value))
UnicodeEncodeError
:
'ascii' codec can't encode character u'\xe4' in position 6:
ordinal not in range(128)
--

All the best,

Harri K.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grass depends on:
ii  gnome-terminal [x-termi 2.30.2-1 The GNOME terminal emulator applic
ii  lesstif21:0.95.2-1   OSF/Motif 2.1 implementation relea
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-4 The Cairo 2D vector graphics libra
ii  libfftw3-3  3.2.2-1  library for computing Fast Fourier
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-1  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.4.4-8GCC support library
ii  libgdal1-1.6.0  1.6.3-4  Geospatial Data Abstraction Librar
ii  libgl1-mesa-glx [libgl1 7.7.1-4  A free implementation of the OpenG
ii  libglu1-mesa [libglu1]  7.7.1-4  The OpenGL utility library (GLU)
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libmysqlclient165.1.49-1 MySQL database client library
ii  libncurses5 5.7+20100313-2   shared libraries for terminal hand
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libpq5  8.4.4-2  PostgreSQL C client library
ii  libproj04.7.0-1  Cartographic projection library
ii  libpython2.62.6.6~rc1-1  Shared Python runtime library (ver
ii  libreadline66.1-3GNU readline and history libraries
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libsqlite3-03.7.2-1  SQLite 3 shared library
ii  libstdc++6  4.4.4-8  The GNU Standard C++ Library v3
ii  libtiff43.9.4-3  Tag Image File Format (TIFF) libra
ii  libwxbase2.8-0  2.8.10.1-3   wxBase library (runtime) - non-GUI
ii  libwxgtk2.8-0   2.8.10.1-3   wxWidgets Cross-platform C++ GUI t
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxext62:1.1.2-1X11 miscellaneous extension librar
ii  libxmu6 2:1.0.5-1X11 miscellaneous utility library
ii  libxrender1 1:0.9.6-1X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  rxvt-unicode [x-termina 9.07-2   RXVT-like terminal emulator with U
ii  tcl8.4  8.4.19-4 Tcl (the Tool Command Language) v8
ii  tk8.4   8.4.19-4 Tk toolkit for Tcl and X11, v8.4 -
ii  unixodbc2.2.14p2-1   ODBC tools libraries
ii  xterm [x-terminal-emula 261-1X terminal emulator
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages grass recommends:
ii  ghostscript 8.71~dfsg2-4 The GPL Ghostscript PostScript/PDF
ii  python  2.6.5-13 interactive high-level object-orie
ii

Processed: Re: Bug#768887: FTBFS: Could not copy file .../osmosis-plugins.conf

2015-11-08 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 768887 osmosis/0.44.1-2
Bug #768887 [src:osmosis] FTBFS: Could not copy file .../osmosis-plugins.conf
Marked as fixed in versions osmosis/0.44.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
768887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#749511: netcdf: wrong quote characters

2015-11-08 Thread Michael Tautschnig 
Hi,

On Sun, Nov 08, 2015 at 23:03:19 +0100, Sebastiaan Couwenberg wrote:
> We migrated away from NetCDF 4.1.3 to 4.4.0 in unstable, and I cannot
> reproduce the issue with the current netcdf packages any more.
> 
[...]
> It looks like this fixed the issue.
> 
> Can you confirm that this is now fixed, or can you still reproduce the
> issue with netcdf (1:4.4.0~rc3-1)?
> 

Yes, I do confirm that this problem has been addressed. There is, however,
another inconsistency that now crops up: ocrc_process is declared with
inconsistent return types. The attached patch fixes this problem.

Best,
Michael

Index: sources-netcdf/1:4.4.0~rc3-1/oc2/ocrc.c
===
--- sources-netcdf/1:4.4.0~rc3-1/oc2/ocrc.c
+++ sources-netcdf/1:4.4.0~rc3-1/oc2/ocrc.c
@@ -407,12 +407,12 @@
free(path);
 return stat;
 }
 
-int
+OCerror
 ocrc_process(OCstate* state)
 {
-int stat = 0;
+OCerror stat = OC_NOERR;
 char* value = NULL;
 OCURI* uri = state->uri;
 char* url_userpwd = NULL;
 char* url_hostport = NULL;


pgp8HiUkwXqqW.pgp
Description: PGP signature
___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#379913: [GRASS-dev] grass-doc: whatis parse errors in manpages

2015-11-08 Thread Vaclav Petras 
On Sun, Nov 8, 2015 at 11:51 AM, Markus Neteler  wrote:

> But before doing so, we need to understand how to deal with the 102
> "topic_xxx.html" pages like e.g.
>
> https://grass.osgeo.org/grass70/manuals/topic_sampling.html
>
> In all those "NAME" does not really make sense. Likewise the 7
> xxxintro.html pages like e.g.
> https://grass.osgeo.org/grass70/wrongmanuals/imageryintro.html
> 
>

I agree that we should think it through.

r.li page mentioned above (I like to call this type module group) has
GRASS-custom meta comment (not what is in r37865):


DESCRIPTION
...

This is turned into a heading when the complete page is generated.
Unfortunately, the heading is  and the other headings are  as well.
The results is thus semantically wrong and graphically ugly HTML (which is
worsen by using all uppercase in headings). I think this applies to wxGUI
pages too. *intro pages are better since the other headings are level 3:


Image processing in general

I think the NAME section doesn't make sense for topics, intros, some GUI
and some other pages perhaps including the module group pages like r.li. If
man et al. needs NAME and some special things than I think we should solve
it during compilation specifically for man pages.
___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#749511: netcdf: wrong quote characters

2015-11-08 Thread Michael Tautschnig 
On Mon, Nov 09, 2015 at  0:11:23 +, Michael Tautschnig wrote:
[...]
> Yes, I do confirm that this problem has been addressed. There is, however,
> another inconsistency that now crops up: ocrc_process is declared with
> inconsistent return types. The attached patch fixes this problem.
> 

There are actually two more cases of the same kind -- patches attached.

Best,
Michael

Index: sources-netcdf/1:4.4.0~rc3-1/oc2/oc.h
===
--- sources-netcdf/1:4.4.0~rc3-1/oc2/oc.h
+++ sources-netcdf/1:4.4.0~rc3-1/oc2/oc.h
@@ -536,9 +536,9 @@
 /* Get the HTTP return code from the last call;
note that this may or may not be the same as returned
by oc_svcerrordata.
  */
-extern int oc_httpcode(OClink);
+extern OCerror oc_httpcode(OClink);
 
 /*
 (Re-)initialize the oc library as if nothing had been called.
 This is primarily for debugging of rc files.
Index: sources-netcdf/1:4.4.0~rc3-1/oc2/ochttp.c
===
--- sources-netcdf/1:4.4.0~rc3-1/oc2/ochttp.c
+++ sources-netcdf/1:4.4.0~rc3-1/oc2/ochttp.c
@@ -87,13 +87,13 @@
oclog(OCLOGERR, "curl error: %s", curl_easy_strerror(cstat));
return OCTHROW(OC_ECURL);
 }
 
-int
+OCerror
 ocfetchurl(CURL* curl, const char* url, OCbytes* buf, long* filetime,
struct OCcredentials* creds)
 {
-   int stat = OC_NOERR;
+   OCerror stat = OC_NOERR;
CURLcode cstat = CURLE_OK;
size_t len;
 long httpcode = 0;
 


pgpUtoofnl7B7.pgp
Description: PGP signature
___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#287760: marked as done (Small fonts in i.points)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 14:12:12 +0100
with message-id <563f4a2c.2060...@xs4all.nl>
and subject line Re: Small fonts in i.points
has caused the Debian Bug report #287760,
regarding Small fonts in i.points
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.)


-- 
287760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass-doc
Version: 5.7.0-6
Severity: normal
File: /usr/share/doc/grass-doc/html/i.points.html

It says
  QUIT To end the i.points program place the mouse cross hairs on the
  word QUIT; the marked points (including coordinates) will be saved.
however at least if we haven't entered any points, we don't see this
word!
The only way to stop it is killall -1 i.points

Oh, looking at the man page I found it.
But why must it be so tiny!?

--- End Message ---
--- Begin Message ---
On Wed, 17 Dec 2008 06:19:34 +1300 Hamish  wrote:
> - i.points is headed out for pasture (removed in grass 7);
> - I seem to be the only one actively maintaining i.points;
> - I'm only fixing serious bugs in it now, no new development.
> 
> severity set to wishlist; this ticket can be closed as "wontfix".

GRASS 7 is in testing/unstable for some time now, closing this issue.--- 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

Bug#341643: closed by Sebastiaan Couwenberg <sebas...@xs4all.nl> (Re: grass-doc: manpage NAME sections often too long)

2015-11-08 Thread 積丹尼 Dan Jacobson 
OK.

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#783245: marked as done (wx gui does not work properly under vnc)

2015-11-08 Thread Debian Bug Tracking System 
Your message dated Sun, 8 Nov 2015 16:50:28 +0100
with message-id <563f6f44.6090...@xs4all.nl>
and subject line Re: Bug#783245: wx gui does not work properly under vnc
has caused the Debian Bug report #783245,
regarding wx gui does not work properly under vnc
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.)


-- 
783245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 7.0.0-1~exp1
Severity: important

Using wxwidget GUI under VNC the add raster/vector tool does not show a
working pop-up window to choose a file, which renders the GUI almost unusable.
Just for information the same issue appears in the native macosx binary under
the latest OSX version. It is working under X11 natively, so it seems some
strange oddity in interaction between the GUI and the WX engine under some
specific environments.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages grass depends on:
ii  grass-core  6.4.4-1
ii  grass-gui   6.4.4-1

Versions of packages grass recommends:
ii  grass-doc  6.4.4-1

Versions of packages grass suggests:
ii  grass-dev  6.4.4-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On 25-04-15 14:55, Francesco P. Lovergine wrote:
> On Fri, Apr 24, 2015 at 06:20:00PM +0200, Sebastiaan Couwenberg wrote:
>> I can reproduce the issue on a jessie VM with grass 6.4.4-1, but I can't
>> reproduce the issue with grass 7.0.0-1~exp1 from experimental on that
>> same VM.
>>
>> It looks like the issue was fixed in GRASS 7, maybe the fix is included
>> in GRASS 6.4.5RC1 already.
>>
>> We may need to consider GRASS 6.4.5 for unstable until GRASS 7 is ready
>> to move out of experimental.
> 
> Indeed I better remembered my trials. I built 7.0.0-1~exp1 under jessie
> from scratch (did not have a try with 6.4.4) with the same problem,
> so there are probably some issues due to the environment not grass per se. 
> I will have a try under sid using the experimental binary for 
> completeness on monday.

I'm closing this issue since GRASS 7 is in unstable for some now.

Kind Regards,

Bas--- 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

Bug#676190: grass-gui: gcpmanager fails to list source mapsets if non-ascii characters in grass data dir path

2015-11-08 Thread Torsti Schulz 

Hi Bas,

I still get the same error as in the original bug report for GRASS 
6.4.1. when using the Georectifier.
Also changing mapset access does not work for me. So I can't confirm 
that the issue has been fixed in GRASS 7.0.1.



Thanks for the good work in the GIS team!

Best,
Torsti

On 08.11.2015 15:00, Sebastiaan Couwenberg wrote:

Control: tags -1 upstream unreproducible moreinfo

Hi Torsti,

We've have GRASS 7 in testing/unstable for some time now, and while the
upstream issue is still open, it seems it has been fixed in GRASS 7.

I can successfully open a GRASS GIS database directory by selecting the
path /home/user/tmp/Työpöytä/grassdata/, selecting the 'spearfish60'
GRASS location, selecting either of the GRASS Mapsets and starting the
GRASS session.

Can you confirm that the issue is fixed in the GRASS 7 packages in
testing/unstable?

Kind Regards,

Bas



___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#749859: netcdf: Please increase size of netcdf models for exodus

2015-11-08 Thread Alastair McKinstry 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Bas

I don't know how many 'large' models there are.

As the documentation states, the netcdf library does not statically
define anything based on these arbitrary limits, so I believe there is
no impact on netcdf itself. Certainly exodus works fine when netcdf is
changed to meet these limits.
If there is a negative impact, it may be due to certain codes that use
classic netcdf statically allocating in order to meet these potential
limits, but I've never heard or seen such issues.

regards
Alastair



On 08/11/2015 7:52 p.m., Sebastiaan Couwenberg wrote:
> notfound 749859 4.2.1+
> found 749859 netcdf/1:4.3.3.1+ds-1~exp1
> tags 749859 upstream
> thanks
>
> Hi Alastair,
>
> On 30-05-14 11:36, Alastair McKinstry wrote:
>> The netcdf library must be modified slightly in order to handle the
>> exodus datamodel. The specific changes are:
>>
>> 1. include/netcdf.h -- Modify the following defines:
>>
>> #define NC_MAX_DIMS 65536/* max dimensions per file */
>> #define NC_MAX_VARS 524288   /* max variables per file */
>> #define NC_MAX_VAR_DIMS 8/* max per variable dimensions */
>>
>> If these changes are not made, the exodus library will still function
>> for "normal" size models, but it will fail for "large" models. The
>> error message from exodus/netcdf should be somewhat clear when this
>> happens...
>
> As you know, we have NetCDF 4.4.0~rc2 in testing/unstable for some time
> now. While that meets the 4.2.1 version requirements, but not the
> NC_MAX_* values:
>
> /**
> Maximum for classic library.
>
> In the classic netCDF model there are maximum values for the number of
> dimensions in the file (\ref NC_MAX_DIMS), the number of global or per
> variable attributes (\ref NC_MAX_ATTRS), the number of variables in
> the file (\ref NC_MAX_VARS), and the length of a name (\ref
> NC_MAX_NAME).
>
> These maximums are enforced by the interface, to facilitate writing
> applications and utilities.  However, nothing is statically allocated
> to these sizes internally.
>
> These maximums are not used for netCDF-4/HDF5 files unless they were
> created with the ::NC_CLASSIC_MODEL flag.
>
> As a rule, NC_MAX_VAR_DIMS <= NC_MAX_DIMS.
> */
> /**@{*/
> #define NC_MAX_DIMS 1024
> #define NC_MAX_ATTRS8192
> #define NC_MAX_VARS 8192
> #define NC_MAX_NAME 256
> #define NC_MAX_VAR_DIMS 1024 /**< max per variable dimensions */
> /**@}*/
>
>
> I'm not comfortable changing these values, because I cannot oversee the
> impact.
>
> How common are the "large" models? Is it not a very specialised use case?
>
> Kind Regards,
>
> Bas
>

- -- 
Alastair McKinstry, , ,
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWQEJBAAoJEMvmu05dmtOlF6MP/39dDi4Pb2QoB8aMHct5eTt/
0xwMLSx5k23G+WwtLn2ZBrmQHhpVhJda+cOjGDKhd+eetpWm3gWYjo8Z3Qfi2Axi
MuP1knVRzrulw0pnSyRDeZTjF0XOpdDeCIaglnqjw5dHTWsmskloWy4d87BHccnS
njZxJ6fd/rXiIg42w5eRbi1mNxoW56M+5dHtSIBEG4R43HzqQzuVIhYWoxybw86I
9OqD/C0JN95itmwy1GuaWMvb/0it9cA5ubGX2kfK9mgFTbubztiWSpraoyk+a4C8
tqDjCB3aPZF+hGmwAKjsgBsN3RL6jkwEP1NZjAzsnWc3f/si0TXpRAhDbHw2Ykqx
c+ZHWTzET8y0eC3FEec9ckZYU38T/RpNmoas62pkUMk7YyMlumipAXTar0+R2vfF
qtTkjAS2QRpjlwRC7NE9CCloH/PCTDPPNH2NMAPdFsMFKHtfXfzaRx3bLGbVL+qZ
2ZRzDChgMxS7Yj2ZSCes28QEjP1GvFd/J7ZlgJ9oukKLeBYEWQOSChWszLVgNqvJ
nY+yThn5K5rD5dB+KCOYQ8M7puJp3PY4goUavTz4eAWil5zC1WD2yPuiutXqIlqQ
2VPs/LUP5tJNTcKMWpubI1CghmlcHq67yCllihs9na51ewjWaRIwZqLEoYgvni7m
1/RmcJDxeXQRthGTiNOl
=7hzg
-END PGP SIGNATURE-

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel