From: Russell Coker <russell@coker.com.au>
To: Brian May <bam@snoopy.apana.org.au>, Tom <tom@lemuria.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: version mismatch in Debian packages
Date: Sat, 18 Jan 2003 04:17:36 +0100 [thread overview]
Message-ID: <200301180417.36062.russell@coker.com.au> (raw)
In-Reply-To: <20030116221605.GA13472@snoopy.apana.org.au>
On Thu, 16 Jan 2003 23:16, Brian May wrote:
> > The tools seem to be compiled to version 12, but the lsm patch for
> > kernel 2.4.18 is version 11. The patches for 2.4.19 and 2.4.20 are
> > version 12, it's only the 2.4.18 that is affected.
>
> I think 2.4.18 is no longer supported anymore. The patch should probably
> get deleted from the package. Russell?
Sounds reasonable to me.
> > This is ugly because woody doesn't contain source packages for 19 or
> > 20, only for 2.4.18
>
> You could use the prepatched kernels (source and image) already
> on my website...
If you use a package that's outside woody then it's reasonable to expect that
you may need other supporting packages from outside of woody.
I don't think that we need to change anything at the moment, other than
possibly removing 2.4.18.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
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.
prev parent reply other threads:[~2003-01-18 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 15:00 version mismatch in Debian packages Tom
2003-01-16 22:16 ` Brian May
2003-01-17 7:03 ` Tom
2003-01-17 21:52 ` Brian May
2003-01-20 11:11 ` Tom
2003-01-18 3:17 ` Russell Coker [this message]
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=200301180417.36062.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=bam@snoopy.apana.org.au \
--cc=selinux@tycho.nsa.gov \
--cc=tom@lemuria.org \
/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.