Your message dated Thu, 05 Jan 2012 14:21:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#641526: python3.2: new upstream version / big delay on
3.2 in testing
has caused the Debian Bug report #641526,
regarding python3.2: new upstream version / big delay on 3.2 in testing
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.)
--
641526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641526
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3.2
Version: 3.2.1~rc1-1
Severity: wishlist
Hi there,
as you would know, version 3.2 final is released last week.
Is there any update available on when 3.2 final will be packaged, and
more importantly, when the clash with python3-profiler will be
resolved so that python3.2 can be available in testing?
Thanks,
Stephen.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-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 python3.2 depends on:
ii libbz2-1.0 1.0.5-6
ii libc6 2.13-18
ii libdb5.1 5.1.25-11
ii libncursesw5 5.9-1
ii libreadline6 6.2-4
ii libsqlite3-0 3.7.7-2
ii mime-support 3.51-1
ii python3.2-minimal 3.2.1~rc1-1
python3.2 recommends no packages.
Versions of packages python3.2 suggests:
pn binutils 2.21.52.20110606-2
pn python3.2-doc 3.2.1~rc1-1
pn python3.2-profiler <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.2.2-1
--- End Message ---
