From: Jan Kiszka <jan.kiszka@siemens.com>
To: Shrikant Bobade <bobadeshrikant@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build
Date: Tue, 28 Jan 2020 23:11:02 +0100 [thread overview]
Message-ID: <7c722c28-9562-4d6d-c967-b292ff996f34@siemens.com> (raw)
In-Reply-To: <464051e7-0b21-4c14-93a5-2db0a6cf1c01@googlegroups.com>
On 28.01.20 14:41, Shrikant Bobade wrote:
> Hi All,
>
> Please have a look, using isar master branch I am trying to build
> "mc:qemuarm-buster:isar-image-base",
> To enable selinux support added selinux policy package
> https://packages.debian.org/buster/selinux-policy-default
> but getting "Value too large for defined data type error" during build.
>
> Build Details: https://github.com/ilbers/isar "master" branch
> Build Host: Buster Debian 10
> Machine Name: qemuarm
>
> Below are my local.conf contents.
> DISTRO ??= "debian-buster"
> MACHINE ??= "qemuarm"
> DISTRO_ARCH ??= "armhf"
>
> # selinx policy packages
> IMAGE_PREINSTALL_append = " \
> .
> .
> selinux-policy-default \
> "
>
> Error log:
> Setting up selinux-policy-default (2:2.20190201-2) ...
> Updating selinux default policy (this step might take a
> moment)...libsemanage.semanage_direct_list_all: Error while scanning
> directory /var/lib/selinux/default/active/modules. (Value too large for
> defined data type).
> /usr/sbin/semodule: Failed on full!
> Could not read the contents of /var/lib/selinux/default/active: Value
> too large for defined data type
> libsemanage.semanage_make_sandbox: Could not copy files to sandbox
> /var/lib/selinux/default/tmp. (Value too large for defined data type).
> /usr/sbin/semodule: Failed on /usr/share/selinux/default/abrt.pp.bz2!
> failed.
> dpkg: error processing package selinux-policy-default (--configure):
> installed selinux-policy-default package post-installation script
> subprocess returned error exit status 1
>
>
> Debugging further, meanwhile I would like to check if anyone else also
> faced similar issue
> Any pointers will be a great help!. This issue only reproducible on non
> amd64.
>
I've reproduced here as well. Maybe it's an issue of the qemu-user
environment, and that's why we don't see it on x86.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-01-28 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:41 Shrikant Bobade
2020-01-28 22:11 ` Jan Kiszka [this message]
2020-01-29 15:12 ` Shrikant Bobade
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=7c722c28-9562-4d6d-c967-b292ff996f34@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bobadeshrikant@gmail.com \
--cc=isar-users@googlegroups.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