Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 282803 Details for
Bug 378623
sec-policy/selinux-sasl and sec-policy/selinux-cyrus-sasl : file collision
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
selinux-sasl-2.20101213-r1 build.log
build.log (text/plain), 4.45 KB, created by
Andreis Vinogradovs ( slepnoga )
on 2011-08-10 09:38:25 UTC
(
hide
)
Description:
selinux-sasl-2.20101213-r1 build.log
Filename:
MIME Type:
Creator:
Andreis Vinogradovs ( slepnoga )
Created:
2011-08-10 09:38:25 UTC
Size:
4.45 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: sec-policy/selinux-sasl-2.20101213-r1 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: selinux@gentoo.org >[32;01m * [39;49;00mUSE: amd64 elibc_glibc kernel_linux multilib selinux userland_GNU >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox selinux sesandbox userpriv >>>> Unpacking source... >>>> Unpacking refpolicy-2.20101213.tar.bz2 to /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work > [32;01m*[0m Applying fix-services-sasl-r1.patch ... >[A[205C [34;01m[ [32;01mok[34;01m ][0m >>>> Source unpacked in /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work >>>> Compiling source in /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work ... >make -j4 -j1 NAME=strict -C /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work//strict >make: Entering directory `/var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work/strict' >Compiling strict sasl module >/usr/bin/checkmodule: loading policy configuration from tmp/sasl.tmp >/usr/bin/checkmodule: policy configuration loaded >/usr/bin/checkmodule: writing binary representation (version 13) to tmp/sasl.mod >Creating strict sasl.pp policy package >rm tmp/sasl.mod tmp/sasl.mod.fc >make: Leaving directory `/var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work/strict' >make -j4 -j1 NAME=targeted -C /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work//targeted >make: Entering directory `/var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work/targeted' >Compiling targeted sasl module >/usr/bin/checkmodule: loading policy configuration from tmp/sasl.tmp >/usr/bin/checkmodule: policy configuration loaded >/usr/bin/checkmodule: writing binary representation (version 13) to tmp/sasl.mod >Creating targeted sasl.pp policy package >rm tmp/sasl.mod tmp/sasl.mod.fc >make: Leaving directory `/var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/work/targeted' >>>> Source compiled. >>>> Test phase [not enabled]: sec-policy/selinux-sasl-2.20101213-r1 > >>>> Install selinux-sasl-2.20101213-r1 into /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/image/ category sec-policy > [32;01m*[0m Installing strict sasl policy package > [32;01m*[0m Installing targeted sasl policy package >>>> Completed installing selinux-sasl-2.20101213-r1 into /var/tmp/portage/sec-policy/selinux-sasl-2.20101213-r1/image/ > >./ >./usr/ >./usr/share/ >./usr/share/selinux/ >./usr/share/selinux/strict/ >./usr/share/selinux/strict/sasl.pp >./usr/share/selinux/targeted/ >./usr/share/selinux/targeted/sasl.pp >>>> Done. > [32;01m*[39;49;00m checking 2 files for package collisions >[31;01m * [39;49;00mThis package will overwrite one or more files that may belong to other >[31;01m * [39;49;00mpackages (see list below). You can use a command such as `portageq >[31;01m * [39;49;00mowners / <filename>` to identify the installed package that owns a >[31;01m * [39;49;00mfile. If portageq reports that only one package owns a file then do >[31;01m * [39;49;00mNOT file a bug report. A bug report is only useful if it identifies at >[31;01m * [39;49;00mleast two or more packages that are known to install the same file(s). >[31;01m * [39;49;00mIf a collision occurs and you can not explain where the file came from >[31;01m * [39;49;00mthen you should simply ignore the collision since there is not enough >[31;01m * [39;49;00minformation to determine if a real problem exists. Please do NOT file >[31;01m * [39;49;00ma bug report at http://bugs.gentoo.org unless you report exactly which >[31;01m * [39;49;00mtwo packages install the same file(s). Once again, please do NOT file >[31;01m * [39;49;00ma bug report unless you have completely understood the above message. >[31;01m * [39;49;00m >[31;01m * [39;49;00mDetected file collision(s): >[31;01m * [39;49;00m >[31;01m * [39;49;00m /usr/share/selinux/strict/sasl.pp >[31;01m * [39;49;00m /usr/share/selinux/targeted/sasl.pp >[31;01m * [39;49;00m >[31;01m * [39;49;00mSearching all installed packages for file collisions... >[31;01m * [39;49;00m >[31;01m * [39;49;00mPress Ctrl-C to Stop >[31;01m * [39;49;00m >[31;01m * [39;49;00msec-policy/selinux-cyrus-sasl-2.20101213 >[31;01m * [39;49;00m /usr/share/selinux/strict/sasl.pp >[31;01m * [39;49;00m /usr/share/selinux/targeted/sasl.pp >[31;01m * [39;49;00m >[31;01m * [39;49;00mPackage 'sec-policy/selinux-sasl-2.20101213-r1' NOT merged due to file >[31;01m * [39;49;00mcollisions. If necessary, refer to your elog messages for the whole >[31;01m * [39;49;00mcontent of the above message.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 378623
: 282803