Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1700 closed defect (fixed)

ossim packages missing for Xenial

Reported by: kalxas Owned by: live-demo@…
Priority: blocker Milestone: OSGeoLive10.0
Component: OSGeoLive Keywords: ossim-qt, ossim-planet
Cc: live-demo@…


Current status:

ossim-core has landed to our ppa. It gets installed by OTB as dependency.

ossim-plugins have been uploaded to DebianGIS, I will soon rebuild for Xenial.

What about the applications? Those are currently missing.

Change history (6)

comment:1 by kalxas, 8 years ago

Priority: criticalblocker

comment:2 by Bas Couwenberg, 8 years ago

  • ossim-gui

Needs license & copyright changes upstream to document the copyright holders and include the license file.

Initial packaging is available in the Debian GIS git repository:

Needs a lot more work, ossim-planet amongst them.

  • ossim-planet{,qt}, libwms, etc

Also need a lot of work to get properly packaged, I'm working my way through those too.

Updating the FPM created packages is your best bet to get these built for OSGeo-Live in the short term.

comment:3 by Bas Couwenberg, 8 years ago

Initial packaging for the other ossim components is available in the Debian GIS git repository now too:

  • ossim-wms (libwms)

  • ossim-planet

  • ossim-planet-qt

  • ossim-video (ossimPredator)

Fails to build with current FFmpeg in Debian unstable, but may still work with the xenial version.

GPSTk is still TODO.

comment:4 by kalxas, 8 years ago

Thanks Bas,

The packages are built in my staging ppa:

comment:5 by kalxas, 8 years ago

Resolution: fixed
Status: newclosed

comment:6 by Bas Couwenberg, 8 years ago

ossim-planet & ossim-planet-qt require some files from the ossim_package_support subdirectory in the upstream tarballs, these were provided in old ossim-share package and now have their own source package too:

Like the other ossim packages, they are far from done. In their current form their are not yet suitable for inclusion in Debian & Ubuntu, but for OSGeo-Live it should suffice.

Note: See TracTickets for help on using tickets.