Hi Andreas,

For Osmosis I'm trying to package the new released version 0.43.1 which doesn't build the same way as 0.40. They use gradle now. I can get it to compile but when I try it, it throws ClassNotFound exceptions, same thing happen when I build it myself without using debuild.

The ticket in lilbgdal-ecw-src is here: http://trac.osgeo.org/ubuntugis/ticket/34.

For Marble, contacting the maintainers might be a good idea since it seems that compiling without KDE removes a lot from Marble, I'll have to see with OSGeoLive too if it still works for them.

The blockage with Geotools is that it requires Java Artifacts that are not available in a .deb. The most important one is JAI which can't be packaged from what I understand because of its license. Someone told me that it may be possible to disable JAI in GeoTools so I'll have to look into it.

On 13-07-27 04:13 PM, Andreas Tille wrote:
Hi Jerome,

On Fri, Jul 26, 2013 at 02:53:48PM -0400, Jerome Villeneuve Larouche wrote:
I also looked a Osmosis, another
java app, I can make a .deb out of it, but I get some java exception
even when built manually so I'm still looking into it.
Are you aware of

$ apt-cache policy osmosis
osmosis:
   Installed: (none)
   Candidate: 0.40.1+ds1-7
   Version table:
      0.40.1+ds1-7 0
         501 file:/home/ftp/pub/debian/ testing/main amd64 Packages
         501 http://http.debian.net/debian/ testing/main amd64 Packages
          50 http://http.debian.net/debian/ unstable/main amd64 Packages

I admit thia is not the latest upstream version but the packaging work
should be done in principle.  Did you checked out

$ apt-cache showsrc osmosis | grep -e ^Vcs
Vcs-Browser: http://git.debian.org/?p=pkg-osm/osmosis.git
Vcs-Git: git://git.debian.org/pkg-osm/osmosis.git

or did you contacted

$ LANG=C apt-cache showsrc osmosis | grep -e Maintainer -e Uploader
Maintainer: Debian OpenStreetMap Team <[email protected]>
Uploaders: Giovanni Mascellani <[email protected]> , David Paleino 
<[email protected]>


Today I also
started looking into Marble to create a package using only QT
instead of the big KDE libs.
I have not checked the Debian package whether it is using KDE libs but I
guess you are in contact with the maintainers.

I also fixed a small bug in
libgdal-ecw-src package in Lucid, Precise and Quantal.
I do not know this package but I'd recommend maintaining it in Debian GIS
team would be reasonable to let it migrate smoothly to any Ubuntu version
you need.  I repeat my offer to Sponsering of Blends[1] which should
smoothen your path to get packages uploaded to the Debian mirror if you
really want to.

What do you plan to do next week?
     I'll try to finish the Marble package and then look a bit more
into Osmosis
Please add communication with Debian GIS on this list.  Both packages are
inside Debian and it makes perfectly sense to do the work only once.

and some other small packages, like imposm.
$ apt-cache policy imposm
imposm:
   Installed: (none)
   Candidate: 2.4.0+dfsg-0.1
   Version table:
      2.5.0-1 0
           5 http://http.debian.net/debian/ experimental/main amd64 Packages
      2.4.0+dfsg-0.1 0
         501 file:/home/ftp/pub/debian/ testing/main amd64 Packages
         501 http://http.debian.net/debian/ testing/main amd64 Packages
          50 http://http.debian.net/debian/ unstable/main amd64 Packages

Moving experimental to unstable should be cheap - its probably just a
consequence of the Wheezy release cycle.

There's
also a bug in libgdal-ecw-src and the gdal-python binding that I'll
have to look into.
Any bug number to check this bug out?

What have you blocked on?
     Like I said before, there is a lot of problem with packaging
Geotools and the Osmosis java exception.
Please try to get rid of blockers by cooperation with Debian GIS.

Kind regards and good luck for your GSoC work

      Andreas.

[1] https://wiki.debian.org/DebianPureBlends/SoB


_______________________________________________
UbuntuGIS mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/ubuntu
http://trac.osgeo.org/ubuntugis/wiki

Reply via email to