From: Daniel J Walsh <dwalsh@redhat.com>
To: Joshua Brindle <brindle@quarksecurity.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Laurent Bigonville <bigon@debian.org>,
Sven Vermeulen <sven.vermeulen@siphos.be>,
SELinux <SELinux@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>
Subject: Re: Last version of policycoreutils using Fedora only API
Date: Thu, 23 May 2013 08:43:46 -0400 [thread overview]
Message-ID: <519E0F02.8070200@redhat.com> (raw)
In-Reply-To: <CADjGSjg_Mk-V82ZvP+rJJnFhkyMRaiXgerK9WJP=kyG_cwbU6Q@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/23/2013 08:36 AM, Joshua Brindle wrote:
> What were the relevant git hashes?
>
>
> On Thu, May 23, 2013 at 8:30 AM, Daniel J Walsh <dwalsh@redhat.com> wrote:
> On 05/23/2013 08:10 AM, Stephen Smalley wrote:
>>>> On 05/23/2013 03:57 AM, Laurent Bigonville wrote:
>>>>> Le Thu, 23 May 2013 07:30:18 +0200, Sven Vermeulen
>>>>> <sven.vermeulen@siphos.be> a ￩crit :
>>>>>
>>>>>> On May 23, 2013 1:09 AM, "Laurent Bigonville" <bigon@debian.org>
>>>>>> wrote:
>>>>>>> The last release of policycoreutils is using a function
>>>>>>> (selinux_current_policy_path()) that is only available in
>>>>>>> Fedora. I guess this shouldn't have made upstream.
>>>>>>>
>>>>>>> An idea how this could be sorted for other distributions?
>>>>>>
>>>>>> Please see my answer to Joshua's announcement on the new
>>>>>> userspace.
>>>>>
>>>>> Oh thanks, I messed this.
>>>>>
>>>>>> You'll need to add in the function.
>>>>>
>>>>> Well I'm not a big fan of adding function in libraries that are
>>>>> not merged upstream. IIRC eparis told me on IRC that he has not
>>>>> happy with this new functions.
>>>>
>>>> Maybe we should back out the relevant changes and cut another
>>>> release? I agree that it is wrong for an upstream release to have
>>>> Fedora-specific dependencies.
>>>>
>>>>
>>>>
>>>> -- 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.
> Yes this was a mistake.
Lets wait for Eric to chime in and get this resolved. We have a ton of new
patches that I would also like to get upstream. :^)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlGeDwIACgkQrlYvE4MpobPd6ACgmU/OGZnyAh+Cvt38qB0SkBf5
W58AoJKGMgJZ0nHe5Xu49FeVsvT8EaPA
=VC28
-----END PGP SIGNATURE-----
--
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:[~2013-05-23 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 22:53 Last version of policycoreutils using Fedora only API Laurent Bigonville
2013-05-23 5:30 ` Sven Vermeulen
2013-05-23 7:57 ` Laurent Bigonville
2013-05-23 12:10 ` Stephen Smalley
2013-05-23 12:30 ` Daniel J Walsh
2013-05-23 12:36 ` Joshua Brindle
2013-05-23 12:43 ` Daniel J Walsh [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=519E0F02.8070200@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=bigon@debian.org \
--cc=brindle@quarksecurity.com \
--cc=eparis@parisplace.org \
--cc=sds@tycho.nsa.gov \
--cc=sven.vermeulen@siphos.be \
/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.