libgdal-grass not updated for latest grass

[kalxas]

Recent move to libgdal1h has caused ossim breaking the build process (malloc error causes chroot freeze). We need someone to step up and create a new ossim package based on the new gdal. Until then, ossim is removed from nightly builds.

[hamish]

was ossim built using the standard 12.04 gdal packages or volatile ubuntugis ones?

if it happens that ossim was built against the official ubuntu packages, then the bug is not with ossim.

?

I still find it odd that a user-space crash would take out the chroot.

Hamish

ps- note Massimo may be traveling.

[hamish]

Angelos, could you cut and paste the error from the build log here?

the old log doesn't seem to be up anymore at ​http://aiolos.survey.ntua.gr/gisvm/dev/

thanks, Hamish

[kalxas]

Selecting previously unselected package libjpeg62.
(Reading database ... 215589 files and directories currently installed.)
Unpacking libjpeg62 (from .../libjpeg62_6b1-2ubuntu1_i386.deb) ...
Setting up libjpeg62 (6b1-2ubuntu1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
ERROR 4: `/usr/local/share/data/raster/BlueMarble_small.tiff' does not
exist in the file system,
and is not recognised as a supported dataset name.

GDALOpen failed - 4
`/usr/local/share/data/raster/BlueMarble_small.tiff' does not exist in the
file system,
and is not recognised as a supported dataset name.

MPI running with 1 processors...
WARNING: Unable to open image file
/usr/share/ossim/images/reference/bluemarble.tif
Elapsed time: 0
Image does not exist /usr/share/ossim/images/reference/bluemarble.tif
Warning 1: GRASS warning: GISBASE enviroment variable was not set, using:
/usr/lib/grass64
Input file size is 1899, 1398
Input file size is 1899, 1398
0Warning 1: Unable to export color table to GeoTIFF file.  Color tables
can only be written to 1 band or 2 bands Byte or UInt16 GeoTIFF files.
Warning 1: GRASS warning: GISBASE enviroment variable was not set, using:
/usr/lib/grass64
...10...20...30...40...50...60...70...80...90...100 - done.
*** glibc detected *** /usr/local/ossim/bin/ossim-orthoigen: malloc():
memory corruption: 0x08b0b290 ***

[hamish]

problematic ossim-orthoigen command commented out in r10394. (not installed blue marble image too, but note we had a symlinked clone of that in the shared data dir somewhere)

this was nothing to do with GDAL AFAICT (?at least on the surface?).

I think it's ok to re-add ossim to the main build list now.

todo (me): work on remaking the north carolina geotiffs with optimized data-types.

Hamish

[kalxas]

After last commit, ossim is included again, without freezing the build server.

[kalxas]

Hamish, I am leaving this open to remind us of the todo item.

Thanks, Angelos

[hamish]

there is /usr/share/osgearth/world.tif (symlinked to ~/data/raster/world.tif) to play with too.

Some flavor of bluemarble.tif is nice to have on disc, that one is 12mb compressed as bzip2 to world.tif's 2.4mb compressed as bzip2.

open question: is the world.tif one detailed enough for our needs? or is the +10mb worth it for more detail? (if so, we should swap it in and remove the osgearth world.tif dupe)

Hamish

[kalxas]

It would be nice to have a more detailed version and some WMS server pointing at it (preferably Mapserver that is always up)

[hamish]

Replying to kalxas:

It would be nice to have a more detailed version and some WMS server pointing at it (preferably Mapserver that is always up)

for grass's r.in.wms module tutorial we are using ​http://mapserver.flightgear.org/ (TelaScience? / OSGeo / FlightGear? Landcover Database Mapserver), but it is a bit underpowered.

NASA JPL's OnEarth? one is only tile)-WMS now (only accepts requests for certain bboxes + zooms), but this one looks interesting, and has BlueMarble?

• ​http://neowms.sci.gsfc.nasa.gov/Search.html
• ​http://neowms.sci.gsfc.nasa.gov/wms/wms

Hamish

[kalxas]

Hamish, thank you for the links.

What I meant was to create a BlueMarble? WMS on the disk so that it is available offline too. And this would be nice with the more detailed version.

[hamish]

Replying to kalxas:

What I meant was to create a BlueMarble? WMS on the disk so that it is available offline too. And this would be nice with the more detailed version.

ah, sorry. yes, it's a nice idea.

Hamish

ps- (offtopic)- do you know who was responsible for making the nice ZOO trac theme?

[kalxas]

re ZOO: no, I have to ask :)

[lucadelu]

Replying to hamish:

ps- (offtopic)- do you know who was responsible for making the nice ZOO trac theme?

Nickolas Bozon, he told me that should be enough override trac.css

cheers Luca

[kalxas]

ossim is (again) not installed (7.0beta2) due to grass dependency

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgdal1-1.9.0-grass : Depends: grass643-3 but it is not installable
E: Unable to correct problems, you have held broken packages.
ERROR: Package install failed! Aborting.

[hamish]

actually it was the gdal dependency:

apt-get install libgdal1-1.9.0 libgdal1-1.9.0-grass

neither work anymore, the grass plugin there had the extra feature that it depended on a non-existent grass package name.

I've updated those to the now-in-ubuntugis version 1.10 to make dpkg happy (r10578), but I suspect the ossim.tar.gz binary will need to be rebuilt against the current gdal package before the program will work.

anyway it will give us an idea of installed size.

Hamish

[kalxas]

it seems that there is a change in the build message:

Processing triggers for menu ...
Reading package lists...
Building dependency tree...
Reading state information...
libgdal1h is already the newest version.
libgdal1h set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgdal1-1.10.0-grass : Depends: grass643-3 but it is not installable
E: Unable to correct problems, you have held broken packages.
ERROR: Package install failed! Aborting.

[hamish]

Right, there is a bogus dependency in the .deb on "grass643-3", a package name which does not exist. I think it should be set in the debian/control file as "grass-core" instead?

Hamish

[kalxas]

ossim is included in beta3. gdal-grass problem with package still valid.

[jlarouche]

libgdal-grass have been built against the latest grass version.

[kalxas]

tested in build 10764 and works fine.