On 28 Apr 2010, at 05:36, Søren Hauberg wrote:
> Hi
>
> It seems like the web pages for the latest version of the io package
> has
> been uploaded, but that the actual package has not.
>
> There was some discussion about two weeks ago regarding this release,
> but I am not sure how things ended
Hi
It seems like the web pages for the latest version of the io package has
been uploaded, but that the actual package has not.
There was some discussion about two weeks ago regarding this release,
but I am not sure how things ended. Carlo, do you know the status of
this release? Can I just uploa
On 18 April 2010 03:59, Søren Hauberg wrote:
>Hi All
>
> Carnë just mentioned that SourceForge blocks users from certain
> countries. They do this to comply with US export regulations. As a
> project administrator I can disable this blocking. This, however,
> requires that I agree to the following
Hmmm.. looking at this mail
http://sourceforge.net/mailarchive/message.php?msg_id=4BC4D154.7090508%40hccnet.nl,
I'd guess the package was never uploaded. Since you tried to download
a
file that didn't exist, it shows you the 'es' package which was the last to
be updated.
I tried to look into the p
On 27 April 2010 20:20, Liam Groener wrote:
> Hi,
> A new version of the io package, io-10.0.12, is listed at
> octave.sourceforge.net/packages.php . However when I click on the
> "download" link for this package, it transfers me to a general Octave
> download page (which doesn't include a link
Hi,
A new version of the io package, io-10.0.12, is listed at
octave.sourceforge.net/packages.php . However when I click on the "download"
link for this package, it transfers me to a general Octave download page (which
doesn't include a link to the package as far as I can see) instead of
downl
ons, 28 04 2010 kl. 03:00 +0200, skrev David Bateman:
> > Can we please deal with 1) before dealing with 2) ?
> >
> If telling you that you can't get around it is dealing with it, then
> consider it dealt with.
Will do :-)
Thanks for clearing up this stuff
Søren
ons, 28 04 2010 kl. 02:52 +0200, skrev David Bateman:
> I think you'll find every European country has signed this treaty...
> Sorry, this one you can't blame on the US and it also wouldn't help to
> migrate octave-forge somewhere else as we'd still be subject to the
> wassenaar treaty.
Well,
ons, 28 04 2010 kl. 02:37 +0200, skrev David Bateman:
> Soren, I'd say you can pretty safely say the Octave isn't using
> cyptography for the purposes of the source-forge export control check box.
Okay, thanks for the detailed reply. I have updated the project settings
to reflect this.
Thanks
Sø
Søren Hauberg wrote:
> tir, 27 04 2010 kl. 19:20 -0400, skrev Carnë Draug:
>
>> On 27 April 2010 17:11, Søren Hauberg wrote:
>> tor, 22 04 2010 kl. 07:38 +0200, skrev David Bateman:
>> > Octave includes the MD5 hashing algorithm and
>> uses /dev/random if
>> > av
On 27 April 2010 17:17, Søren Hauberg wrote:
> This looks good to me. Just to match the general style in Octave, I
> think you should rename '_zenity_options_' to '__zenity_options__' (two
> underscores instead of one). Alternatively, you should put this function
> into a 'private' directory.
>
>
Søren Hauberg wrote:
> Personally, I find the US Export control to be stupid at best, but I am
> not going to break it. I am also ridiculously low on time, so I am not
> going to spend hundreds of hours migrating to a different host unless we
> really have to.
>
Soren,
The EC export control rul
Carnë Draug wrote:
> On 27 April 2010 17:11, Søren Hauberg wrote:
>
>
>> tor, 22 04 2010 kl. 07:38 +0200, skrev David Bateman:
>>
>>> Octave includes the MD5 hashing algorithm and uses /dev/random if
>>> available in the core of Octave and there is an implementation of SHA1
>>> in the octa
tir, 27 04 2010 kl. 19:20 -0400, skrev Carnë Draug:
> On 27 April 2010 17:11, Søren Hauberg wrote:
> tor, 22 04 2010 kl. 07:38 +0200, skrev David Bateman:
> > Octave includes the MD5 hashing algorithm and
> uses /dev/random if
> > available in the core of Octave and
On 27 April 2010 17:10, Søren Hauberg wrote:
> > I know a bit of perl. The problem seems to be the file doc/gsl_sf.cc
> > which seems to be in the wrong place. The file is autogenerated by the
> > script src/buildgsl_sf.sh so I'm thinking it should be in src/ in the
> > first place. Anyway, move
On 27 April 2010 17:11, Søren Hauberg wrote:
> tor, 22 04 2010 kl. 07:38 +0200, skrev David Bateman:
> > Octave includes the MD5 hashing algorithm and uses /dev/random if
> > available in the core of Octave and there is an implementation of SHA1
> > in the octave-forge package general.. These are
ons, 21 04 2010 kl. 19:26 +0200, skrev Ulrich Hoermann:
> I use the IRR code from the financial package, but it does not work.
> The bug seems to be related to the way, the irr.m calls the fsolve
> function. The error message is as follows:
>
> error: error creating function handle "@npv (x, ...
ons, 21 04 2010 kl. 17:01 -0400, skrev Carnë Draug:
> On 11/04/2010, Søren Hauberg wrote:
> > Honestly, I have no idea. No one have written guidelines. In practice, I
> > think this issue happens very rarely, so I guess nobody bothered
> > figuring out how to deal with this. I realise this is not
tor, 22 04 2010 kl. 07:38 +0200, skrev David Bateman:
> Octave includes the MD5 hashing algorithm and uses /dev/random if
> available in the core of Octave and there is an implementation of SHA1
> in the octave-forge package general.. These are about the only crypto
> like functions that I know
søn, 25 04 2010 kl. 21:32 -0400, skrev Carnë Draug:
> On 25 April 2010 12:03, Søren Hauberg wrote:
> >
> > tor, 22 04 2010 kl. 22:14 +0200, skrev Thomas Weber:
> > > I'm forwarding below a bug report against the gsl package. The
> > > gsl_fs.pdf file included in SVN is doubled, that is every funct
On 27 Apr 2010, at 16:01, Alexander Barth wrote:
> Hi all,
> I released a new version of octcdf which should fix the cs-list bug
> (invalid assignment to cs-list outside multiple assignment) in octcdf.
> I have tested it with a recent checkout of octave (2010-04-24) version
> 3.3.51+. All tests p
On 26 Apr 2010, at 09:04, Javier Enciso wrote:
> Hi All,
>
> A new version of the Spanish package has been released. Main features
> include:
>
> - Support for special characters via UTF-8.
> - There are 1246 commands translated into Spanish so far.
>
> Problems: Nothing to report, although feedb
Hi all,
I released a new version of octcdf which should fix the cs-list bug
(invalid assignment to cs-list outside multiple assignment) in octcdf.
I have tested it with a recent checkout of octave (2010-04-24) version
3.3.51+. All tests pass now:
>> nctest
writing test output to nctest.log
> /
23 matches
Mail list logo
