Package: python2.7
Version: 2.7.2-8
Severity: normal
Dear Maintainer,
I was trying to package a custom daemon written in Python for my
company. I used the following debian/rules:
#!/usr/bin/make -f
override_dh_installinit:
dh_installinit --name=customdaemon -R
%:
dh --with python2 "$@"
The end result is that, in the postinst, the section added by dh_python2
comes after the section added by dh_installinit. So python modules are
compiled after attempting to start the daemon.
While I have yet to see any real negative effects, I think that it is
similar to a reincarnation of this old bugreport:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546293
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python2.7 depends on:
ii libbz2-1.0 1.0.6-1
ii libc6 2.13-27
ii libdb4.8 4.8.30-11
ii libexpat1 2.1.0-1
ii libncursesw5 5.9-4
ii libreadline6 6.2-8
ii libsqlite3-0 3.7.11-2
ii libtinfo5 5.9-4
ii mime-support 3.52-1
ii python2.7-minimal 2.7.2-8
python2.7 recommends no packages.
Versions of packages python2.7 suggests:
pn binutils 2.22-6
pn python2.7-doc <none>
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
