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

Bug#434132: marked as done (ITP: php-sasl -- Cyrus SASL extension for PHP)

Your message dated Sun, 23 Sep 2007 14:07:32 +0000
with message-id <E1IZS7Q-0006Cr-OK@ries.debian.org>
and subject line Bug#434132: fixed in php-sasl 0.1.0-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Jack Bates <ms419@freezone.co.uk>

* Package name    : php-sasl
  Version         : 0.1.0
  Upstream Author : Jon Parise <jon@php.net>
* URL             : http://pecl.php.net/package/sasl
* License         : PHP
  Programming Lang: PHP
  Description     : Cyrus SASL extension for PHP

 SASL is the Simple Authentication and Security Layer (as defined by
 RFC 2222).  It provides a system for adding plugable authenticating
 support to connection-based protocols.  The SASL Extension for PHP
 makes the Cyrus SASL library functions available to PHP. It aims to
 provide a 1-to-1 wrapper around the SASL library to provide the
 greatest amount of implementation flexibility.  To that end, it is
 possible to build both a client-side and server-side SASL
 implementation entirely in PHP.

http://cgi.sfu.ca/~jdbates/debian/pool/php-sasl/

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Source: php-sasl
Source-Version: 0.1.0-1

We believe that the bug you reported is fixed in the latest version of
php-sasl, which is due to be installed in the Debian FTP archive:

php-sasl_0.1.0-1.diff.gz
  to pool/main/p/php-sasl/php-sasl_0.1.0-1.diff.gz
php-sasl_0.1.0-1.dsc
  to pool/main/p/php-sasl/php-sasl_0.1.0-1.dsc
php-sasl_0.1.0.orig.tar.gz
  to pool/main/p/php-sasl/php-sasl_0.1.0.orig.tar.gz
php5-sasl_0.1.0-1_i386.deb
  to pool/main/p/php-sasl/php5-sasl_0.1.0-1_i386.deb



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 434132@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jack Bates <ms419@freezone.co.uk> (supplier of updated php-sasl 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@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 29 Dec 2005 16:17:36 -0800
Source: php-sasl
Binary: php5-sasl
Architecture: source i386
Version: 0.1.0-1
Distribution: unstable
Urgency: low
Maintainer: rmgolbeck@debian.org
Changed-By: Jack Bates <ms419@freezone.co.uk>
Description: 
 php5-sasl  - Cyrus SASL extension for PHP 5
Closes: 434132
Changes: 
 php-sasl (0.1.0-1) unstable; urgency=low
 .
   * Initial release
     - Closes: #434132
Files: 
 b6bbc299b5fc6065a112c38a3a0a11c4 606 web optional php-sasl_0.1.0-1.dsc
 8431731cc8a7921a2922af23a57a572f 6435 web optional php-sasl_0.1.0.orig.tar.gz
 09f43e137cbd274a846204ac0201f4f5 6005 web optional php-sasl_0.1.0-1.diff.gz
 9124e470032883e6ecce893e31a4493a 10008 web optional php5-sasl_0.1.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG6zLlNs+6RHiRa4QRAtf0AJ9d2oqT+n5lybBBSige2SU8ye4LiQCfeIta
ShahgOL5wy1D5XkVZl7FHn4=
=fT9b
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: