https://bugzilla.novell.com/show_bug.cgi?id=393160
User ma@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393160#c37
--- Comment #37 from Michael Andres 2008-07-07 03:56:07 MDT ---
I just logged into morgenrot (the machine the logs came from). I checked the
repositories in use, and found the old key
KEY SHA1 30726e9a2959dbe9cace5765edd038e0538878ad
gpg-pubkey-9c800aca-40d8063e.asc
on
SUSE Linux Enterprise Software Development Kit 10 SP1
ftp://schnell.suse.de/CD-ARCHIVE/SLES10/SLE-10-SP1/SLE-10-SP1-SDK-GM/ppc/DVD1
SUSE Linux Enterprise Server 10 SP1
ftp://schnell.suse.de/CD-ARCHIVE/SLES10/SLE-10-SP1/SLES-10-SP1-GM/ppc/DVD1
Both repositories do _NOT_ contain the updated key remote. So how should the
key be updated, if no repository provides it?
(did you consider to use a patch script together with the suse-build-key patch,
that introduces the key into the rpmdb?)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.