On Wed, Jul 28, 1999 at 04:35:54PM +0200, Jozef Hitzinger wrote:
There are two daemons, running as nobody.nogroup, and they need to access
the state file (/var/state/ups/*). Could you tell me where how to chown
Are you sure you want to use nobody.nogroup? If multiple packages use
the same UID
On Thu, Jul 29, 1999 at 01:58:15AM -0500, Manoj Srivastava wrote:
Buddha It seems that there is a missing step -- verification that I
Buddha know John Smith's private key. Without that, you are
How can you know someone's private key? (A nit: In any case,
you don't sign a private
When I submitted my application I attached a scanned
license and passport as requested, because I didn't
know any local debian maintainers (still don't).
[ snip ]
Should I find someone(s) to sign my key?
If so, do we have a geographical list of
maintainers/developers, or do you know of
I am packaging an install wrapper package for the [EMAIL PROTECTED] client. I
have a question about dependencies caused by maintainer scripts.
The client binary is to be downloaded as a tarball from the official
[EMAIL PROTECTED] webpage. At the official webpage, they have optimized
binaries for
Hi,
Brian == Brian May [EMAIL PROTECTED] writes:
Brian You need to be sure that you are signing the *correct* public
Brian key, and not just any public key that happened to be created
Brian with John Smith's id (which is publicly known).
When I sign a key, I have am standing in front
On Fri, Jul 30, 1999 at 01:29:35AM -0500, Manoj Srivastava wrote:
This is quite confused. The fingerprint is of the public key
(or else how do you check it? No one should be giving anyone a look
at the private key at all).
Thats exactly what I meant.
I think you are missing
I have fixed some bugs in the gftp and gnotes packages, and I would like
to tell this to the BTS.
I am not the official developer of these packages (although I am willing
to take them over), and I am not an official developer either.
What should I do to mark the bugs as fixed. Send a command
On Fri, Jul 30, 1999 at 01:29:35AM -0500, Manoj Srivastava wrote:
Brian You need to be sure that you are signing the *correct* public
Brian key, and not just any public key that happened to be created
Brian with John Smith's id (which is publicly known).
When I sign a key, I have
On Fri, Jul 30, 1999 at 11:53:23AM +0200, Etienne Bernard wrote:
I have fixed some bugs in the gftp and gnotes packages, and I would like
to tell this to the BTS.
I am not the official developer of these packages (although I am willing
to take them over), and I am not an official developer
On Fri, Jul 30, 1999, Josip Rodin wrote:
Are the fixed packages in the archive? If not, you must not mark them
fixed.
They are available on http://www.via.ecp.fr/~eb/debian/ and I am waiting
for an official developer to upload them (I don't remember his name, and
his mail is on my machine,
Hi,
Brian == Brian May [EMAIL PROTECTED] writes:
Brian So we agree. You wouldn't sign the key without checking the
Brian fingerprint first. The idea being, if the fingerprint matches,
Brian then John Smith must have the matching private key (and not
Brian somebody else).
Yes, though
Hi,
[cross posted to debian-user, since this has gone beyond the
charter of the -mentor list] ;-)
Joseph == Joseph Carter [EMAIL PROTECTED] writes:
Brian == Brian May [EMAIL PROTECTED] writes:
Brian So we agree. You wouldn't sign the key without checking the
Brian fingerprint
Scenery is here, wish you were beautiful.
On Fri, 30 Jul 1999, Joseph Carter wrote:
On Fri, Jul 30, 1999 at 01:29:35AM -0500, Manoj Srivastava wrote:
Brian You need to be sure that you are signing the *correct* public
Brian key, and not just any public key that happened to be created
Hi,
Etienne == Etienne Bernard [EMAIL PROTECTED] writes:
Etienne On Fri, Jul 30, 1999, Josip Rodin wrote:
Are the fixed packages in the archive? If not, you must not mark them
fixed.
Etienne They are available on http://www.via.ecp.fr/~eb/debian/ and
Etienne I am waiting for an
On Fri, Jul 30, 1999 at 08:32:23AM -0500, Jor-el wrote:
Scenery is here, wish you were beautiful.
wish you were a little less (not much though) paranoid.. =p
Actually, there could be a possible reason for this if the
rejection criteria applied by the new-maintainers group is applied
On Fri, Jul 30, 1999 at 11:41:37AM -0500, Manoj Srivastava wrote:
/*
* keeping -mentors for this message only, replies are likely to get even
* more off-charter for that group, so don't reply there. Note I'm not
* subscribed to -user, however...
*/
Yes, though now that you point it
On 28-Jul-99 Steven V. Russo wrote:
I wonder if anyone can tell me why no one has responded to me from
[EMAIL PROTECTED] I submitted my application months ago, and
sent two follow up applications. I believe I followed their procedure
as closely as possible... How can I get a response from
I'm looking for advice/experience if you can help:
We have a patch to ispell, submitted to one of the
open bugs, which upstream maintainer has decided
isn't important enough to incorporate into the
upstream versions -- but is (apparently) needed
for non-i386 (Alpha, at least) compatibility in
I would talk more with the upstream. Does the patch break ispell? Is it not
possible to incorporate it? Simply it is not significant makes no sense.
Work with them, see how you can get it in. Otherwise, have the non Intel
people start complaining to this person. If it is not a Debian
On Fri, 30 Jul 1999, David Coe wrote:
So I think I'll create a source patch file
and add a rule to debian/rules to apply it
for each build. The alternative, of course,
would be to just apply the patch once to
the working source tree, and let the .deb
system handle it.
I think I like
On Fri, Jul 30, 1999 at 08:18:14PM +, David Coe wrote:
We have a patch to ispell, submitted to one of the
open bugs, which upstream maintainer has decided
isn't important enough to incorporate into the
upstream versions -- but is (apparently) needed
for non-i386 (Alpha, at least)
21 matches
Mail list logo
