Re: [Pkg-octave-devel] Packaging octave-forge 2006-03-17
* Thomas Weber <thomas.weber.mail@gmail.com> [2006-03-22 09:52]:
> Am Dienstag, den 21.03.2006, 11:48 +0100 schrieb Rafael Laboissiere:
> > There is a new version (2006-03.17) of octave-forge available. Could
> > someone try to build the Debian package for it and commit the changes to
> > SVN?
>
> If nobody steps forward, I will give it a try over the weekend.
It is yours.
> > Now that the netcdf transition is over and 2006-01-28-2 finally
> > entered testing, it is a good time for a new upload.
>
> Ehm, you are aware that octave-forge is part of the current hdf5
> transition? Which means we can prepare the update, but the actual upload
> shouldn't happen before somewhen next week.
Right.
> > #295395: octave-forge: Replacing a submatrix of a sparse matrix
>
> This is probably WONTFIX. The sparse code has been integrated into
> Octave 2.9, so I don't expect an upstream fix for octave-forge. And
> David has clearly stated that it was too much work for octave-forge.
>
> Unless you object, I will tag the bugs accordingly.
Go ahead.
> > The following one is not going to be closed any soon, but I hope that
> > Colin will resume the dual 2.1/2.9 build in the near future:
> >
> > #352150: octave-forge: depends on octave2.1, could it also depend on 2.9?
>
> So should I try the octave-forge build for 2.1 or 2.9?
Get coordinated with Colin Ingram, please. There is even a branch for
the dual 2.1/2.9 build in the SVN repository. While this project is not
yet finished, we should build octave-forge only for octave2.1.
--
Rafael
Reply to: