From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: [owner@bugs.debian.org: Bug#338543 acknowledged by developer (Bug#338543: fixed in linux-2.6 2.6.14-3)]
Date: Mon, 14 Nov 2005 21:16:48 +0000 [thread overview]
Message-ID: <20051114211648.GL8699@lkcl.net> (raw)
hurrah. much info cut from the original (very long) message.
highlights below.
----- Forwarded message from Debian Bug Tracking System <owner@bugs.debian.org> -----
This is an automatic notification regarding your Bug report
#338543: linux-image-2.6.14-1-686: CONFIG_SECURITY_NETWORK is disabled which totally breaks SE/Linux,
which was filed against the linux-image-2.6.14-1-686 package.
It has been closed by one of the developers, namely
Norbert Tretkowski <nobse@debian.org>.
Architecture: source i386 all
Version: 2.6.14-3
Distribution: unstable
Urgency: low
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Norbert Tretkowski <nobse@debian.org>
linux-headers-2.6.14 - All header files for Linux kernel 2.6.14
linux-image-2.6.14-2-686 - Linux kernel 2.6.14 image on PPro/Celeron/PII/PIII/P4 machines
linux-tree-2.6.14 - Linux kernel source tree for building Debian kernel images
Closes: 267600 321200 336424 336431 336450 337072 337089 337713 338543 338911
Changes:
linux-2.6 (2.6.14-3) unstable; urgency=low
.
[ Frederik Sch??ler ]
* activate CONFIG_SECURITY_NETWORK to fix SElinux operation.
(Closes: #338543)
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
reply other threads:[~2005-11-14 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051114211648.GL8699@lkcl.net \
--to=lkcl@lkcl.net \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.