Package: dass-tools Version: 1.0.1267-1 Architecture: all Maintainer: Joerg Steffens <joerg.steffens@dass-it.de> Installed-Size: 34 Depends: rsync, sed Recommends: lftp, unzip, xmlstarlet Filename: ./all/dass-tools_1.0.1267-1_all.deb Size: 5938 MD5sum: 8d3e352cb22f37814e69dd2514ba1972 SHA1: 9c7308082a8a2bf4ae9d9a91226ff6cdddd32221 SHA256: a434c4a3bb26bd591146ebeb6663acd82eff6ca927708e3b91c94f83a6441f83 Section: python Priority: optional Description: dass-tools is a collections of small utilities Package: dasscm Version: 1.2.1270-1 Architecture: amd64 Maintainer: Jörg Steffens <joerg.steffens@dass-it.de> Installed-Size: 80 Depends: subversion, perl Filename: ./amd64/dasscm_1.2.1270-1_amd64.deb Size: 14406 MD5sum: f1764c2fb3914f4e339e7960753e38c8 SHA1: 361e93b72f7a84e5a2919855dd5dc3e3892feb41 SHA256: a15deb9f4382b34b53d197ce168106984e1121fa2110b61698a60c289a15fe0b Section: misc Priority: optional Description: dass configuration management tool tools for handling configuration files with subversion Package: dasscm Version: 1.2.1270-1 Architecture: i386 Maintainer: Jörg Steffens <joerg.steffens@dass-it.de> Installed-Size: 80 Depends: subversion, perl Filename: ./i386/dasscm_1.2.1270-1_i386.deb Size: 14424 MD5sum: 435723c677697e03a0d644d434aa5874 SHA1: 74491c8d2e1ad84e93010d727006088671326e46 SHA256: b0a20eb305e8021c3201e98818c42c355d2729db0de9743016da670b279690f3 Section: misc Priority: optional Description: dass configuration management tool tools for handling configuration files with subversion Package: dassldapsync Version: 2.0.1272-1 Architecture: all Maintainer: Sebastian Lederer <slederer@dass-it.de> Installed-Size: 36 Depends: python (>= 2.6), python-ldap Filename: ./all/dassldapsync_2.0.1272-1_all.deb Size: 7432 MD5sum: 2c47e633ae19c2fc9a96631485c2f39b SHA1: ade69ccb6acb191e45cc632ac1eeea2e00d2d611 SHA256: 986f921815733b35656cc508fc8659c9c0f90ee722896f409cb7dabd9fac5bd4 Section: contrib/admin Priority: optional Description: A script for synchronizing two LDAP trees This script compares two different LDAP subtrees and makes the according changes on objects in the destination subtree. Missing objects are created, extraneous objects are deleted. The two subtrees can reside on two different LDAP servers. It is also possible to use an LDIF file as the source subtree.