From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Nicolas Iooss <nicolas.iooss@m4x.org>
Cc: William Roberts <bill.c.roberts@gmail.com>,
SElinux list <selinux@vger.kernel.org>,
Ondrej Mosnacek <omosnace@redhat.com>,
William Roberts <william.c.roberts@intel.com>,
Petr Lautrbach <plautrba@redhat.com>
Subject: Re: [PATCH] libsemanage: check libsepol version
Date: Mon, 2 Mar 2020 10:24:19 -0500 [thread overview]
Message-ID: <CAEjxPJ4UPBWSP0E4pjR+F6uKMZNHK9J7LTL1gVznpwyJh9UWNA@mail.gmail.com> (raw)
In-Reply-To: <CAJfZ7=kB1i0ULzcC-EXNkUpRVbw+TCMzZGiV3EcNPsbqZ-hL1A@mail.gmail.com>
On Sun, Mar 1, 2020 at 4:43 PM Nicolas Iooss <nicolas.iooss@m4x.org> wrote:
> > > > > On the other hand, since I began packaging SELinux libraries for Arch
> > > > > Linux, I found several releases that needed to bump such a dependency
> > > > > version. For example, if I remember correctly libsemanage 2.4 requires
> > > > > libsepol>=2.4, same for 2.5, 2.6... but libsemanage 2.9 could work
> > > > > with libsepol 2.8 (I usually tries building with older versions when
> > > > > packaging a release for Arch Linux, and the history is available for
> > > > > example on https://aur.archlinux.org/cgit/aur.git/log/?h=libsemanage).
In practice, there is really only a single version for the entire
selinux userspace these days, and one should always
upgrade all components at the same time.
> > diff --git a/libsemanage/src/libsemanage.pc.in
> > b/libsemanage/src/libsemanage.pc.in
> > index 43681ddb8652..5b25e467393a 100644
> > --- a/libsemanage/src/libsemanage.pc.in
> > +++ b/libsemanage/src/libsemanage.pc.in
> > @@ -7,7 +7,7 @@ Name: libsemanage
> > Description: SELinux management library
> > Version: @VERSION@
> > URL: http://userspace.selinuxproject.org/
Not related to this per se, but these URLs need to be updated to point
to the GitHub releases.
next prev parent reply other threads:[~2020-03-02 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:47 [PATCH] libsemange: add missing header sepol/policydb.h bill.c.roberts
2020-02-28 8:17 ` Ondrej Mosnacek
2020-02-28 12:43 ` William Roberts
2020-02-28 13:32 ` [PATCH] libsemanage: check libsepol version bill.c.roberts
2020-03-01 19:24 ` Nicolas Iooss
2020-03-01 19:53 ` William Roberts
2020-03-01 20:21 ` Nicolas Iooss
2020-03-01 20:33 ` William Roberts
[not found] ` <CAJfZ7=kocVtoWs2fo8JkH+7FicnORGGVQEH51tG95u2nGoaPTw@mail.gmail.com>
[not found] ` <CAFftDdpkV9furWPR1VzuSV6ew93+Rij3bF7gw2Lup9aa8VMrSw@mail.gmail.com>
2020-03-01 21:43 ` Nicolas Iooss
2020-03-01 22:19 ` William Roberts
2020-03-02 15:24 ` Stephen Smalley [this message]
2020-03-02 15:32 ` William Roberts
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=CAEjxPJ4UPBWSP0E4pjR+F6uKMZNHK9J7LTL1gVznpwyJh9UWNA@mail.gmail.com \
--to=stephen.smalley.work@gmail.com \
--cc=bill.c.roberts@gmail.com \
--cc=nicolas.iooss@m4x.org \
--cc=omosnace@redhat.com \
--cc=plautrba@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=william.c.roberts@intel.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;
as well as URLs for NNTP newsgroup(s).