Your message dated Sat, 19 Jul 2008 18:28:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: reportbug: python modules not recompiled after python
upgrade
has caused the Debian Bug report #476676,
regarding reportbug: python modules not recompiled after python upgrade
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.)
--
476676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476676
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: reportbug
Version: 3.39-0.1
Severity: normal
I've upgraded python from 2.4 to 2.5, and it seems the reportbug modules
are the only ones that were not recompiled in that progress:
,----
| % file $(locate .pyc) | grep '2\.4'
| /usr/share/reportbug/checkbuildd.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/checkversions.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/debianbts.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/hiermatch.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/rbtempfile.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug_exceptions.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug_submit.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug_ui_newt.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug_ui_text.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/reportbug_ui_urwid.pyc: python 2.4 byte-compiled
| /usr/share/reportbug/urlutils.pyc: python 2.4 byte-compiled
`----
In fact, I've purged python 2.4. While reportbug obviously works
nonetheless, this might be a potential problem that could probably be
avoided by depending on python-support and shipping a file
/usr/share/python-support/reportbug.dirs with "/usr/share/reportbug" as
content.
Disclaimer: I'm a Python layman.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.4
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.11 Advanced front-end for dpkg
ii python 2.5.2-1 An interactive high-level object-o
ii python-central 0.6.3 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
thanks for the report! The behavior you reported is not a bug in
reportbug itself but in some of the tools used to manage its
installation (about when and how rtupdate is called) and should be
fixed now. Feel free to reopen if it still applies.
Kindly,
Sandro
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
