Re: Bug#522017: ITP: jblas -- jblas is a fast linear algebra library for Java

2009-04-03 Thread Chris Walker
Matthias Klose d...@debian.org writes:

 Chris Walker schrieb:
  Soeren Sonnenburg so...@debian.org writes:
  
  Package: wnpp
  Severity: wishlist
  Owner: Soeren Sonnenburg so...@debian.org
 
  * Package name: jblas
  
  This package seems likely to be of interest to debian-science, so I'm
  sending this mail there too. 
 
 if jblas seems to be of interest to debian-science, please would you take care

 of atlas and an upgrade to atlas 3.8 as well? else I would suggest to Chris to
 just go ahead and maybe CC debian-java.

When I said jblas is of interest to debian-science, what I meant was
I think that some of the people on debian-science may be interested
in jblas, so please keep them informed of your progress. In addition,
debian-science is a good place to ask for help with science applications. 

Chris


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#522017: ITP: jblas -- jblas is a fast linear algebra library for Java

2009-03-31 Thread Chris Walker
Soeren Sonnenburg so...@debian.org writes:

 Package: wnpp
 Severity: wishlist
 Owner: Soeren Sonnenburg so...@debian.org
 
 * Package name: jblas

This package seems likely to be of interest to debian-science, so I'm
sending this mail there too. 

It would presumably fit into the mathematics-dev task.

And here is the rest of the description for debian-science readers. 

   Version : 0.1
   Upstream Author : Mikio Braun mikioATcs.tu-berlin.de
 * URL : https://ml01.zrz.tu-berlin.de/trac/jblas/
 * License : BSD
   Programming Lang: Java
   Description : jblas is a fast linear algebra library for Java
 
   jblas is a fast linear algebra library for Java. jblas is based on
   BLAS and LAPACK, the de-facto industry standard for matrix
   computations, and uses state-of-the-art implementations like ATLAS for
   all its computational routines, making jBLAS very fast. 
 
   jblas can is essentially a light-wight wrapper around the BLAS and
   LAPACK routines. These packages have originated in the Fortran
   community which explains their archaic API. On the other hand modern
   implementations are hard to beat performance wise. jblas aims to make
   this functionality available to Java programmers such that they do not
   have to worry about writing JNI interfaces and calling conventions of
   Fortran code.
 


Chris


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Grid tasks

2009-03-09 Thread Chris Walker
I propose we (Debian-science) create two grid tasks packages:

Grid-client: This would contain the packages  a user workstation needs to
submit jobs to the grid.

Grid-server: Packages for running a grid cluster. 

The globus packages recently proposed on debian-devel are obvious
candidates. 

Would there be support for creating a grid task, and splitting it this way?

Currently the packages are in the new queue. Should I wait until they
actually reach unstable before creating the task? Are there any other
obvious candidate packages?

Chris




-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#514485: ITP: globus-usage -- Globus Toolkit - Usage Library

2009-02-08 Thread Chris Walker
Steffen Moeller steffen_moel...@gmx.de writes:

 * Package name: globus-usage
 * URL : http://www.globus.org/
 * License : Apache 2
   Programming Lang: C/C++
   Description : Globus Toolkit - Usage Library
 
Debian-science has been collecting packages useful for science into
task packages - for more information look at
wiki.debian.org/DebianScience

There isn't currently a grid task - but it might be an obvious thing
to add (or perhaps grid-client and grid-server tasks). If there are
other obvious candidate packages for such a task, perhaps you could
post them on debian-science too.

Chris


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#508072: ITP: libtango -- tango library for the D programming language

2008-12-07 Thread Chris Walker
Markus Mahlberg [EMAIL PROTECTED] writes:

 Package: wnpp
 Severity: wishlist
 Owner: Markus Mahlberg [EMAIL PROTECTED]
 
 
 * Package name: libtango
   Version : 0.99.7
   Upstream Author : The Tango Team [EMAIL PROTECTED]
 * URL : http://www.dsource.org/projects/tango
 * License : Dual (Academic Free 3.0 or BSD)
   Programming Lang: D
   Description : tango library for the D programming language
 
 Tango is a cross-platform open-source software library, written in the D
 programming language for D programmers. 

Is it related to the tango package
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400201 for which a
preliminary package is available at
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=tango

 It is structured as a cohesive
 and comprehensive library for general purpose usage, and is supported by
 a growing number of recognized D enthusiasts. 


Chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#292539: xdslusb: please update to the latest upstream version

2005-02-19 Thread Chris Walker
[EMAIL PROTECTED] (Marco d'Itri) writes:

 I will probably not do any further work on this package, because the new
 cxacru driver will be merged in 2.6.11 or 2.6.12 and does not need user
 space components. So far, the plan is to have the package removed from
 the distribution after sarge will be released.

That thinking makes sense to me - though I don't use the package in
question. 

However can I urge you, and other package maintainers in a similar
position to mention this in the package description - and
README.Debian. 

Chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Do all frontends use the dpkg binary?

2005-01-23 Thread Chris Walker
Scott James Remnant [EMAIL PROTECTED] writes:

 This would mean the disk would gradually fill up with logs, unless you
 rotated them; which seems to defeat the use case everybody has given for
 dpkg's actions being logged in the first place.

Logs kept for a week would still be useful. 

A bug I filed[1] was closed with The real error was
printed by dpkg much earlier in the process; it probably scrolled off
your screen.

If I had had a dpkg log, it would have been possible to find the real
error.

[1] #285414. It wasn't clear where to file it - so I chose apt. Next
time I'll file it against dpkg.

Chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#32595: remove obsolete and confusing acquisition methods: harddisk, mounted, cdrom, nfs

1999-01-30 Thread Chris Walker
Jules Bean [EMAIL PROTECTED] writes:


On 31 Jan 1999, Martin Mitchell wrote:
 1) A m68k computer with a 60Mb debian installation. Normally I use the nfs
 method. Apt is just not feasible, it wants to copy everything over before
 it starts - there simply isn't space on the disk to do this. Also the
 runtime cost of starting dpkg on m68k is very high, so dselect is often
 much faster, rather than apt's invoking dpkg separately for many packages.
 (I am aware apt is more correct, however in practice so many invocations
 of dpkg are rarely necessary)

Hm.  I'm pretty sure the apt with a file:/ URL doesn't copy, it installs
straight from the remote.  Or is this not true?

 2) A local mirror, hand constructed. No extra or useless packages in there.
 Apt doesn't construct or handle this type of arrangement well by default.
 The mounted method deals with this just fine.

What problems does apt give?  (I assume you're running dpkg-scanpackages
to build local packages file?)


Having to run dpkg-scanpackages manually is a bit of a pain
Dpkg-mountable asks for a local package directory and will then scan
it automatically every time.

Having to work out that you need to run the following every time you
update the local packages file

 dpkg-scanpackages . /dev/null | gzip Packages.gz

and then add the following to your sources.list file:  

  deb file:///usr/local/debian-archive/ /

takes some working out. Answering yes to the question generate a
package file for me is easier.

Including the above information in the manual - if it hasn't found its
way there would be a useful start.


Incidentally, I'm not claiming Martin's objections are foundless.  I'm
interested to see what limitations apt has (and then we can request them
as features).

One other point. It isn't immediately obvious from the web site that you can
intall directly by ftp[1] without manually downloading the packages you
need and then installing them as separate steps.

The web site links to
ftp://ftp.debian.org/debian/dists/stable/main/disks-i386/current/ch-install-methods.html
which doesn't mention installing using ftp as a possibility (and
neither do the frozen and unstable versions). Writing some notes for
this bit of the document would be useful[2] (if it is thought that apt is
ready for this sort of use).

[1]Useful in UK academia where you have a fast network connection to a
mirror site.

[2] I wish I had the time to do this.

Chris



Re: dselect features request

1997-12-19 Thread Chris Walker

[EMAIL PROTECTED] writes:

While I had been a devoted Slackware fan, trying Debian convinced me
that it is far superior a distribution.  However, in the process of
installing Debian 1.3.1 at least 15 times (several computers and
several different plans on how to install them all) it occurred to me
that two features in `dselect` would be WONDERFUL!!!

1)  Once all packages are selected, be able to dump the selections to
a file that could be later read in for subsequent identical
installations. 

It would be nice to do this from dselect, but for the moment you can
quit dselect, and use:

dpkg --get-selections 

to get the list of selected packages, and

dpkg --set-selections to set them.

dpkg --help mentions these two.

I've not actually used these though. 

dpkg and dselect could do with better man pages, I agree. 

There is a project Deity to produce a dselect replacement, but I'm
not sure how near to release they are.

Chris





--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Conflict between Packages file and actual files

1997-05-23 Thread Chris Walker
Dale Scheetz [EMAIL PROTECTED] writes:

 
 On Thu, 22 May 1997, Bob Nielsen wrote:
 
  On Thu, 22 May 1997, Dale Scheetz wrote:
  
   On Thu, 22 May 1997, Bob Nielsen wrote:
   
In /frozen, the packages file shows:

procmail_3.10.4-1.deb
modconf-0.2.9.deb

The actual files are:

procmail-3.10.4-2.deb
modconf-0.2.10.deb

   This is a mirror sync problem. The packages file on master is correct.
   Give the mirror you are using some time to catch up and try again, or, you
   can crate your own, correct, Packages file using dpkg-scanpackages.
  
  I thought that might be the case, so I checked ftp.debian.org and got the
  same answer.  I ended up ftp'ing the two files and installing with dpkg
  rather than worry about dselect not accepting the packages file. 
  
 This is a continuous problem. I don't know why ftp.debian.org takes so
 long to get in sync with master, but the problem simply propogates from
 there to all the additional mirrors. Debian is the only distribution I
 know that depends so heavily on the accuracy of one file.

This sounds like a locking problem to me. 

If the archive on master changes while the mirror to ftp.debian.org is
running, then the packages file will obviously differ from the
contents of the archive. This can continue down the chain of
mirrors. 

Assuming no locking takes place, then differences become increasingly
likely as the time taken to update the mirror increases. Another
source of this is if the packages file on master is not updated
immediately after a package is added. These problems will presumably
settle if the archive is unchanged for a couple of days.
 
I strongly agree however that dselect ought to cope a lot better than it does
at present. I've had it fall over when it calls dpkg -iGROEB and a
package I'm not interested in has a broken symlink on the
archive. I've made a suggestion to the deity team that this should be
one thing to tackle.

Chris


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Sending closed bug notices to interested parties.

1997-05-21 Thread Chris Walker


On Wed, 14 May 1997, Christian Schwarz wrote:

 On Sun, 11 May 1997, Chris Walker wrote:
 
  Would some mechanism of saying when this bug is closed notify me as
  well eg by sending a specially formulated e-mail, or perhaps some web
  interface. This might be useful, as in general I probably don't want to
  see all bug report closures.
  
  Would anyone else be interested in this?
 
 Yes, I think that's a great idea. 

Ok, that's two positive responses, and none negative. Ian Jackson has said
he's willing to implement something like this if there is sufficient
support. 

Could interested parties please mail me to say whether they are likely to
use it, and if so how much. I'll collate the responses and send them to
Ian. 

eg

a) more than 5 times a week
b) once a week
c) once a month
d) once a quarter
e) once a year
f) never




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: sendmail/smail with relaying blocks?

1997-05-14 Thread Chris Walker
Tim Cutts wrote:
 
 On Fri, 9 May 1997, Craig Sanders wrote:
 
  On Thu, 8 May 1997, Mark Baker wrote:
 
   In article [EMAIL PROTECTED],
   Thomas Koenig [EMAIL PROTECTED] writes:
  
   I don't know what's in Tim's debian package though, as I was already
   running exim when I upgraded to debian and used my old configuration
   file.
 
 My exim package currently allows relaying; as Craig points out below, what
 you allow relaying to/from is extremely site-dependent. 

Agreed.

 I think it is
 more sensible to allow relaying by default; 

I beg to differ. I think what is the sensible default depends on the
usage of the machine. For departmental mail servers, then you are
correct relaying is more sensible, but for Satellite systems, it is
more sensible to block it. 

Could you ask a question at configuration time, probably defaulting to
not allowing relaying. If you want to be really clever, you could make a
guess based on earlier answers.

At the very least, a comment in the exim.conf file would be useful.

I don't think the above would be very difficult to implement, but I may
have missed something.

 without it remote mail from
 Eudora and the like will fail, and I'd rather it worked by default. 

Agreed, it is better if things work out of the box.

 I
 have only just restricted mail relaying on my largest exim site (an SG
 Origin 200 machine with 1200 accounts) since relaying abuse by spammers
 has only just become a significant problem.  As Mark suggested below, most
 use temporary accounts and the usual ISP's SMTP server.  I think most
 spammers are probably morons who don't actually have a clue how mail
 works.

Chris


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .