Package: selinux-policy-default Version: 2:2.20140421-9 Followup-For: Bug #757994
Dear Maintainer, the problem still exists in the current version. I'm a little bit confused - this is the second bug (I know about) that was closed because 'it should have been fixed'. It takes not more than three minutes to check, if the problem still exists. IMHO before closing a bug, at least some basic tests should have beed run. If you do not have the resources doing these tests, just ask: I would really like to support you. Kind regards Andreas -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages selinux-policy-default depends on: ii libpam-modules 1.1.8-3.1 ii libselinux1 2.3-2 ii libsepol1 2.3-2 ii policycoreutils 2.3-1 ii python 2.7.8-4 ii selinux-utils 2.3-2 Versions of packages selinux-policy-default recommends: ii checkpolicy 2.3-1 ii setools 3.3.8-3.1 Versions of packages selinux-policy-default suggests: pn logcheck <none> pn syslog-summary <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
