Bug#771503: Remove package web2ldap

[Michael Ströder]

Marc, I hope you understand that this is not meant as personal offense.

It's just facing the fact that it's too hard to keep up for the maintainer in
the current situation. Ok?

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#771504: Remove package python-ldap

[Michael Ströder]

Package: python-ldap
Version: 2.4.10-1

https://tracker.debian.org/pkg/python-ldap

I understand that it's much work to maintain such a package and that Debian
maintainers sometimes cannot keep up with development.

But for me as upstream author it seems better not to have a Debian package at
all than having to deal with an outdated package which contains bugs already
fixed long ago.

=> Please remove package python-ldap because it's outdated and seems
unmaintained.

Ciao, Michael.






smime.p7s
Description: S/MIME Cryptographic Signature

Bug#771505: Remove package python-weblib

[Michael Ströder]

Package: python-weblib
Version: 1.3.9-1

https://tracker.debian.org/pkg/python-weblib

I understand that it's much work to maintain such a package and that Debian
maintainers sometimes cannot keep up with development.

But for me as upstream author it seems better not to have a Debian package at
all than having to deal with an outdated package which contains bugs already
fixed long ago.

=> Please remove package python-weblib because it's outdated and seems
unmaintained.

Ciao, Michael.





smime.p7s
Description: S/MIME Cryptographic Signature

Bug#771503: Remove package web2ldap

[Michael Ströder]

Package: web2ldap
Version: 1.1.43~dfsg-1

https://tracker.debian.org/pkg/web2ldap

I understand that it's much work to maintain such a package and that Debian
maintainers sometimes cannot keep up with development.

But for me as upstream author it seems better not to have a Debian package at
all than having to deal with an outdated package which contains bugs already
fixed long ago.

=> Please remove package web2ldap because it's outdated and seems unmaintained.

Ciao, Michael.




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#742487: Update of python-ldap to upstream version 2.4.15

[Michael Ströder]

Philipp Hahn wrote:
> retitle 742487 Update of python-ldap to upstream version 2.4.16
> tag 742487 patch

Please note that 2.4.18 was released and should be considered for package 
update:

http://pypi.python.org/pypi/python-ldap/2.4.18

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#742487: Update of python-ldap to upstream version 2.4.15

[Michael Ströder]

Philipp Hahn wrote:
> The attached version contains my fix for that problem, which I sent
> upstream and which is already committed to the maintainers CVS
> repository:
> 

I prefer not having to bear in mind backport fixes in distri packages.

Therefore I've release 2.4.16. I would appreciate if you would package that
(after locally testing the release).

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#742487: Update of python-ldap to upstream version 2.4.15

[Michael Ströder]

Package: python-ldap
Version: 2.4.10-1

Please upgrade the package python-ldap to new upstream version 2.4.15. It
contains important fixes for ReconnectLDAPObject and some new features which
are useful for application programmers. AFAICS is does not break any existing
applications.




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#742360: python-ldap: please provide a python3 version

[Michael Ströder]

Sebastian Humenda wrote:
> Package: python-ldap
> Version: 2.4.10-1
> Severity: wishlist
> Tags: upstream
> 
> Please provide a package for python3-ldap, as available e.g. on
> 
> https://pypi.python.org/pypi/python3-ldap

Please note that both module packages have a completely separate code base.
So filing this as a bug against existing package "python-ldap" will likely
lead to confusion.

=> This bug against package python-ldap should be declined.

@Sebastian: You should file another bug report with a request like:
"Create a new package for python3-ldap".

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#742357: Update of python-weblib to upstream version 1.3.11

[Michael Ströder]

Package: python-weblib
Version: 1.3.9-1

Please upgrade the package python-weblib to new upstream version 1.3.11. It
contains only minimal changes but important fixes for two Unicode issues.

Please consider to do the package renaming requested in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295380



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#704939: python-ldap: ldaps connections fail

[Michael Ströder]

Gareth Walters (2K Australia) wrote:
> Neither system(s) have any extra ca certs trusted. The code sets  the ldap
> options to disable cert verification.

As this is bad practice anyway:
Could you please test with explictly the trusted CA certs?

Also note that if you really want to disable all libldap config processing you
would have to set the env var LDAPNOINIT=1.

Add this line to the beginning of your Python code:

os.environ['LDAPNOINIT']='1'

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#704939: python-ldap: ldaps connections fail

[Michael Ströder]

Is the set of trusted CA certs exactly the same on both systems?

Note that on Debian libldap is linked against GnuTLS. In this case the
ldap.SERVER_DOWN exception does not contain a useful diagnostic message.
When linking libldap against OpenSSL a message generated by OpenSSL is
returned by libldap as diagnostic message.

Ciao, Michael.

