Package: dpkg
Version: 1.18.1
Severity: normal

Dear Maintainer,

I'm using armhf Debian on a phone, NOT in a chroot, by using basically an
adapted Debian Kit to get Jessie instead of somethiing old.  Almost
everything I install gives the error message "security labeling handle: no
such file or directory".  I found on the web a workaround of sorts by
remounting /sys/fs/selinux readonly during the installation, but this causes
Android to panic and lock up after about 1 minute.  Normally this works in a
terminal emulator or over a VNC or SSH connection concurently with Android
apps.  Old versions of Debian from a year ago didn't have this problem, and
it may be compunded by the fact that Android shipped with selinux in
permissive mode until 5.0.  Going to permissive mode has little affect on
the problem.

It seems to come from src/selinux.c which is where the error message can be
found.  It seems like at least if you set selinux to permissive this should
only be a warning, not stop the install.  Or maybe it could be a new --force
option to dpkg.

I don't want to run selinux at all but Android uses it.

[email protected]  This has been discussed on the debian-arm list first.

-- System Information:
Debian Release: Jessie (8.2)
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
  500 ???  I'm an OpenBSD user, don't know a lot about Linux.
Architecture: armhf

Kernel: Linux gsm 3.4.42-ga6e4899 #1 SMP PREEMPT Thu Aug 27 00:33:12 CDT
2015 armv7l GNU/Linux
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: any, but I use tcsh
Init: good question, probably init, systemd says it wasn't booted with it.

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8
ii  libc6        2.19-18
ii  liblzma5     5.1.1alpha+20120614-2+b3
ii  libselinux1  2.3-2+b1
ii  tar          1.27.1-2+b1
ii  zlib1g       1:1.2.8.dfsg-2+b1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt  1.1.4

-- no debconf information

dpkg 1.16.16 doesn't have this problem, I don't know exactly when it
started.  1.17.25 and 1.18.4 have problems.

Reply via email to