From: Sinan Kaya <okaya@kernel.org>
To: yocto@yoctoproject.org
Subject: [selinux] sumo compilation
Date: Wed, 17 Oct 2018 19:00:56 -0400 [thread overview]
Message-ID: <ead8ad97-856d-03bb-4444-dc6e4a472d61@kernel.org> (raw)
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707
(virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started
NOTE: Running task 1413 of 2707
(/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching file misc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.
Sinan
next reply other threads:[~2018-10-17 23:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 23:00 Sinan Kaya [this message]
2018-10-17 23:27 ` [selinux] sumo compilation sscott
2018-10-18 6:14 ` Stefano Cappa
2018-10-18 13:48 ` Steve Scott
2018-10-18 14:49 ` Sinan Kaya
2018-10-18 15:05 ` Sinan Kaya
2018-10-18 15:46 ` Steve Scott
2018-10-18 16:15 ` Sinan Kaya
2018-10-18 16:00 ` Mark Hatle
2018-10-18 19:08 ` Joe MacDonald
2018-10-18 20:48 ` Sinan Kaya
2018-10-18 21:13 ` Stefano Cappa
2018-10-20 23:18 ` Stefano Cappa
2018-10-21 8:13 ` Mark Hatle
2018-10-24 23:49 ` Joe MacDonald
2018-10-30 13:45 ` Sinan Kaya
2018-12-30 11:28 ` Stefano Cappa
2018-12-30 14:31 ` MacDonald, Joe
2018-12-31 2:46 ` Joe MacDonald
2018-12-31 2:52 ` MacDonald, Joe
2019-01-09 20:55 ` Stefano Cappa
2019-01-14 23:28 ` Stefano Cappa
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=ead8ad97-856d-03bb-4444-dc6e4a472d61@kernel.org \
--to=okaya@kernel.org \
--cc=yocto@yoctoproject.org \
/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.