On Sun, May 01, 2005 at 06:54:43PM +0200, Rafael Laboissiere wrote: > [Cc: to debian-release]
> * Andreas Jochens <[EMAIL PROTECTED]> [2005-05-01 15:16]: > > Package: octave-gpc > > Version: 0.1.4-1 > > Severity: serious > > Tags: sarge > > > > When building 'octave-gpc' on i386/testing, > > I get the following error: > > > > /usr/bin/mkoctfile -v -s -c gpc_create.cc > > /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.69 > > -I/usr/include/octave-2.1.69/octave -O2 gpc_create.cc -o gpc_create.o > > gpc_create.cc: In function `octave_value_list Fgpc_create(const > > octave_value_list&, int)': > > gpc_create.cc:81: error: no match for 'operator[]' in '*m["vertices"]' > > gpc_create.cc:84: error: no match for 'operator[]' in '*m["indices"]' > > gpc_create.cc:86: error: no match for 'operator[]' in '*m["hole"]' > > make[1]: *** [gpc_create.o] Error 1 > > make[1]: Leaving directory `/octave-gpc-0.1.4' > > make: *** [build-stamp] Error 2 > > The newer version 0.1.5-4 in sid builds fine. > Well, it is not octave-gpc's fault if its newest version is not in sarge > yet. According to http://bjorn.haxx.se/debian/testing.pl?package=octave-gpc, > we have: > # trying to update octave-gpc from 0.1.4-1 to 0.1.5-4 (candidate is 60 > days old) > # octave-gpc is waiting for gpcl > * gpcl is not yet built on alpha: 2.31-5 vs 2.32-1 (missing 2 binaries: > libgpcl-dev, libgpcl0) > [...] > gpcl is in non-free and octave-gpc is in contrib. How could this problem > be fixed? By getting gpcl updated on all architectures, requesting manual builds from the porter lists. I'm starting a build for alpha here. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
