Octave 2.1.62 available for ftp

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Octave 2.1.62 available for ftp

John W. Eaton-6
Octave 2.1.62 is now available for ftp from ftp.octave.org in the
directory /pub/octave/bleeding-edge:

  -rw-r--r--  1 1005 5507279 Nov 11 23:46 octave-2.1.62.tar.gz
  -rw-r--r--  1 1005 4337085 Nov 11 23:46 octave-2.1.62.tar.bz2
  -rw-r--r--  1 1005   16138 Nov 11 23:52 octave-2.1.61-2.1.62.patch.gz
  -rw-r--r--  1 1005   14101 Nov 11 23:52 octave-2.1.61-2.1.62.patch.bz2

  4d2f5ee3717da39a493e305a89ee567f  octave-2.1.62.tar.gz
  fa96da1d5cba1022349cb77be14e2899  octave-2.1.62.tar.bz2
  4abee37642382ba91b7c0c1d73744481  octave-2.1.61-2.1.62.patch.gz
  ac6a05740cec391f63422c4dc8f01c6f  octave-2.1.61-2.1.62.patch.bz2

Thanks again to David Bateman for all his hard work to get this
snapshot ready.

This version includes many new features, including integer data types,
inline functions, function handles, concatenation of structs, cell
arrays and user-defined types, and better compatibility with the
leading brand.

Since 2.1.61, the following features have been implemented:

  * Comparison operations for 64-bit integers without conversion to
    double (so comparisons on the full range of 64-bit integers should
    work correctly).

  * Concatenation of mixed-integer types and concatenation of
    integers and doubles (expressions like [int16(1), int32(2)]).

As always, if your favorite bug is still not fixed, please report it.

Unless any major problems are found in the next few days, 2.1.62 will
become the next "recommended" version of Octave.

jwe


Reply | Threaded
Open this post in threaded view
|

2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Dirk Eddelbuettel
Having updated the Octave packages to 2.1.62 yesterday, I just tried buildin
octave-forge (based on the 2004.09.09 release). This failed in, as far as I
can tell, two spots:

[...]
Compiling op-gm-s.o
/usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.62 -I/usr/include/octave-2.1.62/octave -mieee-fp -O2 -DHAVE_OCTAVE_21 -DGALOIS_DISP_PRIVATES -DHAVE_ND_ARRAYS -DTYPEID_HAS_CLASS -DCLASS_HAS_LOAD_SAVE -DHAVE_SWAP_BYTES op-gm-s.cc -o op-gm-s.o
op-gm-s.cc: In function `octave_value oct_catop_gm_s(octave_value&, const
   octave_value&, const Array<int>&)':
op-gm-s.cc:76: error: `concat' undeclared (first use this function)
op-gm-s.cc:76: error: (Each undeclared identifier is reported only once for
   each function it appears in.)
make[3]: *** [op-gm-s.o] Error 1
Compiling op-m-gm.o
/usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.62 -I/usr/include/octave-2.1.62/octave -mieee-fp -O2 -DHAVE_OCTAVE_21 -DGALOIS_DISP_PRIVATES -DHAVE_ND_ARRAYS -DTYPEID_HAS_CLASS -DCLASS_HAS_LOAD_SAVE -DHAVE_SWAP_BYTES op-m-gm.cc -o op-m-gm.o
Compiling op-s-gm.o
/usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.62 -I/usr/include/octave-2.1.62/octave -mieee-fp -O2 -DHAVE_OCTAVE_21 -DGALOIS_DISP_PRIVATES -DHAVE_ND_ARRAYS -DTYPEID_HAS_CLASS -DCLASS_HAS_LOAD_SAVE -DHAVE_SWAP_BYTES op-s-gm.cc -o op-s-gm.o
op-s-gm.cc: In function `octave_value oct_catop_s_gm(octave_value&, const
   octave_value&, const Array<int>&)':
op-s-gm.cc:89: error: `concat' undeclared (first use this function)
op-s-gm.cc:89: error: (Each undeclared identifier is reported only once for
   each function it appears in.)
make[3]: *** [op-s-gm.o] Error 1

[...]

