On Sunday 06 April 2008 01:18, Manoj Srivastava <[EMAIL PROTECTED]> wrote: > > HI, I'm Ccing Manoj as he contributed the SELinux support in > > dpkg. Hopefully he'll be able to help on this bug. > > I will take a look at it, and see what I can do. However, this > seems like an upstream bug in in a selinux library (libselinux1).
That could be. But if it was a bug in libselinux1 then I would have expected it to occur somewhere else. Also note that the first thing I did was to rebuild dpkg with the latest packages in unstable, so it doesn't seem to be an issue of dpkg being built against an old libselinux1. I vaguely recall a double-free bug in libselinux that was fixed some time ago, but I don't think that's the case. > > Can you tell us what precise change you did ? So that we can reproduce > > it on our own machines if possible. > > Just edit the file: > /etc/selinux/refpolicy-targeted/contexts/files/file_contexts > > and enter in a typo on one of the lines. NB Anything with an invalid type will do. A typo that confuses two different valid types won't trigger it. > Russell has already informed selinux upstream of this issue; > I'll be following the issue. I don't expect upstream to help much unless we reproduce the bug in Fedora or OpenSolaris. -- [EMAIL PROTECTED] http://etbe.coker.com.au/ My Blog http://www.coker.com.au/sponsorship.html Sponsoring Free Software development -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
