Re: postinst corrupts my settings after a 'apt-get upgrade'.

2011-10-06 Thread Volker Theile
Many thanks, a

update-rc.d forked-daapd disable

makes it :-)

Regards
Volker

 Original-Nachricht 
 Datum: Wed, 05 Oct 2011 12:06:27 -0700
 Von: Russ Allbery r...@debian.org
 An: vot...@gmx.de
 CC: debian-dpkg@lists.debian.org
 Betreff: Re: postinst corrupts my settings after a \'apt-get upgrade\'.

 vot...@gmx.de writes:
 
  i have some problems with the package update mechanism in my
  appliance. I have installed various services like
  'forked-daapd'. Because i wanted to monitor and start the daemon via
  'monit' i removed the init script from the runlevels via 'update-rc.d -f
  forked-daapd remove'. After a 'apt-get dist-upgrade' (after enabling
  Squeeze backports) i received the package from the backports. The
  problem now is that it seems that the 'postinst' script has registered
  the runlevels again and the process is statred via init.d script and
  monit now.
 
 The basic problem that you're having is that this is not the correct way
 to disable an init script in Debian.  The correct way is to rename all the
 S* links in /etc/rc?.d for that service to K* links.  If you make that
 change, you'll find it's preserved across upgrades and changes.
 
 And yes, that's annoying and there's no good tool in the base installation
 to handle it for you, and that's a bug that should be fixed.
 
 -- 
 Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/
 
 
 -- 
 To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/8739f7b6mk@windlord.stanford.edu
 

-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de


-- 
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111006205229.15...@gmx.net



Re: postinst corrupts my settings after a 'apt-get upgrade'.

2011-10-05 Thread Jonathan Nieder
Hi,

vot...@gmx.de wrote:

 Another szenario might be that i have installed service xyz but i have 
 disabled
 it because i did not want to use it right now. If it is updated via a package
 update the default postinst behaviour is to register the init script in the
 runlevels and starts the daemon/app/whatever. This is not the behaviour i
 expect.

 I'm thinking wrong here or is this a problem in dpkg/APT?

 In my eyes the postinst script should check whether it is installed the first
 time or not.

This has nothing to do with dpkg or APT.  It has more to do with
Debian policy[1] --- from the point of view of dpkg, each package
provides its own postinst script with whatever behavior it chooses.

There have been a few discussions of this recently[2][3][4].

Hope that helps,
Jonathan

[1] http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3
[2] http://thread.gmane.org/gmane.linux.debian.devel.general/163640/focus=164342
[3] http://thread.gmane.org/gmane.linux.debian.devel.general/163640/focus=164027
[4] 
http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/764253/focus=159724


-- 
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111005114317.GC27187@elie



Re: postinst corrupts my settings after a 'apt-get upgrade'.

2011-10-05 Thread Russ Allbery
vot...@gmx.de writes:

 i have some problems with the package update mechanism in my
 appliance. I have installed various services like
 'forked-daapd'. Because i wanted to monitor and start the daemon via
 'monit' i removed the init script from the runlevels via 'update-rc.d -f
 forked-daapd remove'. After a 'apt-get dist-upgrade' (after enabling
 Squeeze backports) i received the package from the backports. The
 problem now is that it seems that the 'postinst' script has registered
 the runlevels again and the process is statred via init.d script and
 monit now.

The basic problem that you're having is that this is not the correct way
to disable an init script in Debian.  The correct way is to rename all the
S* links in /etc/rc?.d for that service to K* links.  If you make that
change, you'll find it's preserved across upgrades and changes.

And yes, that's annoying and there's no good tool in the base installation
to handle it for you, and that's a bug that should be fixed.

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8739f7b6mk@windlord.stanford.edu