Bug#3060: problems with new sysklogd-1.3-3
Martin> Package: sysklogd
Martin> Version: 1.3-3
Martin> No, there was never a deamon called sysklogd. As you could have
Martin> read in the buglist (Bug#2836) there was a problem with the pidfile
Martin> for the syslogd, which causes the syslogd not to stop.
Well, it is your job as a maintainer to add some creative fudging to the
preinst of the _new_ package. killall might do it, or some grep and sed
hacking.
Martin> I think it would be a good idea to add a killall to the postinst to
Martin> remove an existing syslogd. I will do so and prepare a new upload
Martin> in a few minutes. Hopefully this will solve the problem.
Yes.
Martin> This ONLY happens if there were both packags syslogd AND sysklogd
Martin> installed. A long time ago I made the mistake in renaming the
Martin> package back to its original name (which is sysklogd) before dpkg
Martin> was able to notice this.
Martin>
Martin> The behaviour you describe is a result of this.
Martin>
Martin> The used mixture of Conflicts, Provides and Replaces has been
Martin> coordinated with Ian Jackson. He knows dpkg best and probably would
Martin> have told me if there was another way to get out of this.
I cannot believe that this situation (sysklogd plus fragments of syslogd
installed, --force-* required in (re-)installations) is the best we can do
here. Can't Ian J. and you figure out some new strategy to persuade dpkg to
really forget about syslogd, the other package?
At least it fixed what I reported to debian-user this morning and what Guy
correctly forwarded to be bug#3059. Logging now works again. So _if_ you
create a new package, please fix /etc/cron.weekly/sysklogd.
--
Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Reply to: