Your message dated Tue, 16 Jan 2007 04:02:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#405613: fixed in refpolicy 0.0.20061018-3 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: refpolicy Version: 0.0.20061018-2 Severity: serious Hi, make[1]: Leaving directory `/root/refpolicy-0.0.20061018/debian/build-selinux-policy-refpolicy-strict' test -e debian/stamp/config-strict || \ (cd /root/refpolicy-0.0.20061018/debian/build-selinux-policy-refpolicy-strict ; \ /usr/bin/make NAME=refpolicy-strict TYPE=strict-mcs DISTRO=debian DIRECT_INITRC=y MONOLITHIC=n conf) make[1]: Entering directory `/root/refpolicy-0.0.20061018/debian/build-selinux-policy-refpolicy-strict' cat policy/modules/kernel/corenetwork.if.in >> policy/modules/kernel/corenetwork.if egrep "^[[:blank:]]*network_(interface|node|port|packet)\(.*\)" policy/modules/kernel/corenetwork.te.in \ | m4 -D self_contained_policy -D strict_policy -D enable_mcs -D distro_debian -D direct_sysadm_daemon -D mls_num_sens=16 -D mls_num_cats=1024 -D mcs_num_cats=1024 -D hide_broken_symptoms policy/modules/kernel/corenetwork.if.m4 - \ | sed -e 's/dollarsone/\$1/g' -e 's/dollarszero/\$0/g' >> policy/modules/kernel/corenetwork.if Creating policy.xml echo '<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>' > doc/policy.xml echo '<!DOCTYPE policy SYSTEM "policy.dtd">' >> doc/policy.xml python -E support/segenxml.py -w -m metadata.xml -t policy/global_tunables -b policy/global_booleans -o doc policy/modules/admin policy/modules/apps policy/modules/kernel policy/modules/services policy/modules/system >> doc/policy.xml if test -x /usr/bin/xmllint && test -f doc/policy.dtd; then \ /usr/bin/xmllint --noout --path doc/ --dtdvalid doc/policy.dtd doc/policy.xml ;\ fi Updating policy/modules.conf and policy/booleans.conf python -E support/sedoctool.py -b policy/booleans.conf -m policy/modules.conf -x doc/policy.xml m4 -D self_contained_policy -D strict_policy -D enable_mcs -D distro_debian -D direct_sysadm_daemon -D mls_num_sens=16 -D mls_num_cats=1024 -D mcs_num_cats=1024 -D hide_broken_symptoms policy/modules/kernel/corenetwork.te.m4 policy/modules/kernel/corenetwork.te.in \ | sed -e 's/dollarsone/\$1/g' -e 's/dollarszero/\$0/g' >> policy/modules/kernel/corenetwork.te make[1]: Leaving directory `/root/refpolicy-0.0.20061018/debian/build-selinux-policy-refpolicy-strict' cp debian/modules.conf.strict \ /root/refpolicy-0.0.20061018/debian/build-selinux-policy-refpolicy-strict/policy/modules.conf echo done > debian/stamp/config-strict /bin/sh: debian/stamp/config-strict: No such file or directory make: *** [CONFIG/selinux-policy-refpolicy-strict] Error 1 As a first guess, it seems that the debian/stamp dir needs to be created at some point. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---Source: refpolicy Source-Version: 0.0.20061018-3 We believe that the bug you reported is fixed in the latest version of refpolicy, which is due to be installed in the Debian FTP archive: refpolicy_0.0.20061018-3.diff.gz to pool/main/r/refpolicy/refpolicy_0.0.20061018-3.diff.gz refpolicy_0.0.20061018-3.dsc to pool/main/r/refpolicy/refpolicy_0.0.20061018-3.dsc selinux-policy-refpolicy-doc_0.0.20061018-3_all.deb to pool/main/r/refpolicy/selinux-policy-refpolicy-doc_0.0.20061018-3_all.deb selinux-policy-refpolicy-src_0.0.20061018-3_all.deb to pool/main/r/refpolicy/selinux-policy-refpolicy-src_0.0.20061018-3_all.deb selinux-policy-refpolicy-strict_0.0.20061018-3_all.deb to pool/main/r/refpolicy/selinux-policy-refpolicy-strict_0.0.20061018-3_all.deb selinux-policy-refpolicy-targeted_0.0.20061018-3_all.deb to pool/main/r/refpolicy/selinux-policy-refpolicy-targeted_0.0.20061018-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manoj Srivastava <[EMAIL PROTECTED]> (supplier of updated refpolicy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 15 Jan 2007 13:20:30 -0600 Source: refpolicy Binary: selinux-policy-refpolicy-src selinux-policy-refpolicy-targeted selinux-policy-refpolicy-strict selinux-policy-refpolicy-doc Architecture: source all Version: 0.0.20061018-3 Distribution: unstable Urgency: high Maintainer: Manoj Srivastava <[EMAIL PROTECTED]> Changed-By: Manoj Srivastava <[EMAIL PROTECTED]> Description: selinux-policy-refpolicy-doc - Documentation for the SELinux reference policy selinux-policy-refpolicy-src - Source of the SELinux reference policy for customization selinux-policy-refpolicy-strict - Strict variant of the SELinux reference policy selinux-policy-refpolicy-targeted - Targeted variant of the SELinux reference policy Closes: 404309 404895 405103 405613 Changes: refpolicy (0.0.20061018-3) unstable; urgency=high . * Bug fix: "refpolicy: FTBFS: /bin/sh: debian/stamp/config-strict: No such file or directory", thanks to Lucas Nussbaum. This was fixed by moving all the stamps into ./debian instead. I'll re-visit the ./debian/stamp/ directory in lenny. This is a pretty minor packaging change. (Closes: #405613). * Bug fix: "selinux-policy-refpolicy-targeted: Policy for dcc misses Debian's FHS paths", thanks to Devin Carraway. From the bug report: Many of the files in these packages are overlooked when labelling files, because refpolicy's dcc module stipulates paths not consistent with the Debian FHS layout. The files go unlabelled and dcc-client (at least) stops working. The two major problems are the references to /usr/libexec/dcc (damons, placed in /usr/sbin by the Debian packages) and to /var/dcc (all sorts of things, placed under /var/lib/dcc). A side effect of the latter is that dccifd_t and probably others need search on var_lib_t, through which it must pass to get to /var/lib/dcc. Fixed the policy; will send upstream. (Closes: #404309). * Bug fix: "selinux-policy-refpolicy-targeted: clamav policy forbids clamd_t search on /var/lib", thanks to Devin Carraway. This is a simple one line change, and obviously an oversight; I think getting clamd to work is fairly important. (Closes: #404895). * Bug fix: "selinux-policy-refpolicy-targeted: Multiple problems with courier policy", thanks to Devin Carraway. There is detailed information of the changes made in the bug report, and in the commit logs. Again, fixing courier daemons seems pretty important; SELinux tends to get used a lot on remote mail servers, and this fixes issues with the policy. (Closes: #405103). Files: 385420b7765f56c5e39a4b85724f4abb 813 admin optional refpolicy_0.0.20061018-3.dsc 734eb13417de2ee4acdc33a1ac110f45 51639 admin optional refpolicy_0.0.20061018-3.diff.gz 3f65268b7217d871d29d5da33eabb16f 1539792 admin optional selinux-policy-refpolicy-strict_0.0.20061018-3_all.deb 168e6eccdba11748ce4f955f26a4d17d 1289446 admin optional selinux-policy-refpolicy-targeted_0.0.20061018-3_all.deb b76bd0e81405fc734bf9d4e960dd17d2 593774 admin optional selinux-policy-refpolicy-src_0.0.20061018-3_all.deb 756623e0f77317e01a4cea14abbfebda 334912 doc optional selinux-policy-refpolicy-doc_0.0.20061018-3_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFq/tUIbrau78kQkwRAu+QAKCbuIHP0ZgtG82HpRh3aNMxNsoosQCg8txn Qiu881qXi2SYu3eOp6qCM0g= =ncN+ -----END PGP SIGNATURE-----
--- End Message ---
