Philip Nienhuis writes:
> I see by following links from another recent post by you that you are about to
> prepare an Octave io-1.0.17 pkg for Debian.
We have just packaged io 1.0.17 for Debian (see [1]).
This is the first Debian release for which spreadsheet support works out
of the box. For y
Just an additional info, which can be totally irrelevant to the bug,
or maybe not. When nrbbasisfun is called in my Octave 3.6.1 session,
I get the following warning message when quitting Octave:
warning: octave_chunk_buffer::clear: -2 active allocations remain!
The number (-2 in the output
Hello, Happy Nowruz
I have the symbolic package, but I don't why it doesn't work. there is a
function "sym" in the link that you send that may work like "syms" in
matlab. anyway I'm working on all codes to fit with Octave.
On Mon, Mar 19, 2012 at 5:30 PM, Lukas Reichlin wrote:
> On 19.03.2012, at
On 20 March 2012 02:26, Luca Favatella wrote:
> I wrote a Unix shell script in order to ease the preparation of
> package and function reference, automating the steps described at [1].
> You can find it at [2] (svn r9974).
Hi Luca
there's another script on the repository that does it but it's an
no one support communication package
On 03/19/12 21:31, Nikiforov Alex wrote:
> Hi guys, I dont know a proper list for this message but in gentoo we
> have some problem with communications package
>
> At first
> https://bugs.gentoo.org/show_bug.cgi?id=381109
>
> And second
> https://bugs.gento
Sébastien Villemot wrote:
> Philip Nienhuis writes:
>
>> I see by following links from another recent post by you that you are about
>> to
>> prepare an Octave io-1.0.17 pkg for Debian.
>
> We have just packaged io 1.0.17 for Debian (see [1]).
>
> This is the first Debian release for which spread
On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
> no one support communication package
There is nothing to support:
1) A new version of the communications package is available since
2011-10-xx.
2) The build failure was against Octave 3.4.0 - try again with 3.6.1.
Thom
On 03/20/12 22:00, Thomas Weber wrote:
On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
no one support communication package
There is nothing to support:
1) A new version of the communications package is available since
2011-10-xx.
Ok. I'll try to solve this issue with Gent
On Tue, Mar 20, 2012 at 12:41:43AM -0400, Jordi Gutiérrez Hermoso wrote:
> Please consider hg, as it is what Octave core uses, and if we're
> moving OF to a DVCS, it would be best to consolidate the two projects.
What's the advantage? Where precisely is octave-forge better off with a
DVCS? And not
On 03/20/12 22:00, Thomas Weber wrote:
On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
no one support communication package
There is nothing to support:
1) A new version of the communications package is available since
2011-10-xx.
Ok. I'll try to solve this issue with Gent
On 3/20/2012 8:00 PM, Thomas Weber wrote:
> On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
>> no one support communication package
>
> There is nothing to support:
> 1) A new version of the communications package is available since
> 2011-10-xx.
> 2) The build failure was again
2012/3/20 Thomas Weber :
> On Tue, Mar 20, 2012 at 12:41:43AM -0400, Jordi Gutiérrez Hermoso wrote:
>> Please consider hg, as it is what Octave core uses, and if we're
>> moving OF to a DVCS, it would be best to consolidate the two projects.
>
> What's the advantage? Where precisely is octave-forge
On 20 Mar 2012, at 20:17, Thomas Weber wrote:
> The problem with testing OF packages has one simple solution - enable
> pkg.m to do it.
I am working on this.
> Or ditch it entirely and switch to a
> ./configure | cmake
> make
> make check
> workflow.
This was the approach t
On 20 Mar 2012, at 21:39, Jordi Gutiérrez Hermoso wrote:
> I want a unified build method that builds Octave and then builds and
> tests all OF packages against the same Octave build that just
> happened.
That was done when we had the "monolithic" forge releases.
Having to build all octave-forge
2012/3/20 c. :
>
> On 20 Mar 2012, at 21:39, Jordi Gutiérrez Hermoso wrote:
>
>> I want a unified build method that builds Octave and then builds and
>> tests all OF packages against the same Octave build that just
>> happened.
>
> That was done when we had the "monolithic" forge releases.
> Having
* Jordi Gutiérrez Hermoso [2012-03-20 17:29]:
> On 11 March 2012 20:21, Rafael Laboissiere wrote:
> > With odepkg 0.8.0 and Octave 3.6.1, I am getting a segmentation fault in
> > my Debian system with the following code (taken from the test suite in
> > odepkg_octsolver_mebdfdae.cc):
>
> There
On 19 March 2012 21:14, Philip Nienhuis wrote:
> On Windows I have no problems either. Have you tried it on Linux? I can send
> you a .tar.gz package to try. Perhaps it is my Mandriva setup, who knows.
I only have Linux. I have tried on Debian and Ubuntu and I could
reproduce the problem.
> Othe
On 03/20/12 23:38, marco atzeri wrote:
> On 3/20/2012 8:00 PM, Thomas Weber wrote:
>> On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
>>> no one support communication package
>>
>> There is nothing to support:
>> 1) A new version of the communications package is available since
On 20 Mar 2012, at 23:11, Jordi Gutiérrez Hermoso wrote:
> There's no reason why all of OF has to build. Recursive make(1) calls
> can fail and be logged. It would be nice to have *some* method of at
> least trying to build and test all of Octave Forge regularly. This is
> independent of the rele
On 3/21/2012 8:18 AM, Nikiforov Alex wrote:
> On 03/20/12 23:38, marco atzeri wrote:
>> On 3/20/2012 8:00 PM, Thomas Weber wrote:
>>> On Tue, Mar 20, 2012 at 10:51:26PM +0300, Nikiforov Alex wrote:
no one support communication package
>>>
>>> There is nothing to support:
>>> 1) A new versi
20 matches
Mail list logo
