On Tue, 12 Mar 2013 10:42:23 +0100 "Maksymiuk, Piotr" <[email protected]> wrote:
> Hi > > Good catch! It does correlate, i didn't put in any gpg info for the > channel that didn't have the problem! So now i just delete the gpg > info from those channels, do a zypper ref on those channels and it > should work? Or do i need to resync those channels first, or some > other stuff? > Well, resyncing the channel should not be neccessary. You should delete the GPG information from the affected channels and do a 'zypper refs -f' on your clients. > > > > There is no problem in Spacewalk but zypper. You configured the GPG > > information for your channels and the spacewalk plugin for zypper > > enabled the gpgcheck for the repos coming from spacewalk. If > > gpgcheck is enabled for a repo, zypper expects the repodata to be > > signed by the same key which was used to sign the packages (IIRC). > > So, at this point you are not able to use gpgcheck with > > zypper/spacewalk, because Spacewalk does not sign repository > > metadata. -- Mattias Giese Linux Consultant & Trainer Mail: [email protected] Tel.: +49 (0)160 90447688 B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: PGP signature
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
