Florian Weimer writes (Re: use of invoke-rc.d $PACKAGE stop || exit $? in
prerm scripts):
Ian Jackson:
If the old package's prerm fails, dpkg tries the version from the new
package instead, precisely to avoid this problem. See the policy
manual for details.
And this doesn't help
* Ian Jackson:
Florian Weimer writes (Re: use of invoke-rc.d $PACKAGE stop || exit $? in
prerm scripts):
Ian Jackson:
If the old package's prerm fails, dpkg tries the version from the new
package instead, precisely to avoid this problem. See the policy
manual for details
* Henrique de Moraes Holschuh:
On Tue, 23 May 2006, Florian Weimer wrote:
I suppose it would be preferable to fix the stop target of the init
There is nothing preferable about it. Stop targets *are* to exit with
status 0 if the service is already stopped.
Makes sense. In this case, fixing
Francesco P. Lovergine writes (Re: use of invoke-rc.d $PACKAGE stop || exit
$? in prerm scripts):
Unfortunately sometimes the daemon does not stop for an error in the
maintainer script and that prevents upgrading for ever, even when
the package has been corrected. [...]
If the old package's
* Ian Jackson:
Francesco P. Lovergine writes (Re: use of invoke-rc.d $PACKAGE stop || exit
$? in prerm scripts):
Unfortunately sometimes the daemon does not stop for an error in the
maintainer script and that prevents upgrading for ever, even when
the package has been corrected
On Tue, 23 May 2006, Michael Prokop wrote:
way of life, I'd just like to make sure that removing packages
always works.
If you are going to ignore a failing initscript in order to remove a
package, and that leaves a daemon running, then expect to get a very nasty
bug report...
--
One disk
* Henrique de Moraes Holschuh [EMAIL PROTECTED] [20060523 21:59]:
On Tue, 23 May 2006, Michael Prokop wrote:
way of life, I'd just like to make sure that removing packages
always works.
If you are going to ignore a failing initscript in order to remove a
package, and that leaves a daemon
Michael Prokop wrote:
But /etc/init.d/$PACKAGE is executed only, if [ -x `which
invoke-rc.d 2/dev/null` ] fails. And I still don't see what's the
Ah, I entirely misunderstood your intention. I thought you want to get rid
of this if condition and execute the commands one after the other. Sorry
On Tue, 23 May 2006, Michael Prokop wrote:
Yes, for sure. But IMO it's the initscript which should make sure
that the daemon is stopped when running the stop-rule.
Most try, to the point of doing a kill -9 if the daemon doesn't go away
easily. But if it doesn't die even with a kill -9 (say,
On Tue, May 23, 2006 at 10:21:53AM -0300, Henrique de Moraes Holschuh wrote:
There is nothing preferable about it. Stop targets *are* to exit with
status 0 if the service is already stopped.
The fact that Debian policy still has this as a should clause is just
cruft that needs to be
Florian Weimer [EMAIL PROTECTED] wrote:
* Michael Prokop:
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
would be a replacement already used in some packages like for
example at, binfmt-support, dnsmasq, drbd0.7-utils, freeradius, hal,
scanlogd,
* Bernd Schubert [EMAIL PROTECTED] wrote:
inside their prerm maintainer scripts. If stopping $PACKAGE through
invoke-rc.d/init-script fails, removing the package fails as well.
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
We are using chroot environments
Michael Prokop wrote:
* Bernd Schubert [EMAIL PROTECTED] wrote:
inside their prerm maintainer scripts. If stopping $PACKAGE through
invoke-rc.d/init-script fails, removing the package fails as well.
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
We
On Tue, 23 May 2006, Florian Weimer wrote:
I suppose it would be preferable to fix the stop target of the init
There is nothing preferable about it. Stop targets *are* to exit with
status 0 if the service is already stopped.
The fact that Debian policy still has this as a should clause is just
On Tue, May 23, 2006 at 09:46:10AM +0200, Frank Küster wrote:
Florian Weimer [EMAIL PROTECTED] wrote:
* Michael Prokop:
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
would be a replacement already used in some packages like for
example at,
On Tue, 23 May 2006, Francesco P. Lovergine wrote:
Unfortunately sometimes the daemon does not stop for an error in the
maintainer script and that prevents upgrading for ever, even when
the package has been corrected. BTW, it seems a lack in the policy
to specify how the maintainers scripts
inside their prerm maintainer scripts. If stopping $PACKAGE through
invoke-rc.d/init-script fails, removing the package fails as well.
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
We are using chroot environments (e.g. with sid) where no daemon is
* Bernd Schubert [EMAIL PROTECTED] wrote:
Michael Prokop wrote:
How do you achieve that? For example symlinking invoke-rc.d to
/bin/true is a workaround, but I'm searching for a general solution
to avoid that daemons are started when upgrading even though they
did not run before the upgrade
* Michael Prokop:
Using:
invoke-rc.d $PACKAGE stop || true
/etc/init.d/$PACKAGE stop || true
would be a replacement already used in some packages like for
example at, binfmt-support, dnsmasq, drbd0.7-utils, freeradius, hal,
scanlogd, sl-modem-daemon, snort.
I suppose it would be
19 matches
Mail list logo
