Custom query (1088 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (112 - 114 of 1088)

Ticket Resolution Summary Owner Reporter
#959 fixed geomajas installs old version on OSGeo-Live kalxas camerons
Description

As of OSGeoLive 6.0beta4, the geomajas install script [1] installs version 1.8.0 rather than the latest stable version of 1.11.

[1] https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_geomajas.sh

We believe that this is also linked to geomajas not working in 6.0beta4 when the Java Advanced Imaging (JAI) library was copied into the main java library.

The following email thread [2] should provide insights: On 07/23/2012 08:41 AM, Jody Garnett wrote:

We actually have three things to track here:

  • JAI
  • ImageIO
  • ImageIO-Ext (this will make use of GDAL binaries if they are available on the LD_LIBRARY_PATH, or installed into jre/bin)

I was concerned about GeoMajas using an older copy of GeoTools; and ending up requiring a different version of ImageIO-Ext (and thus GDAL) then the other projects.

From a recent announcement (http://www.geomajas.org/node/629) it looks like GeoTools 2.7.5 is expected. This release of GeoTools (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10270&version=18236) works with ImageIO 1.1.x stream and should be compatible with the same ImageIO-Ext as GeoServer and uDig (which are starting to make use of GeoTools 8).

Hi Jody,

Geomajas on the DVD is still in version 1.8.0. The link you provided was referring to Geomajas 1.11.0

[2] http://lists.osgeo.org/pipermail/live-demo/2012-July/005618.html

#974 wontfix remastersys iso installation fails kalxas darkblueb
Description

install completes but results in flawed system (see screenshots, taken soon after install and reboot)

#988 fixed chroot build method: autologin failure due to rasdaman kalxas kalxas
Description

This issue happens when build_chroot script is used with live session username set to "user". The created iso refuses to autologin. This has been tracked with debug script so far and limited down to 3 packages (liblas, rasdaman and mb-system). When initrd modifications are not used this issue is not present.

Proposed solutions:

  1. Create the iso first without initrd customization and then use the created image file to run a second customization.
  2. Keep building with debug chroot scripts until we track down the package causing this.

Any other ideas I am missing?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.