[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debhelper sequencing: Service program can't start until Python packages are configured



On Sat, 12 Sep 2009 18:18:30 +1000, Ben Finney wrote:

> Howdy all,

Hello,

> [..]
> The default sequencing for Debhelper 7 means that code generated by
> ‘dh_installinit’ appears before code generated by either of
> ‘dh_pycentral’ or ‘dh_pysupport’ in the ‘postinst’ script.
> 
> [..]
> The problem comes when the ‘dh_installinit’ code not only installs the
> package init script, it tries to execute it to start the service. That
> fails, of course, because the ‘dh_pysupport’ code has not yet been
> executed and the Python packages are not yet available for import. (In
> this case, this has been reported as Bug#519623.)
> 
> Should the default sequence for ‘dh_installinit’ not appear after
> ‘dh_pycentral’ or ‘dh_pysupport’?

I believe yes. I had encountered this same problem with wicd, and bzed helped
me with that:

http://git.debian.org/?p=collab-maint/wicd.git;a=commitdiff;h=93610ed6bcdea4fe211a266b85dcc64f8a3ccf92

(check the debian/rules changes)

> Should I report this as a bug in Debhelper's default sequencing?

Please do. I believe this could be easily fixed
in /usr/share/perl5/Debian/Debhelper/Sequence/python_support.pm

Thanks!
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature


Reply to: