On 07/20/2010 09:08 PM, Philipp Kern wrote: > Well, that lsb_release is written in Python is just an implementation > detail, no? So it just should not be the responsibility of the caller.
It should as you can't assume that your dependencies are configured when your own package is being configured (Debian Policy 3.5). So if you depend on a properly install *and* configured lsb_release, either add a Pre-Depends *or* chose a different way to ensure it is configured properly. And this is an easy one actually as all you need to do is to run update-python-modules -p. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c45fc95.50...@bzed.de
