Le samedi 04 juin 2011 à 01:42 +0200, Jakub Wilk a écrit : > Package: python-support > Version: 1.0.13 > Severity: serious > > update-python-modules calls dpkg-trigger with --no-await option. This > means that packages calling update-python-modules will be configured > even before the trigger is run. However, this is wrong, because the > trigger does an important thing: creates empty __init__.py. As such, > some packages are unusable until the trigger is run.
This is well-documented in README.Debian: such packages must use update-python-modules -p before using the modules. The problem without --no-await is that byte-compilation is a very slow operation, and it would be run several times in each upgrade run. > I attached two dummy packages to illustrate the problem: > - foo ships a Python module and a script that uses this module. foo's > modules are bytecompiled by python-support. > - bar depends on foo and uses the script provided by foo in its > postinst, but is completely Python-agnostic. > > Installing foo and bar together fails: Does it correspond to real-world use cases? If so, this might warrant reconsidering, but since anyway python-support is going away I don’t think anyone really cares. Cheers, -- .''`. Josselin Mouette : :' : `. `' `-
signature.asc
Description: This is a digitally signed message part
