Bug#417659: [Pkg-octave-devel] Bug#417659: octave2.9-forge: API version mismatches the octave core

[Hongzheng Wang]

Hi,

I also notice that the octave-forge provides a pkg mechanism now
according to their faq and docs.  And, of course, the pkg subsystem is
not a compatible Debian style.  But I think the new pkg method is not
compulsory.  I mean, octave-forge may be able to work in a pre-build
manner.  Thus, it may be possible to provide a matched octave-forge
package so that it can be used with the current octave core in sid
(after addpath the oct files and m files of octave-forge).  Well, I'm
not sure about it; just a guess :-)

Regards,
Hongzheng

On 4/4/07, Rafael Laboissiere <rafael at debian.org> wrote:
> package octave2.9-forge
> tags 417659 - pending
> thanks
>
> * Rafael Laboissiere <rafael at debian.org> [2007-04-04 09:04]:
>
> > * Hongzheng Wang <wanghz at gmail.com> [2007-04-04 10:55]:
> > >
> > > It seems that the API version of the oct files in this package
> > > mismatches the version of octave core in octave2.9 version 2.9.10-3,
> > > the up-to-date octave2.9 package in unstable.  Could you please upload
> > > a matched one?  Thank you.
> >
> > Thanks, we are aware of this.  I am working on it.
>
> Bad news: the current octave2.9-forge package does not work well with
> octave2.9 and this will take some time to fix.  It is too bad that I
> uploaded 2.9.10 to unstable before checking this.  The current Octave-Forge
> packages are intended to be installed in the user's system through the new
> pkg system.
>
> What should we do now?  Deprecate octave2.9-forge or fix it by backporting
> the code obtained from CVS ?  A third solution would be to start working
> immediately on the new pkg2deb package.
>
> --
> Rafael
>


-- 
Hongzheng Wang