severity 398771 serious thanks This bug, in my opinion, makes the package unsuitable for release with etch. It breaks upgrades from sarge to etch, if I understand well.
There is probably verbiage in the policy / RC policy to support that, but I'm too lazy to dig it out. On Wed, Nov 15, 2006 at 04:44:09PM +0300, Alex Kuklin wrote: > Configuring python (2.4.4-1) ... > running python rtupdate hooks for python2.4... > Traceback (most recent call last): > 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 That file usually is a symlink to /etc/mailman/mm_cfg.py, a configuration file. I'm not terribly convinced it should be compiled at all, actually. It is a bug for it to be compiled unless it is *automatically* read from source when the source is newer than the compiled version. Any python expert could tell me whether it is the case? Alex, you did have the file /etc/mailman/mm_cfg.py, right? -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
