Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 882205 Details for
Bug 922063
dev-build/meson-format-array-0 - [slibtool] file collision with dev-util/meson-format-array-0
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
dev-build:meson-format-array-0:20240113-203958.log
dev-build:meson-format-array-0:20240113-203958.log (text/plain), 2.63 KB, created by
Toralf Förster
on 2024-01-13 20:46:35 UTC
(
hide
)
Description:
dev-build:meson-format-array-0:20240113-203958.log
Filename:
MIME Type:
Creator:
Toralf Förster
Created:
2024-01-13 20:46:35 UTC
Size:
2.63 KB
patch
obsolete
> * Package: dev-build/meson-format-array-0:0 > * Repository: gentoo > * Maintainer: floppym@gentoo.org > * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_11 > * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox > >>>> Unpacking source... >>>> Source unpacked in /var/tmp/portage/dev-build/meson-format-array-0/work >>>> Preparing source in /var/tmp/portage/dev-build/meson-format-array-0/work ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-build/meson-format-array-0/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-build/meson-format-array-0/work ... >>>> Source compiled. >>>> Test phase [not enabled]: dev-build/meson-format-array-0 > >>>> Install dev-build/meson-format-array-0 into /var/tmp/portage/dev-build/meson-format-array-0/image > * python3_11: running python_doscript /var/tmp/portage/dev-build/meson-format-array-0/files/meson-format-array >>>> Completed installing dev-build/meson-format-array-0 into /var/tmp/portage/dev-build/meson-format-array-0/image > > * Final size of build directory: 0 KiB > * Final size of installed tree: 4 KiB > > > * checking 2 files for package collisions > * 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 https://bugs.gentoo.org/ unless you report exactly > * which two packages install the same file(s). See > * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how > * to solve the problem. And once again, please do NOT file a bug report > * unless you have completely understood the above message. > * > * Detected file collision(s): > * > * /usr/lib/python-exec/python3.11/meson-format-array > * /usr/bin/meson-format-array > * > * Searching all installed packages for file collisions... > * > * Press Ctrl-C to Stop > * > * dev-util/meson-format-array-0:0::gentoo > * /usr/bin/meson-format-array > * /usr/lib/python-exec/python3.11/meson-format-array > * > * Package 'dev-build/meson-format-array-0' NOT merged due to 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 922063
:
882204
| 882205 |
882206
|
882207
|
882208
|
882209
|
882210