Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: xboxer21 on October 01, 2005, 01:10:47 AM

Title: SME 7b Yum Update Problems
Post by: xboxer21 on October 01, 2005, 01:10:47 AM

Hello,
I have SME 7.0 beta installed, I was trying to do a Yum update, and I get the following errors after Updates have been downloaded.
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 1e9c9308
public key not available for smeserver-support-1.4.6-02.noarch.rpm

Any Suggestions

Thanks
Bk

Title: SME 7b Yum Update Problems
Post by: hanscees on October 01, 2005, 01:29:07 AM

have a look in this forum at sticky one. This is a known problem.

hc

Title: Thanks hanscees
Post by: xboxer21 on October 01, 2005, 02:19:21 AM

Thanks Hanscees,
I went thru the sticky & found the solution..

yum update smeserver-yum
/etc/e-smith/events/actions/yum-import-keys
/sbin/e-smith/db yum_repositories setprop smeos GPGCheck yes
/sbin/e-smith/expand-template /etc/yum.conf
yum -y update

Title: SME 7b Yum Update Problems
Post by: ejfowler on October 07, 2005, 01:31:12 PM

This didn't quite work for me. I had to disable gpg check for the smeos repository in yum.conf before I could update smeserver-yum. Then I followed the instructions in the previous post, and it worked OK. One issue ramains; all of the other repos still have their gpg-check set to zero. Exposing your server to unsigned packages is a bad idea, I hope the devs fix this before the final release.

Title: SME 7b Yum Update Problems
Post by: gordonr on October 07, 2005, 02:05:09 PM

Quote from: "ejfowler"

This didn't quite work for me. I had to disable gpg check for the smeos repository in yum.conf before I could update smeserver-yum.

That was noted on the KnownIssues page.

Quote from: "ejfowler"

Then I followed the instructions in the previous post, and it worked OK. One issue ramains; all of the other repos still have their gpg-check set to zero. Exposing your server to unsigned packages is a bad idea, I hope the devs fix this before the final release.

Please, please, please report any issues in the bug tracker. Please. I have fixed this, but please don't assume that we will magically find things in the forum threads.

Thanks,

Gordon

Title: SME 7b Yum Update Problems
Post by: xboxer21 on October 08, 2005, 07:11:59 AM

Quote from: "ejfowler"

This didn't quite work for me. I had to disable gpg check for the smeos repository in yum.conf before I could update smeserver-yum. Then I followed the instructions in the previous post, and it worked OK. One issue ramains; all of the other repos still have their gpg-check set to zero. Exposing your server to unsigned packages is a bad idea, I hope the devs fix this before the final release.

Hi ejfowler,
Could you please let me know how you disabled gpg check for the smeos repository in yum.conf before you could update smeserver-yum. I re-installed SME7.0 and I'm having trouble duplicating what i did last time. I know for a fact that I tried a few things before I did what I have mentioned earlier.
Thanks

Title: SME 7b Yum Update Problems
Post by: gordonr on October 08, 2005, 09:37:47 AM

Quote from: "xboxer21"

Hi ejfowler,
Could you please let me know how you disabled gpg check for the smeos repository in yum.conf before you could update smeserver-yum. I re-installed SME7.0 and I'm having trouble duplicating what i did last time. I know for a fact that I tried a few things before I did what I have mentioned earlier.
Thanks

http://smeserver.sourceforge.net/sme70/KnownIssues

Title: Thanks!
Post by: xboxer21 on October 08, 2005, 05:21:52 PM

http://smeserver.sourceforge.net/sme70/KnownIssues[/quote]

Thanks gordonr for your help..

Title: Re: Thanks!
Post by: gordonr on October 08, 2005, 11:19:28 PM

Quote from: "xboxer21"

http://smeserver.sourceforge.net/sme70/KnownIssues

Thanks gordonr for your help..[/quote]

No worries. Please keep an eye on the KnownIssues page and the bug tracker - see the sticky thread at the top of this forum. We keep the KnownIssues and bug tracker up-to-date and it's far more efficient for everyone if there is one place to check.