Custom Query (894 matches)

Because we are running a bcfg2 client on our bcfg2 server I want to use different config files for the client and the server, so I use the -C parameter for bcfg2-server. But the Snapshots-Plugin has /etc/bcfg2.conf hardcoded.

In Pkgmgr/ I have files generated from the create-debian-pkglist.py. This is the source for an installed package defined in a bundle. I add the sources for different Debian releases (etch/backports/etc) to apt sources via Bcfg so that I can "pin" newer versions.

e.g. <PackageList? priority="99" type="deb">

<Group name="grpname">

<Package name="pkgname" version="0.1.1-1" type="deb"/>

</Group>

</PackageList?>

Problem:

If I add a new PackList? for a group and a Package specification to effectively "upgrade" the package I get the message on the client:

Incomplete information for entry Package:packagename; cannot verify

... due to absense of version attribute(s)

If I restart the bcfg2-server and rerun on the client the "upgrade" succeeds as expected.

prune option in POSIX.py for Directory elements in Rules does not seem to extend to files created in SGenshi.

In Rules/apache.xml I have:

<Directory name='/etc/apache2/sites-enabled'

prune='true' owner='root' group='root' perms='755'/>

<SymLink? name='/etc/apache2/sites-enabled/000-default'

to='/etc/apache2/sites-available/default'/>

In SGenshi/projects.xml I have:

<BoundSymLink?

name="/etc/apache2/sites-enabled/${name}.conf" to="${basedir}/${name}/apache/conf/${name}.conf"/>

On the first run with out anything in place I get all symlinks in /etc/apache2/sites-enabled installed. On the second run the prune option removes all but the 000-default symlink. On the third run the templated symlinks come back and thus a loop of removal and reinstallation.

I expect the prune option to be aware of an entry from any plugin.

This is when using an svn checkout from 24th Sept.