mkoctfile -DHAVE_OCTAVE_21 -v -v  -DHAVE_ND_ARRAYS -DTYPEID_HAS_CLASS -c findsymbols.cc
/usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.62 -I/usr/include/octave-2.1.62/octave -mieee-fp -O2 -DHAVE_OCTAVE_21 -DHAVE_ND_ARRAYS -DTYPEID_HAS_CLASS findsymbols.cc -o findsymbols.o
findsymbols.cc: In function `void append_symbols(octave_value_list&, const
   GiNaC::ex&)':
findsymbols.cc:51: error: ambiguous overload for 'operator==' in 'sym ==
   sym_new'
/usr/include/octave-2.1.62/octave/oct-inttypes.h:582: error: candidates are:
   bool operator==(const octave_int<octave_uint32_t>&, const
   octave_int<octave_int8_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:582: error:                
   bool operator==(const octave_int<octave_int8_t>&, const
   octave_int<octave_uint32_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:583: error:                
   bool operator==(const octave_int<octave_uint32_t>&, const
   octave_int<octave_int16_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:583: error:                
   bool operator==(const octave_int<octave_int16_t>&, const
   octave_int<octave_uint32_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:584: error:                
   bool operator==(const octave_int<octave_uint32_t>&, const
   octave_int<octave_int32_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:584: error:                
   bool operator==(const octave_int<octave_int32_t>&, const
   octave_int<octave_uint32_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:586: error:                
   bool operator==(const octave_int<octave_uint64_t>&, const
   octave_int<octave_int8_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:586: error:                
   bool operator==(const octave_int<octave_int8_t>&, const
   octave_int<octave_uint64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:587: error:                
   bool operator==(const octave_int<octave_uint64_t>&, const
   octave_int<octave_int16_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:587: error:                
   bool operator==(const octave_int<octave_int16_t>&, const
   octave_int<octave_uint64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:588: error:                
   bool operator==(const octave_int<octave_uint64_t>&, const
   octave_int<octave_int32_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:588: error:                
   bool operator==(const octave_int<octave_int32_t>&, const
   octave_int<octave_uint64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:589: error:                
   bool operator==(const octave_int<octave_uint64_t>&, const
   octave_int<octave_int64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:589: error:                
   bool operator==(const octave_int<octave_int64_t>&, const
   octave_int<octave_uint64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:621: error:                
   bool operator==(const octave_int<octave_uint32_t>&, const
   octave_int<octave_int64_t>&)
/usr/include/octave-2.1.62/octave/oct-inttypes.h:621: error:                
   bool operator==(const octave_int<octave_int64_t>&, const
   octave_int<octave_uint32_t>&)
/usr/include/ginac/operators.h:77: error:                 const
   GiNaC::relational GiNaC::operator==(const GiNaC::ex&, const GiNaC::ex&)
make[3]: *** [findsymbols.o] Error 1


Shall I disable these components, and release the remainder, or wait for
fixes regarding octave-forge?

Thanks!

Dirk
     
--
If your hair is standing up, then you are in extreme danger.
      -- http://www.usafa.af.mil/dfp/cockpit-phys/fp1ex3.htm


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

David Bateman-3
Dirk Eddelbuettel <edd <at> debian.org> writes:

>
> Having updated the Octave packages to 2.1.62 yesterday, I just tried buildin
> octave-forge (based on the 2004.09.09 release). This failed in, as far as I
> can tell, two spots:

Fixes should have been in octave-forge CVS since last Wednesday...

Cheers
David


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Rafael Laboissiere
* David Bateman <[hidden email]> [2004-11-14 21:01]:

> Dirk Eddelbuettel <edd <at> debian.org> writes:
>
> >
> > Having updated the Octave packages to 2.1.62 yesterday, I just tried buildin
> > octave-forge (based on the 2004.09.09 release). This failed in, as far as I
> > can tell, two spots:
>
> Fixes should have been in octave-forge CVS since last Wednesday...

I succeed to build octave-forge_2004.09.09-4 againts octave2.1_2.1.62-1
after applying the minimal patch attached below, which was extracted from
CVS.  Dirk, please apply the patch and upload a new package ASAP. Otherwise,
octave-forge may become broken in sarge due to the forthcoming freeze.  I am
willing to NMU the package if you wish.

--
Rafael

comm+symbolic.patch (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Dirk Eddelbuettel
On Tue, Nov 16, 2004 at 10:40:47AM +0100, Rafael Laboissiere wrote:

> * David Bateman <[hidden email]> [2004-11-14 21:01]:
>
> > Dirk Eddelbuettel <edd <at> debian.org> writes:
> >
> > >
> > > Having updated the Octave packages to 2.1.62 yesterday, I just tried buildin
> > > octave-forge (based on the 2004.09.09 release). This failed in, as far as I
> > > can tell, two spots:
> >
> > Fixes should have been in octave-forge CVS since last Wednesday...
>
> I succeed to build octave-forge_2004.09.09-4 againts octave2.1_2.1.62-1
> after applying the minimal patch attached below, which was extracted from
> CVS.  Dirk, please apply the patch and upload a new package ASAP. Otherwise,
> octave-forge may become broken in sarge due to the forthcoming freeze.  I am
> willing to NMU the package if you wish.

Go ahead, and add yourself in debian/control in a new Uploaders: field.
Welcome as a co-maintainer :)

Dirk

> --
> Rafael

> --- octave-forge-2004.09.09.orig/main/comm/galois-ops.h
> +++ octave-forge-2004.09.09/main/comm/galois-ops.h
> @@ -106,6 +106,31 @@
>  #define DEFCATOP_G_FN(name, t1, t2, f) \
>    CATOPDECL (name, a1, a2)     \
>    { \
> +    CAST_BINOP_ARGS (octave_ ## t1&, const octave_ ## t2&); \
> +    return new octave_galois (f (v1.t1 ## _value (), v2.t2 ## _value (), ra_idx)); \
> +  }
> +
> +#define DEFCATOP_G_METHOD(name, t1, t2, f) \
> +  CATOPDECL (name, a1, a2)     \
> +  { \
> +    CAST_BINOP_ARGS (octave_ ## t1&, const octave_ ## t2&); \
> +    return new octave_galois (v1.t1 ## _value (). f (v2.t2 ## _value (), ra_idx)); \
> +  }
> +
> +#define INSTALL_G_CATOP(t1, t2, f) INSTALL_CATOP(t1, t2, f)
> +
> +#elif defined(HAVE_OLD_OCTAVE_CONCAT)
> +
> +#define DEFCATOP_G_FN(name, t1, t2, f) \
> +  CATOPDECL (name, a1, a2)     \
> +  { \
> +    CAST_BINOP_ARGS (const octave_ ## t1&, const octave_ ## t2&); \
> +    return new octave_galois (f (v1.t1 ## _value (), v2.t2 ## _value (), ra_idx)); \
> +  }
> +
> +#define DEFCATOP_G_METHOD(name, t1, t2, f) \
> +  CATOPDECL (name, a1, a2)     \
> +  { \
>      CAST_BINOP_ARGS (const octave_ ## t1&, const octave_ ## t2&); \
>      return new octave_galois (f (v1.t1 ## _value (), v2.t2 ## _value (), ra_idx)); \
>    }
> @@ -113,6 +138,7 @@
>  #define INSTALL_G_CATOP(t1, t2, f) INSTALL_CATOP(t1, t2, f)
>  #else
>  #define DEFCATOP_G_FN(name, t1, t2, f)
> +#define DEFCATOP_G_METHOD(name, t1, t2, f)
>  #define INSTALL_G_CATOP(t1, t2, f)
>  #endif
>  
> --- octave-forge-2004.09.09.orig/main/comm/galois.cc
> +++ octave-forge-2004.09.09/main/comm/galois.cc
> @@ -225,7 +225,7 @@
>    return retval;
>  }
>  
> -#ifdef HAVE_OCTAVE_CONCAT
> +#ifdef HAVE_OLD_OCTAVE_CONCAT
>  galois concat (const galois& ra, const galois& rb, const Array<int>& ra_idx)
>  {
>    galois retval (ra);
> @@ -264,6 +264,50 @@
>    retval.insert (tmp, ra_idx(0), ra_idx(1));
>    return retval;
>  }
> +#endif
> +
> +#ifdef HAVE_OCTAVE_CONCAT
> +galois
> +galois::concat (const galois& rb, const Array<int>& ra_idx)
> +{
> +  if (rb.numel() > 0)
> +    insert (rb, ra_idx(0), ra_idx(1));
> +  return *this;
> +}
> +
> +galois
> +galois::concat (const Matrix& rb, const Array<int>& ra_idx)
> +{
> +  if (numel() == 1)
> +    return *this;
> +
> +  galois tmp (0, 0, 0, m(), primpoly());
> +  int _n = (1<<m()) - 1;
> +  int r = rb.rows();
> +  int c = rb.columns();
> +  tmp.resize (r, c);
> +
> +  // Check the validity of the data in the matrix
> +  for (int i=0; i<r; i++) {
> +    for (int j=0; j<c; j++) {
> +      if ((rb(i,j) < 0) || (rb(i,j) > _n)) {
> + gripe_range_galois(m());
> + return *this;
> +      }
> +      if ((rb(i,j) - (double)((int)rb(i,j))) != 0.) {
> + gripe_integer_galois();
> + return *this;
> +      }
> +      tmp(i,j) = (int)rb(i,j);
> +    }
> +  }
> +
> +  insert (tmp, ra_idx(0), ra_idx(1));
> +  return *this;
> +}
> +#endif
> +
> +#if defined (HAVE_OLD_OCTAVE_CONCAT) || defined (HAVE_OCTAVE_CONCAT)
>  
>  galois concat (const Matrix& ra, const galois& rb,  const Array<int>& ra_idx)
>  {
> --- octave-forge-2004.09.09.orig/main/comm/galois.h
> +++ octave-forge-2004.09.09/main/comm/galois.h
> @@ -92,11 +92,19 @@
>    boolMatrix all (int dim = -1) const;
>    boolMatrix any (int dim = -1) const;
>  
> -#ifdef HAVE_OCTAVE_CONCAT
> +#ifdef HAVE_OLD_OCTAVE_CONCAT
>    friend galois concat (const galois& ra, const galois& rb,
>   const Array<int>& ra_idx);
>    friend galois concat (const galois& ra, const Matrix& rb,
>   const Array<int>& ra_idx);
> +#endif
> +
> +#ifdef HAVE_OCTAVE_CONCAT
> +  galois concat (const galois& rb, const Array<int>& ra_idx);
> +  galois concat (const Matrix& rb, const Array<int>& ra_idx);
> +#endif
> +
> +#if defined(HAVE_OCTAVE_CONCAT) || defined(HAVE_OLD_OCTAVE_CONCAT)
>    friend galois concat (const Matrix& ra, const galois& rb,
>   const Array<int>& ra_idx);
>  
> --- octave-forge-2004.09.09.orig/main/comm/op-gm-gm.cc
> +++ octave-forge-2004.09.09/main/comm/op-gm-gm.cc
> @@ -80,7 +80,7 @@
>  DEFBINOP_FN (el_and, galois, galois, mx_el_and)
>  DEFBINOP_FN (el_or, galois, galois, mx_el_or)
>  
> -DEFCATOP_G_FN (gm_gm, galois, galois, concat)
> +DEFCATOP_G_METHOD (gm_gm, galois, galois, concat)
>  
>  DEFASSIGNOP_FN (assign, galois, galois, assign)
>  
> --- octave-forge-2004.09.09.orig/main/comm/op-gm-m.cc
> +++ octave-forge-2004.09.09/main/comm/op-gm-m.cc
> @@ -68,7 +68,7 @@
>  DEFBINOP_FN (el_and, galois, matrix, mx_el_and)
>  DEFBINOP_FN (el_or, galois, matrix, mx_el_or)
>  
> -DEFCATOP_G_FN (gm_m, galois, matrix, concat)
> +DEFCATOP_G_METHOD (gm_m, galois, matrix, concat)
>  
>  // Need to create temporary Galois array so that matrix values are checked
>  DEFASSIGNOP (assign, galois, matrix)
> --- octave-forge-2004.09.09.orig/main/comm/op-gm-s.cc
> +++ octave-forge-2004.09.09/main/comm/op-gm-s.cc
> @@ -68,13 +68,20 @@
>  DEFBINOP_FN_B_S2 (el_and, galois, scalar, mx_el_and)
>  DEFBINOP_FN_B_S2 (el_or, galois, scalar, mx_el_or)
>  
> -#ifdef DEFCATOP
> +#ifdef HAVE_OLD_OCTAVE_CONCAT
>  DEFCATOP (gm_s, galois, scalar)
>  {
>    CAST_BINOP_ARGS (const octave_galois&, const octave_scalar&);
>    return new octave_galois (concat (v1.galois_value (), v2.matrix_value (),
>      ra_idx));
>  }
> +#elif defined(HAVE_OCTAVE_CONCAT)
> +DEFCATOP (gm_s, galois, scalar)
> +{
> +  CAST_BINOP_ARGS (octave_galois&, const octave_scalar&);
> +  return new octave_galois (v1.galois_value (). concat (v2.matrix_value (),
> +    ra_idx));
> +}
>  #endif
>  
>  DEFASSIGNOP(assign, galois, scalar)
> --- octave-forge-2004.09.09.orig/main/comm/op-s-gm.cc
> +++ octave-forge-2004.09.09/main/comm/op-s-gm.cc
> @@ -81,13 +81,20 @@
>  DEFBINOP_FN_B_S1 (el_and, scalar, galois, mx_el_and)
>  DEFBINOP_FN_B_S1 (el_or, scalar, galois, mx_el_or)
>  
> -#ifdef DEFCATOP
> +#ifdef HAVE_OLD_OCTAVE_CONCAT
>  DEFCATOP (s_gm, scalar, galois)
>  {
>    CAST_BINOP_ARGS (const octave_scalar&, const octave_galois&);
>    return new octave_galois (concat (v1.matrix_value (), v2.galois_value (),
>      ra_idx));
>  }
> +#elif defined (HAVE_OCTAVE_CONCAT)
> +DEFCATOP (s_gm, scalar, galois)
> +{
> +  CAST_BINOP_ARGS (octave_scalar&, const octave_galois&);
> +  return new octave_galois (concat (v1.matrix_value (), v2.galois_value (),
> +    ra_idx));
> +}
>  #endif
>  
>  void
> --- octave-forge-2004.09.09.orig/main/comm/ov-galois.cc
> +++ octave-forge-2004.09.09/main/comm/ov-galois.cc
> @@ -56,7 +56,7 @@
>  #endif
>  
>  
> -#ifdef HAVE_OCTAVE_CONCAT
> +#if defined (HAVE_OCTAVE_CONCAT) || defined (HAVE_OLD_OCTAVE_CONCAT)
>  octave_value octave_galois::resize (const dim_vector& dv) const
>  {
>    if (dv.length() > 2)
> --- octave-forge-2004.09.09.orig/main/comm/ov-galois.h
> +++ octave-forge-2004.09.09/main/comm/ov-galois.h
> @@ -34,7 +34,7 @@
>  #include <iostream>
>  #include <string>
>  
> -#ifdef HAVE_OCTAVE_CONCAT
> +#if defined(HAVE_OCTAVE_CONCAT) || defined(HAVE_OLD_OCTAVE_CONCAT)
>  #include <octave/dim-vector.h>
>  #endif
>  
> @@ -111,7 +111,7 @@
>    }
>  #endif
>  
> -#ifdef HAVE_OCTAVE_CONCAT
> +#if defined(HAVE_OCTAVE_CONCAT) || defined(HAVE_OLD_OCTAVE_CONCAT)
>    octave_value resize (const dim_vector& dv) const;
>  
>    size_t byte_size (void) const { return gval.byte_size (); }
> --- octave-forge-2004.09.09.orig/main/symbolic/findsymbols.cc
> +++ octave-forge-2004.09.09/main/symbolic/findsymbols.cc
> @@ -48,7 +48,7 @@
>   /* have to convert back to compare: */
>   get_symbol(symlist(j),ex_sym);
>   sym = GiNaC::ex_to<GiNaC::symbol>(ex_sym);
> - if(sym==sym_new) {
> + if(GiNaC::operator == (sym,sym_new)) {
>   unique = false;
>   break;
>   } else {
> --- octave-forge-2004.09.09.orig/main/symbolic/ov-ex.cc
> +++ octave-forge-2004.09.09/main/symbolic/ov-ex.cc
> @@ -115,7 +115,7 @@
>   GiNaC::symbol sym = GiNaC::ex_to<GiNaC::symbol>(x);
>   std::vector<symbol_list_item>::iterator iter_symlist;
>   for(iter_symlist=symbol_list.begin();iter_symlist<symbol_list.end();iter_symlist++) {
> - if(sym == iter_symlist->sym) {
> + if(GiNaC::operator == (sym, iter_symlist->sym)) {
>   iter_symlist->refcount --;
>   if(iter_symlist->refcount==0)
>   symbol_list.erase(iter_symlist);


--
If your hair is standing up, then you are in extreme danger.
      -- http://www.usafa.af.mil/dfp/cockpit-phys/fp1ex3.htm


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

David Bateman-3
In reply to this post by Dirk Eddelbuettel
Rafael,

There are a few other things in the CVS relative to 2004.09.09, that might
be of interest but aren't build issues. For example the op_uplus stuff is
needed for unary plus to work on the user types... But perhaps this isn't
importnat to finalize a release.

Cheers
David


--
David Bateman                                [hidden email]
Motorola CRM                                 +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Rafael Laboissiere
* Dirk Eddelbuettel <[hidden email]> [2004-11-16 11:57]:

> Go ahead, and add yourself in debian/control in a new Uploaders: field.
> Welcome as a co-maintainer :)
 
* David Bateman <[hidden email]> [2004-11-16 20:25]:

> There are a few other things in the CVS relative to 2004.09.09, that might
> be of interest but aren't build issues. For example the op_uplus stuff is
> needed for unary plus to work on the user types... But perhaps this isn't
> importnat to finalize a release.

Actually, Paul Kienzle has just released a new version of octave-forge
(2004-11-16).  Dirk: what should I do?  Should I package this version
instead of the patched 2004-09-09?

--
Rafael


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

David Bateman-3
According to Rafael Laboissiere <[hidden email]> (on 11/17/04):
> Actually, Paul Kienzle has just released a new version of octave-forge
> (2004-11-16).  Dirk: what should I do?  Should I package this version
> instead of the patched 2004-09-09?

Then I'd vote to put 2.1.63 out straight away with the API version number
updated and call it the testing release. My reasoning is that basically all
that has happened since 2.1.59 has been bug fixes for the patches between
2.1.57 and 2.1.59. So most of the bugs that will come out with the use of
an unstable release have already come out.. Also an immediate release avoids
all possibility of other changes being needed in octave-forge to support a
2.1.63 testing release..

This way 2.1.63 and octave-forge 2004.11.16 can get into debian sarge..

Cheers
David

--
David Bateman                                [hidden email]
Motorola CRM                                 +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Dirk Eddelbuettel
In reply to this post by Rafael Laboissiere
On Wed, Nov 17, 2004 at 09:41:41AM +0100, Rafael Laboissiere wrote:

> * Dirk Eddelbuettel <[hidden email]> [2004-11-16 11:57]:
>
> > Go ahead, and add yourself in debian/control in a new Uploaders: field.
> > Welcome as a co-maintainer :)
>  
> * David Bateman <[hidden email]> [2004-11-16 20:25]:
>
> > There are a few other things in the CVS relative to 2004.09.09, that might
> > be of interest but aren't build issues. For example the op_uplus stuff is
> > needed for unary plus to work on the user types... But perhaps this isn't
> > importnat to finalize a release.
>
> Actually, Paul Kienzle has just released a new version of octave-forge
> (2004-11-16).  Dirk: what should I do?  Should I package this version
> instead of the patched 2004-09-09?

Sure!

Dirk

--
If your hair is standing up, then you are in extreme danger.
      -- http://www.usafa.af.mil/dfp/cockpit-phys/fp1ex3.htm


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

John W. Eaton-6
In reply to this post by David Bateman-3
On 17-Nov-2004, David Bateman <[hidden email]> wrote:

| Then I'd vote to put 2.1.63 out straight away with the API version number
| updated and call it the testing release.

I agree, so will start doing that now unless there are any
objections.

jwe


Reply | Threaded
Open this post in threaded view
|

Re: 2.1.62 breaks octave-forge (Re: Octave 2.1.62 available for ftp)

Dirk Eddelbuettel
In reply to this post by Rafael Laboissiere
On Wed, Nov 17, 2004 at 09:41:41AM +0100, Rafael Laboissiere wrote:

> * Dirk Eddelbuettel <[hidden email]> [2004-11-16 11:57]:
>
> > Go ahead, and add yourself in debian/control in a new Uploaders: field.
> > Welcome as a co-maintainer :)
>  
> * David Bateman <[hidden email]> [2004-11-16 20:25]:
>
> > There are a few other things in the CVS relative to 2004.09.09, that might
> > be of interest but aren't build issues. For example the op_uplus stuff is
> > needed for unary plus to work on the user types... But perhaps this isn't
> > importnat to finalize a release.
>
> Actually, Paul Kienzle has just released a new version of octave-forge
> (2004-11-16).  Dirk: what should I do?  Should I package this version
> instead of the patched 2004-09-09?

I did this earlier, it is currently uploading:

octave-forge (2004.11.16-1) unstable; urgency=low

  * New upstream release
  * Rebuilt with octave 2.1.63 (Closes: #281777)
  * debian/control: Build-Depends and Depends updated accordingly
  * debian/control: Added Rafael as Uploaders:
       
 -- Dirk Eddelbuettel <[hidden email]>  Wed, 17 Nov 2004 19:51:39 -0600

I'll do the same with octave-sp aka semidef-oct.

Dirk

--
If your hair is standing up, then you are in extreme danger.
      -- http://www.usafa.af.mil/dfp/cockpit-phys/fp1ex3.htm