-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Saturday 2006-05-06 at 01:45 +0200, houghi wrote:

> > > > 5 keys... there are exactly 5 ascii key files also.
> > > 
> > > There are 6 *.asc keys.
> > 
> > I have five in CD1:

Notice I say CD1, not DVD.

> > 
> >   gpg-pubkey-0dfb3188-41ed929b.asc   
> >   gpg-pubkey-1d061a62-427a396f.asc             1007  Apr 26 00:00 
> >   gpg-pubkey-307e3d54-44201d5d.asc              613  Apr 26 00:00 
> >   gpg-pubkey-3d25d3d9-36e12d04.asc             1694  Apr 26 00:00 
> >   gpg-pubkey-9c800aca-40d8063e.asc             2173  Apr 26 00:00 
> 
> After running http://houghi.org/script/makeSUSEdvd ?

Yes, but not today, certainly. I run it when I made the dvd with which I 
updated from RC2 to RC3 last weekend. I told you about that already. I 
haven't tried again, I was going to wait for RC4 that now will not exist.

> 
> > The message does not even say what package has the wrong signature. And it 
> > says that before telling it to install anything at all.
> 
> This thread is about makeSUSEdvd. It is about making an iso that is
> bootable. It is not about the standard SUSE iso and then an upgrade from
> RC2 to RC3.

Of course. That's what I did. I created that DVD and updated with it. And 
then, every time I fired YOU I got that pesky message about a bad 
signature that did not say what package or file had a bad signature. The 
problem stopped when I changed the installation source to the CD.iso for 
the already installed system.

Remember that I asked about that and was told it was a problem with 
makeSUSEdvd. You said that it did not work, but it has worked for me.

- -- 
Cheers,
       Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFEW+sDtTMYHG2NR9URAo9gAJ4hwuJN91pKsKpjPEY+XT+LK1xFUgCgingA
N4cpiRT8QG2mIDXXw54UQsk=
=KMCp
-----END PGP SIGNATURE-----


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to