Custom Query (894 matches)

made by: svn checkout on trunk cd redhat make

rpm -qpR bcfg2-1.1.0-0.0rc4r.noarch.rpm /bin/sh /bin/sh /bin/sh /bin/sh /sbin/chkconfig /sbin/chkconfig /sbin/service /sbin/service /usr/bin/python config(bcfg2) = 1.1.0-0.0rc4r initscripts python(abi) = 2.4 python-lxml >= 0.9 rpmlib(CompressedFileNames?) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix?) <= 4.0-1

whereas python-lxml wouldn't be needed in here anoymore i guess ?

It seems that pysvn.Client.update fails to run because it is not avaiabled in pysvn or because the way to call "update" is not correct?

    Failed to update repository
    Traceback (most recent call last):
      File "/usr/lib/python2.6/site-packages/Bcfg2-1.2.3-py2.6.egg/Bcfg2/Client/Tools/VCS.py", line 127, in Installsvn
        client = pysvn.Client.update(entry.get('name'), recurse=True)
    AttributeError: 'function' object has no attribute 'update'

There is unexpected behavior if you combine a public group with dynamic, probed groups - the probed groups are effectively now public. I believe dynamic group membership should be suppressed when a public group is specified.

1. create a public group
2. create a probe that returns group membership (e.g., 'group:gutsy')
3. connect from a new client, specifying the public group w/ 'bcfg2 -p <groupname>'; this client should also be detected by the dynamic groups probe

You'll see the entries for both the specified public group are used, as well as the dynamic group. This could be exploited by a malicious client by forcing the probe to return the configuration info for a certain group, e.g., - 'group:kdc'