From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates: SELinux
Date: Sun, 28 Jan 2018 13:32:44 +0100 [thread overview]
Message-ID: <87d11utb83.fsf@elephly.net> (raw)
In-Reply-To: <20180120005159.GF18016@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Wed, Jan 17, 2018 at 07:50:28PM -0800, Leo Famulari wrote:
>> The latest core-updates evaluation is coming together [0], but there are
>> still a few notable issues:
>
> Some of the SELinux packages are also failing to build:
>
> https://hydra.gnu.org/build/2414231
>
> I tried updating libsepol to 2.7, and that fixes some things, but it
> breaks other packages...
>
> If you use SELinux, please help :)
I updated to 2.7 in master and core-updates. It built fine on x86_64,
but according to Mark it broke on i686 and armhf. I’m going to take a
look at this today.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-01-28 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:27 core-updates, let’s go! Ludovic Courtès
2017-12-31 10:32 ` Efraim Flashner
2017-12-31 11:14 ` Danny Milosavljevic
2017-12-31 12:20 ` Danny Milosavljevic
2017-12-31 15:07 ` Marius Bakke
2017-12-31 17:27 ` Ricardo Wurmus
2018-01-02 18:12 ` change to the wrap-program procedure (was: core-updates, let’s go!) Hartmut Goebel
2018-01-02 19:01 ` Ricardo Wurmus
2018-01-02 19:19 ` change to the wrap-program procedure Hartmut Goebel
2018-01-02 20:47 ` Ricardo Wurmus
2017-12-31 14:44 ` core-updates, let’s go! Marius Bakke
2018-01-01 17:12 ` Ludovic Courtès
2018-01-01 19:08 ` Efraim Flashner
2018-01-03 18:35 ` Leo Famulari
2018-01-03 20:06 ` Leo Famulari
2018-01-03 19:34 ` Leo Famulari
2018-01-18 3:50 ` Leo Famulari
2018-01-20 0:51 ` core-updates: SELinux Leo Famulari
2018-01-28 12:32 ` Ricardo Wurmus [this message]
2018-01-20 20:57 ` core-updates, let’s go! Kei Kebreau
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=87d11utb83.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.