Created attachment 326558 [details, diff] Install the syslog.conf included in files/, not the one from the Debian patchset. There are different sample syslog.conf files that get installed depending on whether you install app-admin/sysklogd-1.4x or app-admin/sysklogd-1.5x (same slot). This could possibly be declared "not a bug", but it seems messy to me. app-admin/sysklogd includes a sample/default syslog.conf file in files/. However, this is only used by the sysklogd 1.4 ebuild. The 1.5 ebuilds use a Debian patch set that includes a syslog.conf file, and they deploy that file, not the one in files/. They are similar, but not identical. [ There is yet a third: the stock source tarballs for sysklogd-1.[45] include a sample syslog.conf as well. But no ebuilds actually deploy that version, so I'm ignoring it. ] Probably this came about because 1.4 didn't include a file so one was added; when 1.5 (+Debian patches) included one, there was no need to use the one previously added to files/. However, it looks as if changes were made to the version in files/ - i.e. it should be the preferred version. But the 1.5 ebuilds don't use it. (Contrary to what bug #376553 commenters say--although maybe the case was different a year ago.) I'll attach a simple patch for sysklogd-1.5-r2.ebuild that switches to using the version in files/. [ This is relevant because I'm about to suggest a default sysklogd.logrotate file for bug #324401, but I need to know what syslog.conf to target. ]
the intention is to stop shipping our own and just use the one from Debian. hence we do not want 1.5.x to use $FILESDIR/syslog.conf.