On Fri, 14 Jan 2011, Russ Allbery wrote:
> Roger Leigh <rle...@codelibre.net> writes:
> > I've yet to find a single system which upgraded to insserv cleanly.
> > This is mostly due to removed packages which need fully purging to
> > remove the last traces of old init scripts which break the process.
> 
> Huh. Every system I've upgraded had no problems. What is the failure
> mode? What happens on those systems?

One of the things which happens is #606588 because insserv doesn't do
#606593 yet. Also, #598020.


Don Armstrong

#606588 [i|  |☺] [unscd] unscd: Uninstallable if NSCD already installed and 
using dependency based boot
#598020 [S|  | ] [insserv] barfs when there are "invalid" init scripts
#606593 [i|  |♔] [insserv] insserv needs to support multiple packages providing 
the same service
-- 
Never underestimate the power of human stupidity.     
 -- Robert Heinlein

http://www.donarmstrong.com              http://rzlab.ucr.edu


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110115060008.ge5...@teltox.donarmstrong.com

Reply via email to