[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#730548: marked as done (ITP: python-django-ldapdb -- An LDAP database backend for Django)



Your message dated Sat, 28 Dec 2013 05:00:08 +0000
with message-id <E1Vwm0O-0000pm-BN@franck.debian.org>
and subject line Bug#730548: fixed in django-ldapdb 0.2.0-1
has caused the Debian Bug report #730548,
regarding ITP: python-django-ldapdb -- An LDAP database backend for Django
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
730548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730548
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Olivier Berger <obergix@debian.org>

* Package name    : python-django-ldapdb
  Version         : 0.2.0
  Upstream Author : Jeremy Laine <jeremy.laine@m4x.org>
* URL             : https://github.com/jlaine/django-ldapdb
* License         : BSD
  Programming Lang: Python
  Description     : An LDAP database backend for Django

django-ldapdb - support for django models over LDAP

--- End Message ---
--- Begin Message ---
Source: django-ldapdb
Source-Version: 0.2.0-1

We believe that the bug you reported is fixed in the latest version of
django-ldapdb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 730548@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olivier Berger <obergix@debian.org> (supplier of updated django-ldapdb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 04 Dec 2013 14:08:21 +0100
Source: django-ldapdb
Binary: python-django-ldapdb
Architecture: source all
Version: 0.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Olivier Berger <obergix@debian.org>
Changed-By: Olivier Berger <obergix@debian.org>
Description: 
 python-django-ldapdb - LDAP database backend for Django
Closes: 730548
Changes: 
 django-ldapdb (0.2.0-1) unstable; urgency=low
 .
   * Initial packaging (Closes: #730548).
Checksums-Sha1: 
 3516d0a3d5f3e9d8181968d35952ae4bbc7b9c21 2143 django-ldapdb_0.2.0-1.dsc
 328d08ec42c6d4ea523753e078d5431100e98eec 15328 django-ldapdb_0.2.0.orig.tar.gz
 e7714a2b8c97e1a3fdae59b2b5b4b8b71d8c0333 2681 django-ldapdb_0.2.0-1.debian.tar.gz
 cc551301b3f237f9d809c73f515b98ace81220d1 17064 python-django-ldapdb_0.2.0-1_all.deb
Checksums-Sha256: 
 f7e6d81136a90928d30444fc1f072602d11a9f79b661b827ee055f641455d8db 2143 django-ldapdb_0.2.0-1.dsc
 958a9229b2b53b2e763791941f677c690ba4b5e2c8015dcfb61143e1b9b6d337 15328 django-ldapdb_0.2.0.orig.tar.gz
 3f6e5fa312aa66eb7d291593beeb7e53e0b2a9cace3fa8a2a246add8f339031f 2681 django-ldapdb_0.2.0-1.debian.tar.gz
 2329d2f8602d63ad0bde4ddc066752d3c5eef6e0c3b5d605e7b2a107798a2ccb 17064 python-django-ldapdb_0.2.0-1_all.deb
Files: 
 a3e76ce62485fe784f11a2c3953a5ace 2143 python optional django-ldapdb_0.2.0-1.dsc
 7200cd78b1116195053b2befb5b4af99 15328 python optional django-ldapdb_0.2.0.orig.tar.gz
 4a7274cb2ffbde0f5f94db512d474190 2681 python optional django-ldapdb_0.2.0-1.debian.tar.gz
 553ac361f7a71d14a76fca22deb9dab8 17064 python optional python-django-ldapdb_0.2.0-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBCAAGBQJSvZoGAAoJEOlB3tp8W7alDEoP/AyibtOJpyjh3w0jv1nWjI+Y
Ig+rZsWl+CW6jsvxgzZ5K2/AjmDTQVMozudKhhrs8b4oWt2kGamjIyeF4dgL1cKW
f+W8xKz0muEc28jt8bvXMPEOQ/MHsKI9Xt/DJ3AcKckRoQQysRZDfvoKrStdDpsj
EnXLkgoH7G9q0QThMsHWZ6o3n9Y9xW+GMRjLDRnt4lZOCGRgxW2afUx2kVBkVk2s
6nibPPGc9zUoUzKahT3gBffCVIBPYHP5qiZBxzTvYzu+NXjjHRSAX60IXLoR/4Vi
+qYOiXUSOx7FG7Meekq7zvvBu3pYpXGUEVgaCjeyU3XJQj3CkgmfET24MnSTBtca
Jw9jOv9jM9X2MBq4jrPc7BUKZdfl7Y1ffftaugnlR5zLuqcGeoUeNMqSg+j+8CNy
NZ68C/NPNgigmiu753+Gu+0r6ghU92Ay55nCmYDnHpOv/5euHyHbWui0sm0aPvA7
XzgnMULrYEifJ7Uy6K0omKGxWyFSerhzQjBs2T0VyYwPUeMSs33NKzTs2rEtfI5b
hCmI5PpGl+OzUIk4bzeW5kQgLFajWbmZcpgSghu8DaUTToDE401lG1Tjb+M5ghZT
p8t5EwqRl4P2I+vHGkmPJgWNLqa7A5ZjsBN5oQZyRCJMyHBXT81CXqisURG4iorc
PfetUA1lerBfBkvIMzBw
=MOKg
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: