[Peter Eisentraut] > $ sudo update-bootsystem-insserv > info: Checking if it is safe to convert to dependency based boot. > error: Problems running insserv: > insserv: script postgresql-8.2: service postgresql already provided!
Yes, to avoid surprises, I decided to let the check done before enabling insserv refuse to convert if such settings are present. I am not sure if it is the correct thing to do, but thought it best to err on the safe side and stick with the existing boot sequence when such setting is found. > Now if insserv doesn't handle that, we have a big problem, because > it would make the dependency based boot system unusable for systems > that have PostgreSQL installed and want to upgrade between major > versions. > > I didn't find anything in the LSB specification that would disallow > that. So I think insserv needs to be fixed. How do you believe insserv should behave when it encounter two packages with different dependencies and the same provides header? What dependency three should it build? I'm not sure, so I decided to reject such configurations until it was clear to me. The insserv program itself actually handle this (as in it generates some boot order), but I am not sure if it is the correct one (as I am not sure what would be the correct one). The code to reject such situations is only in the code to check if it is safe to activate insserv. If the insserv behaviour is OK, the check for this can be removed. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
