> |is shipped and/or installed by upstream in a way that doesn’t
> make
> |it easy to let dh_installinit find it.
> `
>
> Must have had not enough sleep and/or not enough coffee. ;)
I'll put that into the newmaint guide, it's a small enough thi
On 01/07/2010 06:52 PM, Russ Allbery wrote:
> Darshaka Pathirana writes:
>
>> I have the following situation:
>
>> I have a "upstream"-package which provides an init.d-script.
>
>> dh_installinit(1) states:
>> ,
>> | If a file named d
Darshaka Pathirana writes:
> I have the following situation:
> I have a "upstream"-package which provides an init.d-script.
> dh_installinit(1) states:
> ,
> | If a file named debian/package.init exists, then it is installed into
> | etc/init.d/package in the p
Dear mentors!
I have the following situation:
I have a "upstream"-package which provides an init.d-script.
dh_installinit(1) states:
,
| If a file named debian/package.init exists, then it is installed into
| etc/init.d/package in the package build directory, with "package
t
>> > with error status code to allow an admin to script something e.g.).
>>
>> Why this? Why not just
>>
>> invoke-rc.d $INITSCRIPT start || true
>
> Because I do not want to install, configure, etc. the initscript
> manually in postinst. I simply use dh_
ng e.g.).
>
> Why this? Why not just
>
> invoke-rc.d $INITSCRIPT start || true
Because I do not want to install, configure, etc. the initscript
manually in postinst. I simply use dh_installinit as helper which will
also work if the init-procedure changes somehow or something like this.
-- Balu
On Thu, Jun 17, 2004 at 02:04:52PM +0200, Thomas Hood wrote:
> Don't try to control the exit status with an environment variable.
> Let the initscript return a nonzero status. If you need to ignore
> the status (because you have "set -e") then append '|| :' to the
> line that returns the error sta
t
>> > with error status code to allow an admin to script something e.g.).
>>
>> Why this? Why not just
>>
>> invoke-rc.d $INITSCRIPT start || true
>
> Because I do not want to install, configure, etc. the initscript
> manually in postinst. I simply use dh_
Thomas -Balu- Walter <[EMAIL PROTECTED]> wrote:
> On Tue, May 18, 2004 at 08:43:40AM -0700, Matt Zimmerman wrote:
>>
>> Let it fail to start; simply don't allow this to break the postinst.
>
> Okay, after fiddling around a little and not being sure what solution
> I'd prefer I go for Matt's.
>
>
ng e.g.).
>
> Why this? Why not just
>
> invoke-rc.d $INITSCRIPT start || true
Because I do not want to install, configure, etc. the initscript
manually in postinst. I simply use dh_installinit as helper which will
also work if the init-procedure changes somehow or something like
On Thu, 2004-06-17 at 13:48, Thomas -Balu- Walter wrote:
> To do so I need the initscript to make a difference if the package is
> called from postinst (don't exist with error status code) or not (exit
> with error status code to allow an admin to script something e.g.).
Don't try to control the e
On Thu, Jun 17, 2004 at 02:04:52PM +0200, Thomas Hood wrote:
> Don't try to control the exit status with an environment variable.
> Let the initscript return a nonzero status. If you need to ignore
> the status (because you have "set -e") then append '|| :' to the
> line that returns the error sta
urce using /etc/camsource.conf and enable it in
> > /etc/default/camsource if you want to use init to start it."
> > if not enabled...
> >
> > Use --no-start with dh_installinit and stop the daemon manually on
> > uninstall in prerm?
> >
> > Other?
Thomas -Balu- Walter <[EMAIL PROTECTED]> wrote:
> On Tue, May 18, 2004 at 08:43:40AM -0700, Matt Zimmerman wrote:
>>
>> Let it fail to start; simply don't allow this to break the postinst.
>
> Okay, after fiddling around a little and not being sure what solution
> I'd prefer I go for Matt's.
>
>
On Thu, 2004-06-17 at 13:48, Thomas -Balu- Walter wrote:
> To do so I need the initscript to make a difference if the package is
> called from postinst (don't exist with error status code) or not (exit
> with error status code to allow an admin to script something e.g.).
Don't try to control the e
urce using /etc/camsource.conf and enable it in
> > /etc/default/camsource if you want to use init to start it."
> > if not enabled...
> >
> > Use --no-start with dh_installinit and stop the daemon manually on
> > uninstall in prerm?
> >
> > Other?
."
> if not enabled...
>
> Use --no-start with dh_installinit and stop the daemon manually on
> uninstall in prerm?
>
> Other?
Let it fail to start; simply don't allow this to break the postinst.
--
- mdz
."
> if not enabled...
>
> Use --no-start with dh_installinit and stop the daemon manually on
> uninstall in prerm?
>
> Other?
Let it fail to start; simply don't allow this to break the postinst.
--
- mdz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, May 10, 2004 at 12:18:07PM -0300, Ben Armstrong wrote:
> On Mon, 2004-05-10 at 11:20, Thomas -Balu- Walter wrote:
> > I'm not sure what would be best practice to avoid those errors, because
> > the admin might have to configure the video device first anyway (though
> > the default /dev/vide
On Mon, 2004-05-10 at 11:20, Thomas -Balu- Walter wrote:
> I'm not sure what would be best practice to avoid those errors, because
> the admin might have to configure the video device first anyway (though
> the default /dev/video0 is usually a nice guess).
I should think the normal case for a webc
I am packaging camsource - a webcam-streaming software.
I've just added an init script that gets installed with dh_installinit.
However on this testing box where I check the packaging in chroot does
not have a webcam attached, so the daemon is missing a device and not
starting correctly:
U
On Mon, May 10, 2004 at 12:18:07PM -0300, Ben Armstrong wrote:
> On Mon, 2004-05-10 at 11:20, Thomas -Balu- Walter wrote:
> > I'm not sure what would be best practice to avoid those errors, because
> > the admin might have to configure the video device first anyway (though
> > the default /dev/vide
On Mon, 2004-05-10 at 11:20, Thomas -Balu- Walter wrote:
> I'm not sure what would be best practice to avoid those errors, because
> the admin might have to configure the video device first anyway (though
> the default /dev/video0 is usually a nice guess).
I should think the normal case for a webc
I am packaging camsource - a webcam-streaming software.
I've just added an init script that gets installed with dh_installinit.
However on this testing box where I check the packaging in chroot does
not have a webcam attached, so the daemon is missing a device and not
starting correctly:
U
; >
> > > > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > > > ${misc:Depends}?
> > >
> > > No. That's a build-dependency, you know. There is no runtime dependency.
>
> Duh, I got debconf and debhelper mixed up. Neve
On Sun, 10 Nov 2002, Martin Godisch wrote:
> On Sun, Nov 10, 2002 at 09:13:39 -0200, Henrique de Moraes Holschuh wrote:
>
> > On Sun, 10 Nov 2002, Martin Godisch wrote:
> >
> > > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > &
and this seems to have nothing to do with
your other, very strange suggestion that any package that uses
dh_installinit needs to depend on debconf. Show me something breaking
because of a missing dependency.
--
see shy jo
pgpw33R3hzMQZ.pgp
Description: PGP signature
Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 12:06:58 -0500, Joey Hess wrote:
>
> > [EMAIL PROTECTED]:~>grep prerm =dpkg-reconfigure
> > foreach my $info (['prerm','upgrade', $version],
>
> May I suggest that dh_installini
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > ${misc:Depends}?
>
> No. That's a build-dependency, you know. There is no runtime dependency.
Of course debconf (dpkg-r
; >
> > > > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > > > ${misc:Depends}?
> > >
> > > No. That's a build-dependency, you know. There is no runtime dependency.
>
> Duh, I got debconf and debhelper mixed up. Neve
On Sun, 10 Nov 2002, Martin Godisch wrote:
> On Sun, Nov 10, 2002 at 09:13:39 -0200, Henrique de Moraes Holschuh wrote:
>
> > On Sun, 10 Nov 2002, Martin Godisch wrote:
> >
> > > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > &
and this seems to have nothing to do with
your other, very strange suggestion that any package that uses
dh_installinit needs to depend on debconf. Show me something breaking
because of a missing dependency.
--
see shy jo
msg07811/pgp0.pgp
Description: PGP signature
Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 12:06:58 -0500, Joey Hess wrote:
>
> > joey@dragon:~>grep prerm =dpkg-reconfigure
> > foreach my $info (['prerm','upgrade', $version],
>
> May I suggest that dh_installinit adds '
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> > May I suggest that dh_installinit adds 'debconf (>= 1.2.9)' to
> > ${misc:Depends}?
>
> No. That's a build-dependency, you know. There is no runtime dependency.
Of course debconf (dpkg-r
On Sun, 10 Nov 2002, Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 12:06:58 -0500, Joey Hess wrote:
> > [EMAIL PROTECTED]:~>grep prerm =dpkg-reconfigure
> > foreach my $info (['prerm','upgrade', $version],
>
> May I suggest that
On Sun, 10 Nov 2002, Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 12:06:58 -0500, Joey Hess wrote:
> > joey@dragon:~>grep prerm =dpkg-reconfigure
> > foreach my $info (['prerm','upgrade', $version],
>
> May I suggest that
On Sat, 09 Nov 2002, Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 08:12:57 -0200, Henrique de Moraes Holschuh wrote:
> > On Sat, 09 Nov 2002, Martin Godisch wrote:
> > > dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> > > postinst,
On Sat, 09 Nov 2002, Martin Godisch wrote:
> On Sat, Nov 09, 2002 at 08:12:57 -0200, Henrique de Moraes Holschuh wrote:
> > On Sat, 09 Nov 2002, Martin Godisch wrote:
> > > dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> > > postinst,
Martin Godisch wrote:
> I do not upgrade, dpkg-reconfigure doesn't call prerm...
Look again.
[EMAIL PROTECTED]:~>grep prerm =dpkg-reconfigure
foreach my $info (['prerm','upgrade', $version],
--
see shy jo
pgp58jOS4Ok1X.pgp
Description: PGP signature
Martin Godisch wrote:
> dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> postinst, hence, after dpkg-reconfigure is run, postinst will try to
> start an already running service, start-stop-daemon will fail, and the
> daemon will not reload its new conf
Martin Godisch wrote:
> I do not upgrade, dpkg-reconfigure doesn't call prerm...
Look again.
joey@dragon:~>grep prerm =dpkg-reconfigure
foreach my $info (['prerm','upgrade', $version],
--
see shy jo
msg07790/pgp0.pgp
Description: PGP signature
Martin Godisch wrote:
> dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> postinst, hence, after dpkg-reconfigure is run, postinst will try to
> start an already running service, start-stop-daemon will fail, and the
> daemon will not reload its new conf
On Sat, 09 Nov 2002, Martin Godisch wrote:
> dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> postinst, hence, after dpkg-reconfigure is run, postinst will try to
> start an already running service, start-stop-daemon will fail, and the
> daemon w
On Sat, 09 Nov 2002, Martin Godisch wrote:
> dh_installinit adds 'invoke-rc.d start' (or: init.d/package start) to
> postinst, hence, after dpkg-reconfigure is run, postinst will try to
> start an already running service, start-stop-daemon will fail, and the
> daemon w
dent files here.
> binary-arch: build install
> # dh_testversion
> dh_testdir
> dh_testroot
> # dh_installdebconf
> dh_installdocs
> dh_installexamples
> dh_installmenu
> # dh_installemacsen
> # dh_installpam
> dh_installini
les
dh_installmenu
# dh_installemacsen
# dh_installpam
dh_installinit
dh_installcron
dh_installmanpages
dh_installinfo
# dh_undocumented
dh_installchangelogs CHANGES.txt
dh_link
dh_strip
dh_compress
dh_fixpe
On Wed, May 23, 2001 at 12:18:18PM +0530, Viral wrote:
> Hi,
>
> I am packaging mosix, which is a cluster computing tool which does fault
> tolerance, load balancing and process migration.
>
> It comes as 2 kernel patches. One is a standard kernel patch which I handle
> with dh_installkpatches. T
Viral <[EMAIL PROTECTED]> wrote:
>Also, with dh_installinit, the init.d script gets a default priority of
>20. How do I change it ?
>
>I tried dh_installinit -- defaults s90 k10
>
>It makes the debs fine, but during installation, update-rc.d grumbles of
>bad parameters.
On Wed, May 23, 2001 at 12:18:18PM +0530, Viral wrote:
> Hi,
>
> I am packaging mosix, which is a cluster computing tool which does fault
> tolerance, load balancing and process migration.
>
> It comes as 2 kernel patches. One is a standard kernel patch which I handle
> with dh_installkpatches.
.
Can I handle this too with dh_installkpatches ? How otherwise would be a good
way to do it ? Currently, I just have a note in README.Debian to do it
manually.
Also, with dh_installinit, the init.d script gets a default priority of
20. How do I change it ?
I tried dh_installinit -- defaults s90
Viral <[EMAIL PROTECTED]> wrote:
>Also, with dh_installinit, the init.d script gets a default priority of
>20. How do I change it ?
>
>I tried dh_installinit -- defaults s90 k10
>
>It makes the debs fine, but during installation, update-rc.d grumbles of
>bad param
.
Can I handle this too with dh_installkpatches ? How otherwise would be a good
way to do it ? Currently, I just have a note in README.Debian to do it
manually.
Also, with dh_installinit, the init.d script gets a default priority of
20. How do I change it ?
I tried dh_installinit -- defaults s90
52 matches
Mail list logo
