Yesterday I put my name on the applicant list for the New Maintainer
program, and I was wondering: Is it too early to put my name on the Debian
Key Signing Coordination Page to start looking for someone to sign my key
for the identification phase? And if it's not, and someone reading this is
locate
On Tue, Dec 12, 2000 at 01:09:38AM -0500, Harry Henry Gebel wrote:
> Yesterday I put my name on the applicant list for the New Maintainer
> program, and I was wondering: Is it too early to put my name on the Debian
> Key Signing Coordination Page to start looking for someone to sign my key
> for th
Hi,
I am packaging mpich, and to fix the outstanding wishlist bug, I have created
binaries which
call "ssh" instead of "rsh".
I am not sure at all about the current situation surrounding crypto.
Does being able to execute ssh belong to non-US ?
My best guess is that just being able to execute
On Tue, 12 Dec 2000, Harry Henry Gebel wrote:
> Yesterday I put my name on the applicant list for the New Maintainer
> program, and I was wondering: Is it too early to put my name on the Debian
> Key Signing Coordination Page to start looking for someone to sign my key
> for the identification pha
Junichi Uekawa wrote:
> Hi,
>
> I am packaging mpich, and to fix the outstanding wishlist bug, I have created
> binaries which
> call "ssh" instead of "rsh".
It seems this will slow things down a LOT, and considering MPI is usually used
for
high-performance computing, I wouldn't make this stand
In Tue, 12 Dec 2000 08:41:55 -0500 Adam C Powell IV <[EMAIL PROTECTED]> cum
veritate scripsit :
> > Hi,
> >
> > I am packaging mpich, and to fix the outstanding wishlist bug, I have
> > created binaries which
> > call "ssh" instead of "rsh".
>
> It seems this will slow things down a LOT, and co
At Tue, 12 Dec 2000 20:35:27 +0900,
Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> I am packaging mpich, and to fix the outstanding wishlist bug, I have created
> binaries which
> call "ssh" instead of "rsh".
Why not use environment variables for rsh/ssh program name (like $CVS_RSH for
cvs, $RSYNC
On Tue, Dec 12, 2000 at 11:35:05PM +0900, Fumitoshi UKAI wrote:
> Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> > I am packaging mpich, and to fix the outstanding wishlist bug, I have
> > created binaries which
> > call "ssh" instead of "rsh".
> Why not use environment variables for rsh/ssh progra
* Junichi Uekawa
| It would be a non-problem if ssh provided rsh.
It does, kind of:
$ls -l /etc/alternatives/rsh
lrwxrwxrwx1 root root 12 nov 17 16:23 \
/etc/alternatives/rsh -> /usr/bin/ssh*
how about having mpich depending on rsh | ssh, and then using the link
in alternativ
Hi,
In 12 Dec 2000 16:15:35 +0100 Tollef Fog Heen <[EMAIL PROTECTED]> cum veritate
scripsit :
> | It would be a non-problem if ssh provided rsh.
>
> It does, kind of:
>
> $ls -l /etc/alternatives/rsh
> lrwxrwxrwx1 root root 12 nov 17 16:23 \
> /etc/alternatives/rsh -> /usr/b
* Junichi Uekawa
| > how about having mpich depending on rsh | ssh, and then using the link
| > in alternatives?
|
| No, the right way will be the package providing rsh having a "Provides: rsh"
| in its description.
|
| A bug report is due, I think.
perhaps so.
| >
| > | Now, what about a pa
In Wed, 13 Dec 2000 01:12:59 +0900 Junichi Uekawa <[EMAIL PROTECTED]> cum
veritate scripsit :
>
> No, the right way will be the package providing rsh having a "Provides: rsh"
> in its description.
Sorry, mistake.
The "virtual names" policy states it's "Provides: rsh-client".
regards,
Greetings! This is a good question, and I'd like to solicit the
feedback of likely atlas users on this.
1) Would you prefer the package to
a) install the best binary for your system
b) install all binaries appropriate to you arch under the
appropriate /usr/lib/??? director
On 09-Dec-2000 Cord Beermann wrote:
> Hi.
>
> I've built a new jove-package, that now matches the current standards,
> i also added some debhelper functions, a beginners menu, activated the
> recovery-function, and fixed the Bug that stops it from working on the
> Hurd.
>
> The current maintaine
On 11-Dec-2000 Michael Moerz wrote:
> Hi!
>
> Just in case that I have detected an unattandend maintainer
> who hasn't fixed bugs at least for half a year and never
> answeres to direct mails ( have been waiting for an answere
> now more than a month ), what should I do?
>
> I am really interest
Can anybody tell me why I get this error so _much_ when I am compiling a
kernel?
I litteraly get it hundreds of times (seriously). I wrote a script that
gives up after 256 errors, and I it still times outs.
I am using debian woody with kernel 2.2.17.
I do have bin86 installed and these other pro
James Leigh <[EMAIL PROTECTED]> wrote:
>Can anybody tell me why I get this error so _much_ when I am compiling a
>kernel?
[...]
>cc: Internal compiler error: program cc1 got fatal signal 11
Chances are you've got hardware problems, probably bad memory. See
http://www.bitwizard.nl/sig11/>.
--
Col
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
>
> I am using debian woody with kernel 2.2.17.
> I do have bin86 installed and these other programs too:
> gcc2.95.2-20
> make 3.79.1-1
> bin86 0.15.3-1
> binutils 2.10.1.0.2-1
> bzip2 1.0.1
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
Are you overclocking your CPU? This problem is probably caused by memory
corruption, which sometimes happens when you overclock your CPU too much.
Or i
On 12-Dec-2000 James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
please take this to debian-user, debian-m
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> I do not have as much trouble compiling programs, but real trouble
> compiling a kernel. This is the error I always get. It seems that it
> returns the error for almost every f*n *.c file in there, one after
> another. Some of then t
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
> I am using deb
Package: water
Severity; wishlist
Description:
water is a nice graphical water effect demo written using SDL.
You have lots of options to cause many different effectsm like
rain, swirls, blobs etc.
Copyright: Copyright (C) 1997 Scott Scriven
License: GPL
Upstream URL: http://www.libsdl.org/p
ok. i hope that i'm at the right place to ask this. I think it would
be good to have a mentor as this would be my first official
Debian-package]
>> I've built a new jove-package, that now matches the current standards,
>> i also added some debhelper functions, a beginners menu, activated the
>> re
On Tue, 12 Dec 2000, Pete Lypkie wrote:
>...
> > gcc2.95.2-20
>...
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
>
> you can install it from the package called "gcc272".
>
> IIRC, the 2.4 series has moved to using gcc 2.95, but 2.2 still needs gcc
> 2.7.2
>
On Tue, Dec 12, 2000 at 08:41:55AM -0500, Adam C Powell IV wrote:
> You might look into making it work with kerberos4kth's krsh/krshd for strong
> authentication
> without the encryption overhead. Unless you really need all communication to
> be encrypted
> (doing classified computations on an
It turns out it was an overclocked cpu problem. Thanks for the all
help, I guess I will have to get a bigger fan, before I can really
overclock my AMD350. You cannot imagen the weight off my shoulders now
that I can compile again. I was sceptical about it being my memory
because my 128MB 16x64 D
I used to get this error many years ago on a Cyrix processor with redhat 4.
Redhat had a patch for it. Are you running a Cyrix processor?
On Tue, Dec 12, 2000 at 11:30:19PM +0100, Adrian Bunk wrote:
> On Tue, 12 Dec 2000, Pete Lypkie wrote:
>
> >...
> > > gcc2.95.2-20
> >...
> > Fir
What's the "best" way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is there's a simple manpage editor out there, or a
sensible emacs mode,
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
> What's the "best" way of maintaining or creating a man page?
>
> I'll be needing to do that with some of my packages, but it just occurred to
> me I don't actually know how, apart from cutting and pasting in a text
> editor. My gues
On Tue, Dec 12, 2000 at 01:09:38AM -0500, Harry Henry Gebel wrote:
> Yesterday I put my name on the applicant list for the New Maintainer
> program, and I was wondering: Is it too early to put my name on the Debian
> Key Signing Coordination Page to start looking for someone to sign my key
> for t
Hi,
I am packaging mpich, and to fix the outstanding wishlist bug, I have created binaries
which
call "ssh" instead of "rsh".
I am not sure at all about the current situation surrounding crypto.
Does being able to execute ssh belong to non-US ?
My best guess is that just being able to execute
On Tue, 12 Dec 2000, Harry Henry Gebel wrote:
> Yesterday I put my name on the applicant list for the New Maintainer
> program, and I was wondering: Is it too early to put my name on the Debian
> Key Signing Coordination Page to start looking for someone to sign my key
> for the identification ph
Junichi Uekawa wrote:
> Hi,
>
> I am packaging mpich, and to fix the outstanding wishlist bug, I have created
>binaries which
> call "ssh" instead of "rsh".
It seems this will slow things down a LOT, and considering MPI is usually used for
high-performance computing, I wouldn't make this standa
In Tue, 12 Dec 2000 08:41:55 -0500 Adam C Powell IV <[EMAIL PROTECTED]> cum veritate
scripsit :
> > Hi,
> >
> > I am packaging mpich, and to fix the outstanding wishlist bug, I have created
>binaries which
> > call "ssh" instead of "rsh".
>
> It seems this will slow things down a LOT, and cons
At Tue, 12 Dec 2000 20:35:27 +0900,
Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> I am packaging mpich, and to fix the outstanding wishlist bug, I have created
>binaries which
> call "ssh" instead of "rsh".
Why not use environment variables for rsh/ssh program name (like $CVS_RSH for
cvs, $RSYNC
On Tue, Dec 12, 2000 at 11:35:05PM +0900, Fumitoshi UKAI wrote:
> Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> > I am packaging mpich, and to fix the outstanding wishlist bug, I have created
>binaries which
> > call "ssh" instead of "rsh".
> Why not use environment variables for rsh/ssh program
* Junichi Uekawa
| It would be a non-problem if ssh provided rsh.
It does, kind of:
$ls -l /etc/alternatives/rsh
lrwxrwxrwx1 root root 12 nov 17 16:23 \
/etc/alternatives/rsh -> /usr/bin/ssh*
how about having mpich depending on rsh | ssh, and then using the link
in alternati
Hi,
In 12 Dec 2000 16:15:35 +0100 Tollef Fog Heen <[EMAIL PROTECTED]> cum veritate scripsit :
> | It would be a non-problem if ssh provided rsh.
>
> It does, kind of:
>
> $ls -l /etc/alternatives/rsh
> lrwxrwxrwx1 root root 12 nov 17 16:23 \
> /etc/alternatives/rsh -> /usr/b
* Junichi Uekawa
| > how about having mpich depending on rsh | ssh, and then using the link
| > in alternatives?
|
| No, the right way will be the package providing rsh having a "Provides: rsh"
| in its description.
|
| A bug report is due, I think.
perhaps so.
| >
| > | Now, what about a p
In Wed, 13 Dec 2000 01:12:59 +0900 Junichi Uekawa <[EMAIL PROTECTED]> cum veritate
scripsit :
>
> No, the right way will be the package providing rsh having a "Provides: rsh"
> in its description.
Sorry, mistake.
The "virtual names" policy states it's "Provides: rsh-client".
regards,
Greetings! This is a good question, and I'd like to solicit the
feedback of likely atlas users on this.
1) Would you prefer the package to
a) install the best binary for your system
b) install all binaries appropriate to you arch under the
appropriate /usr/lib/??? directo
On 09-Dec-2000 Cord Beermann wrote:
> Hi.
>
> I've built a new jove-package, that now matches the current standards,
> i also added some debhelper functions, a beginners menu, activated the
> recovery-function, and fixed the Bug that stops it from working on the
> Hurd.
>
> The current maintain
On 11-Dec-2000 Michael Moerz wrote:
> Hi!
>
> Just in case that I have detected an unattandend maintainer
> who hasn't fixed bugs at least for half a year and never
> answeres to direct mails ( have been waiting for an answere
> now more than a month ), what should I do?
>
> I am really interes
Can anybody tell me why I get this error so _much_ when I am compiling a
kernel?
I litteraly get it hundreds of times (seriously). I wrote a script that
gives up after 256 errors, and I it still times outs.
I am using debian woody with kernel 2.2.17.
I do have bin86 installed and these other pr
James Leigh <[EMAIL PROTECTED]> wrote:
>Can anybody tell me why I get this error so _much_ when I am compiling a
>kernel?
[...]
>cc: Internal compiler error: program cc1 got fatal signal 11
Chances are you've got hardware problems, probably bad memory. See
http://www.bitwizard.nl/sig11/>.
--
Co
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
>
> I am using debian woody with kernel 2.2.17.
> I do have bin86 installed and these other programs too:
> gcc2.95.2-20
> make 3.79.1-1
> bin86 0.15.3-1
> binutils 2.10.1.0.2-1
> bzip2 1.0.
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
Are you overclocking your CPU? This problem is probably caused by memory
corruption, which sometimes happens when you overclock your CPU too much.
Or
On 12-Dec-2000 James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
please take this to debian-user, debian-
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> I do not have as much trouble compiling programs, but real trouble
> compiling a kernel. This is the error I always get. It seems that it
> returns the error for almost every f*n *.c file in there, one after
> another. Some of then
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
> I am using de
ok. i hope that i'm at the right place to ask this. I think it would
be good to have a mentor as this would be my first official
Debian-package]
>> I've built a new jove-package, that now matches the current standards,
>> i also added some debhelper functions, a beginners menu, activated the
>> r
On Tue, 12 Dec 2000, Pete Lypkie wrote:
>...
> > gcc2.95.2-20
>...
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
>
> you can install it from the package called "gcc272".
>
> IIRC, the 2.4 series has moved to using gcc 2.95, but 2.2 still needs gcc
> 2.7.2
Package: water
Severity; wishlist
Description:
water is a nice graphical water effect demo written using SDL.
You have lots of options to cause many different effectsm like
rain, swirls, blobs etc.
Copyright: Copyright (C) 1997 Scott Scriven
License: GPL
Upstream URL: http://www.libsdl.org/
On Tue, Dec 12, 2000 at 08:41:55AM -0500, Adam C Powell IV wrote:
> You might look into making it work with kerberos4kth's krsh/krshd for strong
>authentication
> without the encryption overhead. Unless you really need all communication to be
>encrypted
> (doing classified computations on an u
It turns out it was an overclocked cpu problem. Thanks for the all
help, I guess I will have to get a bigger fan, before I can really
overclock my AMD350. You cannot imagen the weight off my shoulders now
that I can compile again. I was sceptical about it being my memory
because my 128MB 16x64
I used to get this error many years ago on a Cyrix processor with redhat 4. Redhat
had a patch for it. Are you running a Cyrix processor?
On Tue, Dec 12, 2000 at 11:30:19PM +0100, Adrian Bunk wrote:
> On Tue, 12 Dec 2000, Pete Lypkie wrote:
>
> >...
> > > gcc2.95.2-20
> >...
> > Fi
What's the "best" way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is there's a simple manpage editor out there, or a
sensible emacs mode
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
> What's the "best" way of maintaining or creating a man page?
>
> I'll be needing to do that with some of my packages, but it just occurred to
> me I don't actually know how, apart from cutting and pasting in a text
> editor. My gue
On Wed, Dec 13, 2000 at 12:59:30AM -0500, Matt Zimmerman wrote:
>
> If you don't want to do SGML, you could always edit the nroff source directly.
> This is what has been done historically. SGML, however, makes it easier to
> render the manpage in different ways in the future.
>
I wouldn't nece
60 matches
Mail list logo
