Bug#730530: ITP: mockldap -- mock replacement for python-ldap
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: mockldap Version : 0.1.4 Upstream Author : Peter Sagerson * URL : http://bitbucket.org/psagers/mockldap/ * License : BSD Programming Lang: Python Description : mock replacement for python-ldap This project provides a mock replacement for python-ldap. It’s useful for any project that would like to write unit tests against LDAP code without relying on a running LDAP server. .. The goal of mockldap is to provide a mock instance of LDAPObject in response to any call to ldap.initialize. In the general case, you would register return values for all LDAPObject calls that you expect the code under test to make. Your assertions would then verify that the tested code behaved correctly given this set of return values from the LDAP APIs. .. As a convenience, the mock LDAPObject isn’t just a dumb mock object. The typical way to use mockldap is to provide some static directory content and then let LDAPObject generate real return values. This will only work for simple LDAP operations–this obviously isn’t a complete Python LDAP server implementation–but those simple operations tend to cover a lot of cases. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCgAGBQJSlFiTAAoJEGlMre9Rx7W2zhwP/RCxHWp53cP80HHfozo+K34j egHUqt/VfF4i8jXuG63O2zwtzxzw8fq0kLn+kyEMPbkq0By1V8ah2LJMOx3K1vZK RMTweHMYMRi3xZhzw44U0bg2DUOACzgHnJXN5LuCrpmOVaplwk/cOSBKYB1DP4jp Fah/aHvrUpHQDvHZdT9lgtf6ascPx+XAeRXeGalhi4Q0fNZ3OCtdScWSzTSKSTiU mdqrSB/Y5r8zsKkgRbGzvzixn5b4JD18SC1Y6ILwi0q4hp2ezYdvP9qEo1l2k6RF PgfuTy4v+qaHc92TSOtvC5eOkFynB13lNKsrskI7WZ34cRfsxEJOCFbJVAtBjvne IB2K67L2jznQMvjW4ugfJt52o2nEuBjfgRn1gIT7HCQEc3+aCP0C1qUm1BgGlabN zZXqGNLvyyJeWbxQSmt3E5HYfcVBLZnnSDWLrCfuQdl7xFiUOwDlQ+BL+dBSMTRn NpXqM3Cof5akeI2OmJ79MwvusH5x97B4NUu76RfCypjI8juGbeBdl+3Dss5S/jl6 TnBKySZ0s97fOcFdcIDYiqLoJsWaQq8Ovozigd0C7S9nIuZkh/5Nzs0Irdegcp8N wR5u10fdcllLMjI4XUqWXMSAu9nWSv3wOsCgKcYN3FJa8B8+qkNX0dtoMKAJJNxx j4qTJYVVzmcngXrh+L0P =whci -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131126081519.19210.77186.report...@server.home.fladi.at
Re: About access to git.debian.org and the DPMT
[Zygmunt Krynicki, 2013-11-26] > > * "plainbox is a Simple replacement for CheckBox" looks weird to me, > >> it looks better with lower case "s" IMO (see dev. ref. §6.2.2), > >> > > > > I was reading that and I think that description is no longer accurate. I > > will write a better one, that describes the purpose of the project as it > > stands now. > > > > > > Rewrote descriptions entirely please use lowercase "t" and remove the dot from the end of short description > > * plainbox manpage is missing, > >> > > > > Is it mandatory to have one? I recall reading about not symlinking to > > undocumented.7. Plainbox does not currently have a man page but instead has > > built-in --help. I guess I'm asking about the minimum required man page > > that could be worked upon later. > > > > No change yet it's not mandatory but help2man is so easy to use... (and even if you decide to not write/generate one, let lintian complain about it) > > How should I inject that into SVN? Will I get commit access to the > > collaborative repository? you already have commit access, https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Work_With_The_Packages > Before I sort that out I've updated the repository on github. > Please have a look and tell me if I missed anything. please move -doc package to "extra" priority; sorry I forgot to mention it in my last mail -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131126084155.gj3...@sts0.p1otr.com
Re: About access to git.debian.org and the DPMT
Hello again. I've prepared 0.4~b1-2 with the following changes: (the branch is still on github at https://github.com/zyga/debian.plainbox On Tue, Nov 26, 2013 at 9:41 AM, Piotr Ożarowski wrote: > [Zygmunt Krynicki, 2013-11-26] > > > * "plainbox is a Simple replacement for CheckBox" looks weird to me, > > >> it looks better with lower case "s" IMO (see dev. ref. §6.2.2), > > >> > > > > > > I was reading that and I think that description is no longer accurate. > I > > > will write a better one, that describes the purpose of the project as > it > > > stands now. > > > > > > > > > > Rewrote descriptions entirely > > please use lowercase "t" and remove the dot from the end of short > description > > Corrected > > > * plainbox manpage is missing, > > >> > > > > > > Is it mandatory to have one? I recall reading about not symlinking to > > > undocumented.7. Plainbox does not currently have a man page but > instead has > > > built-in --help. I guess I'm asking about the minimum required man page > > > that could be worked upon later. > > > > > > > No change yet > > it's not mandatory but help2man is so easy to use... > (and even if you decide to not write/generate one, let lintian complain > about it) > I now auto-generate both man pages at build time. I was unsure if this is the right avenue (it won't affect cross building as this is an -all package but perhaps there are some guidelines on how to use help2man). I'll work on getting upstream man pages generated with sphinx, which should fix that issue in a couple of releases. > > > > How should I inject that into SVN? Will I get commit access to the > > > collaborative repository? > > you already have commit access, > > https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Work_With_The_Packages > > I'll inject the -2 version shortly, thanks. > > > Before I sort that out I've updated the repository on github. > > Please have a look and tell me if I missed anything. > > please move -doc package to "extra" priority; sorry I forgot to mention > it in my last mail > Done I also made sure to fix the vendorized packages. Those are now patched away, totaling in three patches in debian/patches. Two will be dropped by the time beta2 is released. The remaining one has to be carried for as long as python3.2 is supported by the upstream plainbox project but should not change so won't be a burden to maintain. Thanks ZK
please review and sponsor the plainbox package
Hello. I've just successfully injected plainbox into the python-modules directory [1].I've filed an ITP bug and I'll shortly correct the changelog to reference the bug number. You can find the git source corresponding to the package that was uploaded on [2]. I'm also available in #debian-python to answer any questions that you may have. [1] http://anonscm.debian.org/viewvc/python-modules/packages/plainbox/trunk/debian/ [2] https://github.com/zyga/debian.plainbox Best regards Zygmunt Krynicki
please review and sponsor the plainbox package
Hello. I've just successfully injected plainbox into the python-modules directory [1].I've filed an ITP bug and I'll shortly correct the changelog to reference the bug number. You can find the git source corresponding to the package that was uploaded on [2]. I'm also available in #debian-python to answer any questions that you may have. [1] http://anonscm.debian.org/viewvc/python-modules/packages/plainbox/trunk/debian/ [2] https://github.com/zyga/debian.plainbox Best regards Zygmunt Krynicki -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajn_i49pwk1qbezsvrmk+f2bko5v5yma6b+k3opnte9vxp6...@mail.gmail.com
Review of Django-ldapdb package needed
Hi. I Intend To Package django-ldapdb [0] but I'm quite new to Python packaging (incl. Django apps packaging ;). I intend to have it maintained in the team SVN but am still waiting for a kind sould to add obergix to the alioth project ;) In the meantime, I've prepared a git-buildpackage repo in [1] that holds my source package, cloned off the upstream github repo. I'd welcome any comments or suggestions of more experienced team members regarding it. For the records, this could be a needed dependency of the userdir-ldap Django rewrite [2]. I'm a bit unsure how to deal with the upstream provided examples/ app, so tried to add it into /usr/share/doc/python-django-ldapdb/examples/examples/ which then requires a lintian override... Thanks in advance. Best regards, [0] http://bugs.debian.org/730548 [1] http://anonscm.debian.org/gitweb/?p=users/obergix/django-ldapdb.git [2] https://wiki.debian.org/DSA/UserdirLdapRewrite -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) pgpPKCq5mL9Ze.pgp Description: PGP signature
Re: About access to git.debian.org and the DPMT
debian/copyright is still not complete - vendor files are still in the tarball so you have to mention these files in debian/copyright also: $ ./debian/rules get-orig-source uscan --noconf --force-download --download-current-version --destdir=. plainbox: Version (0.4~b1) available on remote site: http://pypi.python.org/packages/source/p/plainbox/plainbox-0.4b1.tar.gz (local version is 0.4~b1) plainbox: Successfully downloaded updated package plainbox-0.4b1.tar.gz and symlinked plainbox_0.4~b1.orig.tar.gz to it dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: applying 01-add-main-module dpkg-source: info: applying 02-executable-laucher1 can't find file to patch at input line 26 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Description: Make plainbox.impl.secure.launcher1 executable via `python -m` | This patch adds a simple if __name__ == '__main__': main() statement | a the end of plainbox.impl.secure.launcher1 module so that it can be | executed directly with `python3 -m ...`. This is useful to generate | the plainbox-trusted-launcher-1.1 manual page with help2man | |Author: Zygmunt Krynicki |Bug: https://bugs.launchpad.net/checkbox/+bug/1255085 |Last-Update: 2013-11-26 |Forwarded: yes |--- |The information above should follow the Patch Tagging Guidelines, please |checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here |are templates for supplementary fields that you might want to add: | |Origin: , |Bug: |Bug-Debian: http://bugs.debian.org/ |Bug-Ubuntu: https://launchpad.net/bugs/ |Forwarded: |Reviewed-By: |Last-Update: | |--- plainbox-0.4~b1.orig/plainbox/impl/secure/launcher1.py |+++ plainbox-0.4~b1/plainbox/impl/secure/launcher1.py -- No file to patch. Skipping patch. 1 out of 1 hunk ignored dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch '02-executable-laucher1' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/02-executable-laucher1/ --reject-file=- < trunk/debian/patches/02-executable-laucher1 gave error exit status 1 > I'll inject the -2 version shortly, thanks. see Q5 from document linked in my signature -- http://people.debian.org/~piotr/sponsor signature.asc Description: Digital signature
