On Tue, 2007-05-15 at 10:00 +0200, Marc Fargas wrote: > When you run bcfg2-admin init, one of the things it does is create a SSL > certificate. Without this certificate you **can't** use bcfg2. The matter is > that bcfg2 needs the package openssl to be installed to create the > certificate.
i'll look in to the problem, but i would assume that it's resolved in the new upstream versions (yes, there are several by now). > Maybe this bug should be Sverity: important, as bcfg2-server is unusable > without such certificate, but I'll leave as normal so you can decide ;) I'm a bit torn between important and normal too. It doesn't affect the core functionality that much, but still it's important to anyone creating a new repository. > PS: The affected box does not have reportbug, but it is an Etch ;) at the moment there is just one version of bcfg2 in debian (i've been a bit too busy elsewhere to update the package to match the upstream). You might want to look at the upstream package anyway, there are quite a few changes since the debian package was frozen. Things like importing configuration from clients to the repository through the bcfg2 client itself. -- Sami Haahtinen <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