Gareth Walters (2K Australia) wrote:
> 
> Package: python-ldap
> Version: 2.4.10-1
> Severity: important
> 
> Dear Maintainer,
> While trying to get a python scrip tof mine to work in Wheezy (have it
> running in Squeeze and several other OSs)
> I come across this error when using ldaps://
> 
> ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
> The server is up and the same script is working on the Squeeze machine.
> 
> Its talking to Windows AD 2008 R2
> 
> the minimal code to reproduce is;
> import ldap
> myldap=ldap.initialize("ldaps://xx.xx.xx.100")
> myldap.bind_s('bindDN','bindPASS')
> 
> but this works
> import ldap
> myldap=ldap.initialize("ldap://xx.xx.xx.100";)
> myldap.bind_s('bindDN','bindPASS')
> 
> Does not even get far enough to give a certificate error as would
> notmally happen without allow unverified/trusted SSL cert.
> 
> 
> Output when setting ldap debug on;
> 
> ldap_create
> ldap_url_parse_ext(ldaps://xx.xx.xx.105)
> ldap_url_parse_ext(ldaps://xx.xx.xx.100)
> ldap_sasl_bind
> ldap_send_initial_request
> ldap_new_connection 1 1 0
> ldap_int_open_connection
> ldap_connect_to_host: TCP xx.xx.xx.100:636
> ldap_new_socket: 3
> ldap_prepare_socket: 3
> ldap_connect_to_host: Trying xx.xx.xx.100:636
> ldap_pvt_connect: fd: 3 tm: -1 async: 0
> ldap_int_open_connection
> ldap_connect_to_host: TCP xx.xx.xx.105:636
> ldap_new_socket: 5
> ldap_prepare_socket: 5
> ldap_connect_to_host: Trying xx.xx.xx.105:636
> ldap_pvt_connect: fd: 5 tm: -1 async: 0
> ldap_err2string
> Traceback (most recent call last):
>   File "./adauth.py", line 71, in 
>  
> myldap.bind_s(config.get('ldap','bindDN'),config.get('ldap','bindPASS'))
>   File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 222,
> in bind_s
> msgid = self.bind(who,cred,method)
>   File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 216,
> in bind
> return self.simple_bind(who,cred)
>   File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 201,
> in simple_bind
> return
> self._ldap_call(self._l.simple_bind,who,cred,RequestControlTuples(server
> ctrls),RequestControlTuples(clientctrls))
>   File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 99,
> in _ldap_call
> result = func(*args,**kwargs)
> ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
> 
> 
> 
> -- System Information:
> Debian Release: 7.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages python-ldap depends on:
> ii  libc6  2.13-38
> ii  libldap-2.4-2  2.4.31-1
> ii  python 2.7.3-4
> ii  python2.7  2.7.3-6
> 
> python-ldap recommends no packages.
> 
> Versions of packages python-ldap suggests:
> pn  python-ldap-doc  
> pn  python-pyasn1
> 
> -- no debconf information



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#687242: web2ldap: should depend on python-weblib >= 1.3.8

[Michael Ströder]

Marc Haber wrote:
> On Tue, Sep 11, 2012 at 08:55:20AM +0300, Paul Totterman wrote:
>> web2ldap needs python-weblib 1.3.8 or later.
> 
> I disagree on that, I am using web2ldap on Debian squeeze.
> 
> Michael, what do you say?

1.3.8+ is definitely required. Otherwise exceptions are raised.

See also http://www.web2ldap.de/install.html#Prerequisites

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#600782: #600782 - pyca is NOT compatible with the default python version 2.6

[Michael Ströder]

Evgeni Golov wrote:
>> Maintainer should modify the hash-bang line in python scripts from 
>> `#!/usr/bin/python' to `#!/usr/bin/python2.5'
>> because some DeprecationWarning appeared and said md5, sha, mimify modules 
>> should be replaced.
> 
> I think your report is a bit wrong.
> 
> Yes, running pyca does produce DeprecationWarnings when run with
> python2.6, but it seems not to disturb the workflow of pyca.

Yes. A DeprecationWarning in Python is just for informing the developer about
future removal of a module/function.

> md5 and sha are deprecated since 2.5 in favour of hashlib
> mimify is deprecated since 2.3 in favour of email

Modules md5 and sha are still available even in Python 2.7 (checked docs right
now). So I currently see no urgent need to do anything about this in the
upstream source.

> PS: I plan to downgrade this to wishlist and retitle to "pyca should be
> ported to newer python libs" - any objections? Lars?

But in general please note the section *Project status* on http://www.pyca.de/

At the moment I'm not even using pyCA myself anymore.

Ciao, Michael.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#295380: should be named python-pyweblib

[Michael Ströder]

Being the author of pyweblib I wholeheartly agree that this package
should be renamed to python-pyweblib. And while you're at it I'd
appreciate if you upgrade to version 1.3.5.

Ciao, Michael.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]