This is an important yet easy to fix bug why hasn't this patch gone into the debian package?

The same patch was recently posted to the syslog-ng mailing list (5 months after debian already knew about it and had a fix available):
http://marc.theaimsgroup.com/?l=syslog-ng&m=115107194518388&w=2

Is there something in the debian policy that has kept this bug from being fixed in the debian package at least? Not being able to set permissions correctly can break other programs and could potentially lead to security holes.

Any clarification would be appreciated.

Thanks,
Ron



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to