Mailinglist Archive: opensuse-buildservice (344 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] obs and signing
- From: Marcus Hüwe <suse-tux@xxxxxx>
- Date: Sat, 29 May 2010 02:24:04 +0200
- Message-id: <20100529002403.GB3339@linux>
On 2010-05-28 18:19:47 -0600, Troy Telford wrote:
message indicates that $sign isn't defined in BSConfig.pm.
Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
I've noted a slightly old thread where somebody asked about how to useDid you restart the srcserver after modifying the BSConfig.pm? This
obssigner or obssignd. However, the problem was that there wasn't any
documentation; and there wasn't any discussion on how to set up the signer.
I'd be more than willing to help document the process on the build service
wikis -- if only I knew how to set it up. I can't find any documentation on
how to configure obssigner.
I've uncommented:
our $sign = '/usr/bin/sign';
from BSConfig.pm
I've tried putting the following into my /etc/sign.conf:
### for build service host
server: <my_real_ip_address>
user: obsbuild@xxxxxxx
allowuser: obsrun
#
### for sign server
#allow: <IP of your build service host>
allow: <my_real_ip_address>
#phrases: /root/.phrases
When I start /etc/init.d/obssignd, it starts without throwing an error.
After I start /etc/init.d/obssigner, there is a new logfile created in:
/srv/obs/log/signer.log
This logfile has the following contents:
Name "BSConfig::sign_project" used only once: possible typo at
/usr/lib/obs/server//bs_signer line 96.
starting build service signer
waiting for an event...
When I try to create a key (from a project I've checked out), I get:
~/src/obs/myproject$ osc signkey --create
Server returned an error: HTTP Error 404: Not Found
don't know how to create a key
message indicates that $sign isn't defined in BSConfig.pm.
Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |