Custom Query (894 matches)


Show under each result:

Results (58 - 60 of 894)

Ticket Owner Reporter Resolution Summary
#927 desai Thomas Ackermann <[email protected]…> fixed python-lxml dependency in client RPMS made by redhat make

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 ?

#1147 desai DongInn Kim <[email protected]…> fixed pysvn.Client.update function is not available in

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/", line 127, in Installsvn
        client = pysvn.Client.update(entry.get('name'), recurse=True)
    AttributeError: 'function' object has no attribute 'update'

#529 desai [email protected] fixed public groups combined with dynamic groups implicitly makes probed groups public

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'

Note: See TracQuery for help on using queries.