From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6786988350059315200 Date: Tue, 28 Jan 2020 05:41:05 -0800 (PST) From: Shrikant Bobade To: isar-users Message-Id: <464051e7-0b21-4c14-93a5-2db0a6cf1c01@googlegroups.com> Subject: Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_361_1563147319.1580218865902" X-Google-Token: EPHzwPEFrViI7PPWi8g0 X-Google-IP: 139.181.36.34 X-TUID: 5wnSyo4JSpio ------=_Part_361_1563147319.1580218865902 Content-Type: multipart/alternative; boundary="----=_Part_362_801171337.1580218865902" ------=_Part_362_801171337.1580218865902 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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. Thanks Shrikant Bobade ------=_Part_362_801171337.1580218865902 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
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" d= uring=C2=A0 build.

Build= Details:=C2=A0 https://github.com/ilbers/isar "master" branch
Build Host: Buster Debian 10
Machine Name: qemuarm
<= div>
Below are my local.conf contents.
DISTRO ?= ?=3D "debian-buster"
MACHINE ??=3D "qemuarm"
DISTRO_ARCH ??=3D "armhf"

# selin= x policy packages
IMAGE_PREINSTALL_append =3D " \
<= div>=C2=A0=C2=A0=C2=A0 .
=C2=A0=C2=A0=C2=A0 .
=C2= =A0=C2=A0=C2=A0 selinux-policy-default =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 \
"

Error log:
=
Setting up selinux-policy-default (2:2.20190201-2) ...
U= pdating selinux default policy (this step might take a moment)...libsemanag= e.semanage_direct_list_all: Error while scanning directory /var/lib/selinux= /default/active/modules. (Value too large for defined data type).
/usr/s= bin/semodule:=C2=A0 Failed on full!
Could not read the contents of /var/= lib/selinux/default/active: Value too large for defined data type
libsem= anage.semanage_make_sandbox: Could not copy files to sandbox /var/lib/selin= ux/default/tmp. (Value too large for defined data type).
/usr/sbin/semod= ule:=C2=A0 Failed on /usr/share/selinux/default/abrt.pp.bz2!
=C2=A0faile= d.
dpkg: error processing package selinux-policy-default (--configure):<= br>=C2=A0installed 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!. Thi= s issue only reproducible on non amd64.


Thanks
Shrikant Bobade

------=_Part_362_801171337.1580218865902-- ------=_Part_361_1563147319.1580218865902--