Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 306627 Details for
Bug 409669
www-client/firefox-11.0-r1 - ?
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
output terminal log
log (text/plain), 3.42 KB, created by
KinG-InFeT
on 2012-03-25 18:17:44 UTC
(
hide
)
Description:
output terminal log
Filename:
MIME Type:
Creator:
KinG-InFeT
Created:
2012-03-25 18:17:44 UTC
Size:
3.42 KB
patch
obsolete
>>>> Installing (5 of 5) www-client/firefox-11.0-r1 > * This package will overwrite one or more files that may belong to other > * packages (see list below). You can use a command such as `portageq > * owners / <filename>` to identify the installed package that owns a > * file. If portageq reports that only one package owns a file then do > * NOT file a bug report. A bug report is only useful if it identifies at > * least two or more packages that are known to install the same file(s). > * If a collision occurs and you can not explain where the file came from > * then you should simply ignore the collision since there is not enough > * information to determine if a real problem exists. Please do NOT file > * a bug report at http://bugs.gentoo.org unless you report exactly which > * two packages install the same file(s). Once again, please do NOT file > * a bug report unless you have completely understood the above message. > * > * Detected file collision(s): > * > * /usr/lib/firefox/plugins > * > * Searching all installed packages for file collisions... > * > * Press Ctrl-C to Stop > * > * None of the installed packages claim the file(s). > * > * Package 'www-client/firefox-11.0-r1' merged despite file collisions. > * If necessary, refer to your elog messages for the whole content of the > * above message. > * Updating desktop mime database ... > * Updating icons cache ... [ ok ] > >>>> Recording www-client/firefox in "world" favorites file... > > * Messages for package www-client/firefox-11.0-r1: > > * You are enabling official branding. You may not redistribute this build > * to any users on your network or the internet. Doing so puts yourself into > * a legal problem with Mozilla Foundation > * You can disable it by emerging firefox _with_ the bindist USE-flag > * Fallback PaX marking -m > * /var/tmp/portage/www-client/firefox-11.0-r1/work/mozilla-release/obj-i686-pc-linux-gnu/dist/bin/xpcshell > * Fallback PaX marking -m > * /var/tmp/portage/www-client/firefox-11.0-r1/image//usr/lib/firefox/firefox > * /var/tmp/portage/www-client/firefox-11.0-r1/image//usr/lib/firefox/firefox-bin > * /var/tmp/portage/www-client/firefox-11.0-r1/image//usr/lib/firefox/plugin-container > * This package will overwrite one or more files that may belong to other > * packages (see list below). You can use a command such as `portageq > * owners / <filename>` to identify the installed package that owns a > * file. If portageq reports that only one package owns a file then do > * NOT file a bug report. A bug report is only useful if it identifies at > * least two or more packages that are known to install the same file(s). > * If a collision occurs and you can not explain where the file came from > * then you should simply ignore the collision since there is not enough > * information to determine if a real problem exists. Please do NOT file > * a bug report at http://bugs.gentoo.org unless you report exactly which > * two packages install the same file(s). Once again, please do NOT file > * a bug report unless you have completely understood the above message. > * > * Detected file collision(s): > * > * /usr/lib/firefox/plugins > * > * Searching all installed packages for file collisions... > * > * Press Ctrl-C to Stop > * > * None of the installed packages claim the file(s). > * > * Package 'www-client/firefox-11.0-r1' merged despite file collisions. > * If necessary, refer to your elog messages for the whole content 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 409669
: 306627