public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: "Todd, Charles" <CTODD@ball.com>
Cc: linux-audit@redhat.com
Subject: Re: audit 1.0.15 released
Date: Mon, 20 Nov 2006 09:56:10 -0500	[thread overview]
Message-ID: <200611200956.10749.sgrubb@redhat.com> (raw)
In-Reply-To: <C482FF98AE985A47B8C982FD429C9E340B8E65@daytonmsg2k3.AERO.BALL.COM>

On Friday 17 November 2006 23:00, Todd, Charles wrote:
> In order to get the tarball mentioned below to compile for RHEL4u3, I had
> to modify the SPEC file to allow glibc-kernheaders >= 2.6.9.1.94, whereas
> before it was an exact match only.  

What I'd suggest is taking the RHEL4 audit 1.0.14 srpm and changing the 
version number to 1.0.15 and then rebuilding. There are differences between 
FC4 and RHEL4 spec files.

> Thanks for posting this.  Hopefully it passes the final wickets at RedHat
> without a lot of grief.

I'm seeing a couple things, so probably -2 file will be final.

-Steve

      reply	other threads:[~2006-11-20 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 22:01 audit 1.0.15 released Steve Grubb
2006-11-18  4:00 ` Todd, Charles
2006-11-20 14:56   ` Steve Grubb [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=200611200956.10749.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=CTODD@ball.com \
    --cc=linux-audit@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox