All of lore.kernel.org
 help / color / mirror / Atom feed
From: antoine <antoine@nagafix.co.uk>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: upgrade howto
Date: Wed, 22 Jun 2005 20:41:23 +0100	[thread overview]
Message-ID: <1119469283.9358.37.camel@localhost> (raw)
In-Reply-To: <1119441245.13181.18.camel@moss-spartans.epoch.ncsc.mil>

On Wed, 2005-06-22 at 07:54 -0400, Stephen Smalley wrote:
> On Wed, 2005-06-22 at 00:06 +0100, antoine wrote:
> > What is the safest way of upgrading libselinux and libsepol?
> > 
> > I attempted it a couple of weeks ago and had to resort to statically
> > linked copies of ls and tar to restore the previous version after the
> > upgrade broke my system. Clearly, I did something wrong. What is scary
> > is that a lot of the core system utilities are linked against libselinux
> > (ls, init, portage, etc) and that when I upgrade, it would seem that I
> > need to rebuild them (as just upgrading the library left them unusable)
> > - which is impossible without these basic tools... catch 22?
> 
> Note btw that while upgrading should always work, downgrading is another
> matter.  So if Gentoo was using a newer base version of libsepol and
> libselinux (e.g. one from the sourceforge CVS tree), and you downgraded
> to an older one (e.g. the last nsa.gov release, which was in March),
> that could easily break your system as your userland may be depending on
> newer interfaces.  nsa.gov releases are only made periodically,
> typically when there is a new Linux kernel release (e.g. one should be
> occurring soon for 2.6.12), whereas the sourceforge CVS tree tracks
> development much more closely, and some distributions (like Fedora)
> track the sourceforge CVS tree directly.

I was upgrading from CVS and clearly I must have done something wrong.
I've just upgraded by creating new Gentoo ebuild files for the just
released versions and it all worked fine.

Antoine


--
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-06-22 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 23:06 upgrade howto antoine
2005-06-22 11:45 ` Stephen Smalley
2005-06-22 11:54 ` Stephen Smalley
2005-06-22 19:41   ` antoine [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=1119469283.9358.37.camel@localhost \
    --to=antoine@nagafix.co.uk \
    --cc=sds@tycho.nsa.gov \
    --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.