On 7 January 2006 at 16:08, Paul Kienzle wrote:
| With a fresh compile of octave-2.1.72 (no patches) and
| octave-forge from CVS, my debian system doesn't panic.
|
| When I compile and run against the Debian octave 2.1.72-8
| it panics on every oct-file in octave-forge. The particular
| problem
With a fresh compile of octave-2.1.72 (no patches) and
octave-forge from CVS, my debian system doesn't panic.
When I compile and run against the Debian octave 2.1.72-8
it panics on every oct-file in octave-forge. The particular
problem at startup is that dispatch.oct is called by a
number of the
Rafael Laboissiere @ 2005-12-31 (Saturday), 00:15 (+0100)
> Also, since there is no problem with the octave2.1 and octave-forge
> currently in sid, I the severity level must be lowered to normal and the
> bug must be tagged "etch", and this message should do just that.
>
> As soon as the newest ve
package octave-forge
severity 345241 normal
tags 345241 etch
thanks
* Dirk Eddelbuettel <[EMAIL PROTECTED]> [2005-12-30 14:23]:
> reassign 345241 octave-forge
> thanks
>
> [...]
>
> It needs to be reassigned to octave-forge, and this message should do
> just that.
Also, since there is no problem
reassign 345241 octave-forge
thanks
On Fri, Dec 30, 2005 at 09:06:35PM +0100, Martin Samuelsson wrote:
> Dirk Eddelbuettel @ 2005-12-30 (Friday), 07:22 (-0600)
> > | The compilation has finished, but it seems like the build process did
> > | not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1])
>
Dirk Eddelbuettel @ 2005-12-30 (Friday), 07:22 (-0600)
> | The compilation has finished, but it seems like the build process did
> | not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1])
> |
> [zap]
> |
> | Unless someone tells me how to easily produce a debugable debian
> | package, I'm not spe
This seems to be a problem in connection with the octave-forge package:
After uninstalling the current testing version octave-forgre=2005.06.13-2
octave-2.1 started correctly on my system.
Therefore I've installed the unstable version octave-forge=2005.06.13-4 .
And It worked for me without the a
On 30 December 2005 at 12:54, Martin Samuelsson wrote:
| Martin Samuelsson @ 2005-12-30 (Friday), 09:23 (+0100)
| > I just started rebuilding octave again with DEB_BUILD_OPTIONS set to
| > "nostrip noopt". Hopefully that will give some clues.
|
| The compilation has finished, but it seems like th
Martin Samuelsson @ 2005-12-30 (Friday), 09:23 (+0100)
> I just started rebuilding octave again with DEB_BUILD_OPTIONS set to
> "nostrip noopt". Hopefully that will give some clues.
The compilation has finished, but it seems like the build process did
not honour DEB_BUILD_OPTIONS. (Debian Policy 1
Martin Samuelsson @ 2005-12-29 (Thursday), 22:35 (+0100)
> After upgrading octave today, it no longer starts at all. Reverting back
> to octave2.1_2.1.72-5_i386.deb makes it work again.
I tried rebuilding 2.1.72-5 locally to see if something in the packaging
breaks the package, or if it is the upg
Package: octave2.1
Version: 2.1.72-6
Severity: grave
Justification: renders package unusable
After upgrading octave today, it no longer starts at all. Reverting back
to octave2.1_2.1.72-5_i386.deb makes it work again.
This happens on at least two different machines. I have not done any
further b
11 matches
Mail list logo
