On Wed, Apr 09, 2014 at 01:04:29AM +0200, Martin von Wittich wrote: > Hi, > > I just updated my server's libssl1.0.0 package to 1.0.1e-2+deb7u6, and the > postinst code that restarts the daemons works pretty good: [...] > Unfortunately though, it overlooked the installed Apache server. I believe > this is due to the fact that /var/lib/dpkg/info/libssl1.0.0:i386.postinst > looks for a package "apache2-common", but the name is in fact > "apache2.2-common":
Yes. This was found only after the upload. And in jessie/unstable it's moved to the apache2 binary package and it should work there. > Oh, and the postgres init script is called /etc/init.d/postgresql, the > script seems to be looking for /etc/init.d/postgresql-9.1 and therefore > can't restart postgres either. Someone else mentioned this too, just after I uploaded to unstable. Other problems I'm aware of caused by debconf: - It fails to install if you use a non-interactive debconf frontend. - The readline based frontend shows an empty list of services while the script properly detects them. Anyway, I would like to get rid of this static list of packages and finding the init scripts. I would actually like to see the package manager like apt deal with this directly. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
