Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 886156 Details for
Bug 925538
app-admin/bitwarden-desktop-bin-2024.2.0 collides with net-im/slack-4.36.140
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
bitwarden-desktop-bin build.log
build.log (text/x-log), 7.11 KB, created by
Antonio Quartulli
on 2024-02-28 10:45:04 UTC
(
hide
)
Description:
bitwarden-desktop-bin build.log
Filename:
MIME Type:
Creator:
Antonio Quartulli
Created:
2024-02-28 10:45:04 UTC
Size:
7.11 KB
patch
obsolete
>[32m * [39;49;00mPackage: app-admin/bitwarden-desktop-bin-2024.2.0:0 >[32m * [39;49;00mRepository: gentoo >[32m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux >[32m * [39;49;00mFEATURES: network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox >>>> Unpacking source... >>>> Unpacking Bitwarden-2024.2.0-amd64.deb to /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/work >>>> Source unpacked in /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/work >>>> Preparing source in /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/work ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/work ... >>>> Source compiled. >>>> Test phase [not enabled]: app-admin/bitwarden-desktop-bin-2024.2.0 > >>>> Install app-admin/bitwarden-desktop-bin-2024.2.0 into /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image >>>> Completed installing app-admin/bitwarden-desktop-bin-2024.2.0 into /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image > > [32m*[0m Final size of build directory: 293256 KiB (286.3 MiB) > [32m*[0m Final size of installed tree: 293000 KiB (286.1 MiB) > >strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version > /opt/Bitwarden/libEGL.so > /opt/Bitwarden/chrome-sandbox > /opt/Bitwarden/libffmpeg.so > /opt/Bitwarden/chrome_crashpad_handler > /opt/Bitwarden/bitwarden > /opt/Bitwarden/libGLESv2.so > /opt/Bitwarden/libvk_swiftshader.so > /opt/Bitwarden/libvulkan.so.1 > /opt/Bitwarden/resources/app.asar.unpacked/node_modules/@bitwarden/desktop-native/desktop_native.linux-x64-musl.node >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/libEGL.so: debuglink section already exists >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/libffmpeg.so: debuglink section already exists >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/chrome_crashpad_handler: debuglink section already exists >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/libvk_swiftshader.so: debuglink section already exists >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/libGLESv2.so: debuglink section already exists >x86_64-pc-linux-gnu-objcopy: /var/tmp/portage/app-admin/bitwarden-desktop-bin-2024.2.0/image/opt/Bitwarden/bitwarden: debuglink section already exists > [32;01m*[39;49;00m checking 108 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 https://bugs.gentoo.org/ unless you report exactly >[31;01m * [39;49;00mwhich two packages install the same file(s). See >[31;01m * [39;49;00mhttps://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how >[31;01m * [39;49;00mto solve the problem. And once again, please do NOT file a bug report >[31;01m * [39;49;00munless 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/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff >[31;01m * [39;49;00m /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762 >[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;00mnet-im/slack-4.36.140:0::gentoo >[31;01m * [39;49;00m /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff >[31;01m * [39;49;00m /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2.debug >[31;01m * [39;49;00m /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0 >[31;01m * [39;49;00m /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0.debug >[31;01m * [39;49;00m >[31;01m * [39;49;00mPackage 'app-admin/bitwarden-desktop-bin-2024.2.0' NOT merged due to >[31;01m * [39;49;00mfile collisions. If necessary, refer to your elog messages for the >[31;01m * [39;49;00mwhole 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 925538
: 886156