From octave-sources-request at bevo dot che dot wisc dot edu Wed Jun 18 08:17:26 2003 Subject: Re: polyfit.m patch From: Dirk Eddelbuettel To: Paul Kienzle Cc: "Pascal A. Dupuis" , octave-sources@bevo.che.wisc.edu Date: Wed, 18 Jun 2003 06:51:39 -0500 On Wed, Jun 18, 2003 at 07:40:33AM -0400, Paul Kienzle wrote: > Pascal A. Dupuis wrote: > > >I know about the octave-forge solutions, but actually, on my debian, > >the available octave-forge is not very up-to-date, while octave2.1 is. > > > > > This surprises me. Dirk Eddelbuettel has been stellar with > keeping his packages up to date --- always within days of a > new release. I wish all of Debian developers were so > dedicated. Thanks for the praise, Paul. Unfortunately, both statements can be true in the sense that octave-forge in testing lags behind while it is current in unstable. Packages only migrate from unstable to testing if they build on each platform they previously built. Now, octave-forge is so vast that it depends on a ton of other libraries, and the ginac maintainer has dropped the ball for m68k and mipsel so that libginac-dev is not available on these two systems. For that reason, octave-forge_2003.06.02-1 is only in unstable and not in testing. Now, those "who know" simply take it from unstable and use it on testing. To that effort, any of the 'apt-get howtos' can be wholeheartedly recommended. Incidentally, now that octave2.1 is finally back in testing with its newest version 2.1.49, I have also rebuild octave-forge last night. In this last built, I have dropped the requirement for ginac on m68k and mipsel. With a bit of luck, octave-forge may be in testing before long. Dirk -- Don't drink and derive. Alcohol and analysis don't mix.