> gpg: Can't check signature: public key not found
> [CraigRussell:~/Downloads] clr% gpg --recv-keys 42196CA8
> gpg: requesting key 42196CA8 from hkp server subkeys.pgp.net
> gpgkeys: key 42196CA8 not found on keyserver
Thanks, i sent it to several keyservers now :-)
Can you try again?
Christian
James Carman wrote at Mittwoch, 6. Mai 2009 03:12:
> On Tue, May 5, 2009 at 6:36 PM, Matt Benson wrote:
>>
>> I feel differently--how many times do we need to duplicate code that does
>> the same damned thing amongst the various components? For example, we've
>> now added MethodUtils to [lang],
Not so good.
Here's what I get after downloading the two files:
[CraigRussell:~/Downloads] clr% gpg --verify commons-chain-1.2-
bin.tar.gz.asc
gpg: Signature made Tue May 5 22:13:09 2009 PDT using DSA key ID
42196CA8
gpg: Can't check signature: public key not found
[CraigRussell:~/Downloads
> Why not try creating a signature for an existing Commons release, e.g. IO?
> Upload it to your home directory on people, along with the public key,
> and some of us can see if it is usable.
That would be great! Thanks!
Here are the urls:
http://people.apache.org/~grobmeier/test/commons-chain-1.
Hi,
> as far as I remember CACert is about X.509 certificates and not PGP
> keys. If that assumption is true than this key is not usable for
> PGP-signing.
yes, but if you are assured at CACert they offer signing your PGP too.
Thanks
Christian
---
On Tue, May 5, 2009 at 6:36 PM, Matt Benson wrote:
>
> I feel differently--how many times do we need to duplicate code that does the
> same damned thing amongst the various components? For example, we've now
> added MethodUtils to [lang], but [collections] has its own set of code
> supporting
On Tue, May 5, 2009 at 8:46 PM, Torsten Curdt wrote:
>> Using what strategy, Torsten?
>
> Not sure I understand the question. But let's try:
I think the question was "using what existing
technology/framework/tool/etc"? Something like uberjar, perhaps?
---
> Using what strategy, Torsten?
Not sure I understand the question. But let's try:
In the source code "org.apache.commons.something" uses "org.apache.commons.else"
In the released jar "org.apache.commons.something" will use
"x.org.apache.commons.else"
All dependencies are getting in-lined and a
> -Original Message-
> From: Matt Benson [mailto:gudnabr...@yahoo.com]
> Sent: Tuesday, May 05, 2009 3:36 PM
> To: Commons Developers List
> Subject: Re: [COLLECTIONS] 3.3 release
>
>
>
>
> --- On Tue, 5/5/09, Stephen Colebourne
> wrote:
>
> > From: Stephen Colebourne
> > Subject: Re
--- On Tue, 5/5/09, Torsten Curdt wrote:
> From: Torsten Curdt
> Subject: Re: [COLLECTIONS] 3.3 release
> To: "Commons Developers List"
> Date: Tuesday, May 5, 2009, 6:43 PM
> > I think its really important
> that [collections] has no dependencies. As part of that, I'd
> also suggest that [f
--- On Tue, 5/5/09, sebb wrote:
> From: sebb
> Subject: Re: [COLLECTIONS] 3.3 release
> To: "Commons Developers List"
> Date: Tuesday, May 5, 2009, 6:02 PM
> On 05/05/2009, Matt Benson
> wrote:
> >
> >
> >
> > --- On Thu, 4/30/09, James Carman
> wrote:
> >
> > > From: James Carman
> >
> I think its really important that [collections] has no dependencies. As part
> of that, I'd also suggest that [functor] shouldn't have dependencies.
>
> While I understand the arguments of just picking up another jar if your using
> it, of tools like maven, and of eating dog food, when push com
On 05/05/2009, Matt Benson wrote:
>
>
>
> --- On Thu, 4/30/09, James Carman wrote:
>
> > From: James Carman
> > Subject: Re: [COLLECTIONS] 3.3 release
> > To: "Commons Developers List"
> > Date: Thursday, April 30, 2009, 12:18 AM
>
> > I would love to see a collections
> > version that is
--- On Tue, 5/5/09, Stephen Colebourne wrote:
> From: Stephen Colebourne
> Subject: Re: [COLLECTIONS] 3.3 release
> To: "Commons Developers List"
> Date: Tuesday, May 5, 2009, 4:37 PM
>
> Matt Benson wrote:
> > --- On Tue, 5/5/09, James Carman
> wrote:
> >> I'm trying to remember myself! :
Matt Benson wrote:
> --- On Tue, 5/5/09, James Carman wrote:
>> I'm trying to remember myself! :) I would think
>> collections, since
>> that's what this email was regarding. Is there a
>> branch that gets rid
>> of Transformer, Closure, and Predicate from collections and
>> instead
>> uses Fun
Why not try creating a signature for an existing Commons release, e.g. IO?
Upload it to your home directory on people, along with the public key,
and some of us can see if it is usable.
S.
On 05/05/2009, Siegfried Goeschl wrote:
> Hi Christian,
>
> as far as I remember CACert is about X.509 cer
--- On Tue, 5/5/09, James Carman wrote:
> From: James Carman
> Subject: Re: [COLLECTIONS] 3.3 release
> To: "Commons Developers List"
> Date: Tuesday, May 5, 2009, 12:35 PM
> On Tue, May 5, 2009 at 1:14 PM, Matt
> Benson
> wrote:
> > Notwithstanding the fact that I'm way behind on email,
> w
On Tue, May 5, 2009 at 1:14 PM, Matt Benson wrote:
> Notwithstanding the fact that I'm way behind on email, what is "it" above?
>
> [functor]'s generification has been complete for nearly a year.
> [collections] is done in the branch AFAIK. I simply haven't had time to
> figure out how to get sv
--- On Thu, 4/30/09, James Carman wrote:
> From: James Carman
> Subject: Re: [COLLECTIONS] 3.3 release
> To: "Commons Developers List"
> Date: Thursday, April 30, 2009, 12:18 AM
> I would love to see a collections
> version that is based on
> commons-functor (once it's generified).
Notwiths
Hi Christian,
as far as I remember CACert is about X.509 certificates and not PGP
keys. If that assumption is true than this key is not usable for
PGP-signing.
Cheers,
Siegfried Goeschl
Christian Grobmeier wrote:
> Hi all,
>
> I am sorry for asking dumb, but I am a complete idiot on all that
>
Hi all,
I am sorry for asking dumb, but I am a complete idiot on all that
encryption stuff.
I read this: http://wiki.apache.org/commons/CreatingReleases
and all the links in the section of signature keys. i understand how PGP works.
I have a key created and this has been signed by CACert where I
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-ojb has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
23 matches
Mail list logo