While smart is ok as a temporary work around, it still would be good to
see some sort of approach here that works better. ...
I note its not possible to build an 11.1 rpm from an 11.2 .src using
"rpmbuild --rebuild file.src.rpm" because one gets the key error.
Lee
aka oldcpu
On 03/19/2011 06:17 PM, oldcpu wrote:
Ok Thanks.
Until this is sorted : I setup the Smart Package manager with the
Evergreen-11.1 repositories, and briefly set the rpm-signature check to
false in Smart Packager manager, and easily updated and installed the
latest Packman packages for Evergreen-11.1.
Smart always has served me well as a back up to YaST/zypper.
Many thanks to the Packman packagers for their Evergreen support.
Lee
aka oldcpu
On 03/19/2011 02:40 PM, Joachim Schrod wrote:
oldcpu wrote:
Was this fixed for Evergreen in Packman?
I'm still getting (as of this morning) errors when trying to install
from Packman Evergreen repository via YaST about a bad key. I received
PM in the forum from others with same problem.
Yours is a different problem.
It seems that 11.1's rpm cannot handle the current Packman signing
key. That's an rpm issue, not a zypper issue. It was confirmed here
a few days ago; look at messages with the subject "RPM problem with
packet signatures (not zypper and repomd.xml!)"
Maybe that's because it's a 4096-bit key, but the root cause has
not been established yet.
Since there is no known way to turn off rpm gpg signature check in
zypper, Packman repositories cannot be used via zypper / yast for
11.1/Evergreen installations at the time.
Joachim
_______________________________________________
Packman mailing list
[email protected]
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
_______________________________________________
Packman mailing list
[email protected]
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
