Am Freitag, 13. März 2009 08:50:48 schrieb Carsten Hoeger: AFAIK, we do not have an api call for this. Yes, sign daemon was dead for 1 or 2 days, 2 weeks ago. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

I think carsten actually runs his own OBS. I once had the same problem on mine (well, signd did not die, but a package update replaced BSConfig.pm and sign was disabled again afterwards.. I solved it with launching sign manually against all the RPMs using sign -r <rpmfile>. for a in *.rpm; do sign -r $a; done Additionally you'll have to run createrepo and sign it again... to avoid this step (and to avoid simple errors here) I let OBS rebuild one of the smallest leaf packages in my project. Then all the rpms are signed, the new leaf get's automatically signed and then published and createrepo and all signing steps incl. publishing the keyfile happen automatically. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

Am Freitag, 13. März 2009 10:45:33 schrieb Ludwig Nussel: That is a bit late, but we could block entire building (or better accept build results) when signd is configured but not working. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

On Fri, Mar 13, Ludwig Nussel wrote: I just opened a bug: https://bugzilla.novell.com/show_bug.cgi?id=485580 -- With best regards, Carsten Hoeger