On Thu, May 14, 2009 at 06:12:58PM +1200, Hamish wrote:
> Package: gdal-bin
> Followup-For: Bug #528557
> note that in the resolution to bug #495353 (thanks for digging that out)
> the closing message states that this is fixed in the 1.6.0 package in
> experiemental, not the 1.5.x packages currently in Sid.
> You might try installing those and see how it goes. (and the more testing
> it gets the sooner it moves into Sid)
> FWIW, I can confirm the segfault in Etch using gdal 1.5.2-3~bpo40+1
> from backports.org and the test data attached to bug #495353. Follows
> is a gdb backtrace of the standard stripped binaries.
> If needed I can provide a trace against unstripped gdal/trunk
> self-built binaries but I think that's not needed or useful
> as Frankie's already on top of the situation.

Due to the current status of testing I think I could move the new style 
hdf4 into sid and wait for testing promotion. I was waiting to have a few 
in testing (-> bpo) before moving on, but at this stage it seems
we will not have the whole toolchain in testing any time soon.

My own schedule was having both HDF4/5 updated in experimental along with gdal 
(which fixes a lot of issues) then move all into testing. But this is currently
an optimistic idea, we have simply too many migrations in sid...

So in the immediate time, I'm going to promote hdf4 in sid, then fix gdal 1.5
series and complete the current plan of support for hdf5. That's the tentative
plan, but I still need to re-check current testing global status and blockers.

Francesco P. Lovergine

Pkg-grass-devel mailing list

Reply via email to