Your message dated Wed, 29 Nov 2006 19:49:37 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398771: installing mailman with python 2.3 causes loop
condition during python upgrade
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: mailman
Version: 1:2.1.9-2
Severity: important
Configuring python (2.4.4-1) ...
running python rtupdate hooks for python2.4...
Traceback (most recent call last):
File "/usr/sbin/update-python-modules", line 268, in ?
bytecompile_privatedir(basedir)
File "/usr/sbin/update-python-modules", line 205, in bytecompile_privatedir
process(basedir,bytecompile_only)
File "/usr/sbin/update-python-modules", line 154, in process
func(basedir, dir, file)
File "/usr/sbin/update-python-modules", line 90, in bytecompile_only
compile(fullpath)
File "/usr/lib/python2.4/py_compile.py", line 115, in compile
f = open(file, 'U')
IOError: [Errno 2] No such file or directory:
'/usr/lib/mailman/Mailman/mm_cfg.py'
error running python rtupdate hook python-support
Removing mailman allows python to be configured correctly.
Mailman may be successfully installed then.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Versions of packages mailman depends on:
ii adduser 3.87 Add and remove users and groups
ii apache2 2.2.3-3.1 Next generation, scalable, extenda
ii apache2-mpm-worker [httpd] 2.2.3-3.1 High speed threaded model for Apac
ii cron 3.0pl1-94 management of regular background p
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii libc6 2.3.6-13 GNU C Library: Shared libraries
ii logrotate 3.7.1-3 Log rotation utility
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
ii postfix [mail-transport-agent 2.2.10-2 A high-performance mail transport
ii pwgen 2.05-1 Automatic Password generation
ii python 2.4.4-1 An interactive high-level object-o
ii python-support 0.5.4 automated rebuilding support for p
ii ucf 2.0010 Update Configuration File: preserv
mailman recommends no packages.
-- debconf information:
mailman/queue_files_present:
mailman/default_server_language: en
mailman/gate_news: false
mailman/site_languages: en
* mailman/used_languages:
* mailman/create_site_list:
--- End Message ---
--- Begin Message ---
On Fri, Nov 24, 2006 at 08:18:59AM +0100, Raphael Hertzog wrote:
> On Fri, 24 Nov 2006, Lionel Elie Mamane wrote:
>> Ah, I think I have it. We can remove the symlink in pre-rtupdate and
>> put it back in post-rtupdate. That takes care of python version
>> updates. Now, for new installs... Python will guaranteed be configured
>> before us, so indeed creating the symlink in postinst will be safe.
> This looks like really overkill for your need. Python-support has
> been fixed and will only warn about the failed byte-compilation, so
> mailman's installation shouldn't fail anymore.
Oh, I just realised python-support will only warn about failed
byte-compilation not only at the time of a python upgrades, but also
of Mailman install/upgrade. So we can just consider this "not a bug"
and not do anything.
--
Lionel
--- End Message ---
