Your message dated Sun, 13 Sep 2009 16:51:45 +0200
with message-id <[email protected]>
and subject line fixed in 0.5.15-1
has caused the Debian Bug report #542878,
regarding python-pycryptopp: new upstream release available
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 [email protected]
immediately.)
--
542878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-pycryptopp
Version: 0.5.14-1
Severity: normal
There's a new upstream release available (pycryptopp-0.5.15), at:
http://pypi.python.org/pypi/pycryptopp/0.5.15
(I'm eager to see this version get into debian, because I'm trying to get
Tahoe into debian, and Tahoe requires >=0.5.15).
thanks,
-Brian
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-pycryptopp depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libcrypto++8 5.6.0-2 General purpose cryptographic libr
ii libgcc1 1:4.4.1-2 GCC support library
ii libstdc++6 4.4.1-2 The GNU Standard C++ Library v3
ii python 2.5.4-2 An interactive high-level object-o
ii python-support 1.0.3 automated rebuilding support for P
python-pycryptopp recommends no packages.
python-pycryptopp suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pycryptopp
Source-Version: 0.5.15-1
I forgot to close this bug in the changelog
signature.asc
Description: Digital signature
--- End Message ---
