[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#3060: problems with new sysklogd-1.3-3

Hallo Dirk!

}Package: sysklogd
}Version: 1.3-3
}I just installed the new sysklogd-1.3-3 fresh from master. There are several
}problems with it.
}I had syslogd-1.3-2 installed (note the missing 'k'). After I installed the
}new sysklogd-1.3-3, 'dpkg -l syslogd sysklogd' revealed that both versions
}are installed.

This is the correct result.

}Moreover, I had two daemons sysklogd running as a new one was added, but
}the old one didn't stop.

No, there was never a deamon called sysklogd. As you could have read
in the buglist (Bug#2836) there was a problem with the pidfile for the
syslogd, which causes the syslogd not to stop. How should it? Any
signal didn't beat the daemon.

I think it would be a good idea to add a killall to the postinst to
remove an existing syslogd. I will do so and prepare a new upload in a
few minutes. Hopefully this will solve the problem.

}With some --force-<action> I cleaned the situation, but this package is
}definitely not in stage that I would recommend for the 1.1 release. The
}upgrade from one version to another just doesn't work well enough.

This ONLY happens if there were both packags syslogd AND sysklogd
installed. A long time ago I made the mistake in renaming the package
back to its original name (which is sysklogd) before dpkg was able to
notice this.

The behaviour you describe is a result of this.

The used mixture of Conflicts, Provides and Replaces has been
coordinated with Ian Jackson. He knows dpkg best and probably would
have told me if there was another way to get out of this.



  / Martin Schulze  *  joey@infodrom.north.de  *  26129 Oldenburg /
 /  Wer ist Germany.Net?               http://home.pages.de/~joey/
/  - Dauerwerbesender seiner Abbonenten.    -- Lutz Donnerhacke /

Reply to: