Hello all, Petter Reinholdtsen [2010-08-06 17:32 +0200]: > I believe I already suggested how to solve this in #474515: Make all > postgresql init.d scripts have a unique provides line, and let them > all provide a $postgresql virtual facility, and get all init.d scripts > that should start before or after any of the postgresql init.d scripts > declare a relationship on $postgresql. > > See <URL: http://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities > > for more information on Debian specific virtual facilities. But this would mean that we would need to change the init scripts of all reverse dependencies of the postgresql service, just to fix the remaining upgrade problem from Lenny. If sysvinit isn't meant to handle this situation gracefully, would it be acceptable for the release team if I add a preinst snippet to postgresql-common which removes /etc/init.d/postgresql-8.3 (shipped by postgresql-8.3 in lenny) on upgrade if it was unmodified, and rename it to .dpkg-bak if it was modified? This is essentially the same that postgresql-8.4 does in its preinst to remove its obsolete init script in favor of the shared one in p-common. By the letter of the policy this preinst snippet would need to go into postgresql-8.3, but we can't retroactively fix this in lenny reliably. We could upload it to lenny-updates, but there's no guarantee that everyone installs it before an upgrade to squeeze. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Attachment:
signature.asc
Description: Digital signature