started by: och
Posted by och on May 20 2007,09:20I found out the existence of this fundamental script (supposed to be used by all Debian packages needing to run a /etc/init.d script) through an unsuccessful apt, so I guess this is the place to post this issue.
I am using DSL3.3 but I changed my source to sarge. It might be the reason for my problem.
I initially thought invoke-rc.d might be missing but there is /sbin/invoke-rc.d. Just its behavior is:
I tried to update the corresponding package (I may be wrong on that):
Does anybody know what is going on here?
Posted by Juanito on May 20 2007,10:03I'm not sure what sarge corresponds to, but I would guess it is oldstable whereas DSL now corresponds to +/- old-oldstable (archived). Did you do "apt-get update" on archived, oldstable or stable?
As you're finding, when you change from one Debian generation to another, unless you begin at the beginning of the dependency tree, apt-get or dpkg always seems to complain about an app depending on another app, or an app being used by another app, etc. For me this seems to mean that I have to force the installation at some point or other.
I've often wondered why daemons I install as part of an extension (eg acpid) will not auto start and I am obliged to enter something like "/etc/init.d/acpid start" - maybe you stumbled on the reason?
Posted by och on May 20 2007,11:30I don't like to play with 'force' options because I don't master apt or dpkg enough to fully understand all the implications of it. But you were right (in another post) and
solved my problem with invoke-rc.d while installing another package.
I'll mention it in the other post too.