On Sat, 2003-01-11 at 23:55, Mark Scott wrote:
> [EMAIL PROTECTED] wrote:
> > On Sat, 11 Jan 2003 [EMAIL PROTECTED] wrote:
> >>
> >>I've made "sdd" SRPMs: one older, one newer. The newer seems pretty 
> >>stable, so it might be enough to stick that one into contribs.
> >>
> >>Somebody please let me know where / how / to whom to upload it, so it 
> >>gets into contribs, or, better, please take it (recompile) and put it 
> >>where it should be, and just let me know, so I can use the diskspace on 
> >>the website again.
> >>
> >>The two packages can be found at:
> >>
> >>http://Honza.Vicherek.com/sdd-1.31-1.src.rpm
> >>http://Honza.Vicherek.com/sdd-1.22-2.src.rpm
> >>
>  >OK, I've also uploaded the i586.rpm's:
>  >http://Honza.Vicherek.com/sdd-1.31-1.i586.rpm
>  >http://Honza.Vicherek.com/sdd-1.22-2.i586.rpm
>  >
>  >John
>  >
> 
> In case you hadn't read them, this page gives an outline of the process 
> (scroll down to "How to contribute some packages to Cooker?"):
> http://www.mandrakelinux.com/en/cookerdevel.php3
> 
> And did you read this before packaging the RPMs? It deals with 
> Mandrake-specific rules and methods for RPM packaging.
> http://www.mandrakelinux.com/en/howtos/mdk-rpm/
> 
> In particular, you seem to have missed something about the package name:
> "The release is a number followed by mdk (stands for "Mandrake"; this is 
> absolutely mandatory) which is incremented at each new build of the 
> package."
> http://www.mandrakelinux.com/en/howtos/mdk-rpm/building.html#AEN204
> 
> So, your package should be sdd-1.31-1mdk.i586.rpm.
> 
> -- 
> Mark Scott
> 

Some comments on the "How to contribute some packages to Cooker" section
of the web page. To quote:

> Next, get and install GnuPG :
>
> - get our GnuPG package from 
> ftp://ftp.sunet.se/pub/Linux/distributions/mandrake-crypto/

This directory is completely empty, nothing, de nada.

> - install it;

Happily, I found that I had installed gnupg with Mandrake Linux 9.0.

> - create a .gpg directory in your home directory: mkdir ~/.gpg

I did this.

> - in order to generate your GnuPG keys type: "gpg --gen-key"

gnupg complained that there was no .gnupg directory, created one for me,
and created an options file as well, then told me to start gnupg again
so it can read the new options file.

> select option "1) 1024 bits- Low commercial grade..."

Well, the options are:
   (1) DSA and ElGamal (default)
   (2) DSA (sign only)
   (4) ElGamal (sign and encrypt)
   (5) RSA (sign only)

So I chose 1 anyways.

gnupg then asked me for the desired keylength. 1024 is the default, so I
hit return.

gnupg then asked me how long the key should be valid. 0 (key does not
expire) is the default, so I hit return.

> - enter your Firstname+Name+email address @linux-mandrake.com
> (for example: if your name is "John Smith" and your email address is
> "[EMAIL PROTECTED]", then enter: John Smith
> [EMAIL PROTECTED])

Hmm, I don't have an @linux-mandrake.com email address. Should I?

gnupg prompts me for my real name, email address, then a comment. So I
use "Dan Scott", "[EMAIL PROTECTED]", "".

So far, so good. But then...

> In order to extract a public ascii key:
> - type: gpg -kxa

Hmm. gnupg doesn't recognize those options. I search the man page for
gnupg and the closest thing I can find is gpg --clearsign. I try it,
enter my passphrase for confirmation, and... nothing. It just sits
there.

Read the gnupg FAQ and HOWTO and eventually figured out that I really
want something like:

gpg --armor --output asc.key --export "Dan Scott"

That's as far as I have come in the process. I've been working in my
spare time since the end of December to try and contribute an RPM for
Figaro's Password Manager to club-volunteers. But critical process
information is either split between the Mandrake RPM HOWTO, web pages,
the club-volunteers FAQ, and occasional messages on the cooker list, or
it's a little out of date.

Any chance that we could update the Mandrake RPM HOWTO and move the RPM
signing information into a chapter of the HOWTO? I know Docbook, so I
might be able to be coaxed into updating the beast a wee bit...

(All this to say that I'm not surprised to find someone else having
trouble getting started in the world of contributions to Mandrake...
Stick with it, John!)

Dan








Reply via email to