| View previous topic :: View next topic |
| Author |
Message |
Nreal
Apprentice
Joined: 06 Jan 2009
Posts: 266
|
 Posted: Sat Mar 23, 2024 10:13 am Post subject: File collision /usr/lib64/libthrift.so |
 |
|
What can I do with this collision?
mariadb, apache-arrow and dev-libs/thrift?
| Code: | >>> Failed to install dev-libs/thrift-0.16.0-r2, Log file:
>>> '/var/tmp/portage/dev-libs/thrift-0.16.0-r2/temp/build.log'
* Messages for package dev-libs/thrift-0.16.0-r2:
* 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/lib64/libthrift.so
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* dev-db/mariadb-10.6.17:10.6::gentoo
* /usr/lib64/libthrift.so
*
* Package 'dev-libs/thrift-0.16.0-r2' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of the
* above message.
* GNU info directory index is up-to-date.
!!! existing preserved libs:
>>> package: dev-libs/thrift-0.16.0-r2
* - /usr/lib64/libthrift.so.0.16.0
* used by /usr/lib64/libparquet.so.1500.2.0 (dev-libs/apache-arrow-15.0.2)
Use emerge @preserved-rebuild to rebuild packages using these libraries
|
| Code: |
[ebuild R ] dev-db/mariadb-10.6.17:10.6/18::gentoo USE="backup columnstore extraengine galera innodb-lz4 innodb-lzo innodb-snappy jdbc jemalloc kerberos latin1 numa odbc oqgraph pam perl profiling s3 server xml -bindist -cracklib -debug (-mroonga) -rocksdb (-selinux) -sphinx -sst-mariabackup -sst-rsync -static -systemd -systemtap -tcmalloc -test -yassl" 0 KiB |
| Code: | [ebuild N ] dev-libs/thrift-0.16.0-r2::gentoo USE="ssl -libevent -lua -test" 0 KiB
[ebuild R ~] dev-libs/apache-arrow-15.0.2:0/15::gentoo USE="brotli bzip2 compute dataset json parquet re2 snappy ssl zlib zstd -lz4 -test" 0 KiB |
| Code: | | [ebuild N ] dev-libs/thrift-0.16.0-r2::gentoo USE="ssl -libevent -lua -test" 0 KiB |
|
|
| Back to top |
|
 |
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 223
Location: Zedelgem Belgium
|
| Posted: Sat Mar 23, 2024 1:36 pm Post subject: Re: File collision /usr/lib64/libthrift.so |
|
|
| Nreal wrote: | You can use a command such as `portageq
owners / <filename>` to identify the installed package that owns a
file. |
|
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21640
|
| Posted: Sat Mar 23, 2024 3:17 pm Post subject: Re: File collision /usr/lib64/libthrift.so |
|
|
| Nreal wrote: | | What can I do with this collision? |
Determine if it is real. If it is real, report it as a bug. Note also the big banner from Portage telling you this, and when not to report it. Incidentally, this was already reported as dev-libs/thrift-0.16.0-r1 - file collision with dev-db/mariadb-10.6.8-r1, which I found by using quick search for thrift. This suggests it is a real bug, and does not need another report. | Nreal wrote: | | Code: | >>> Failed to install dev-libs/thrift-0.16.0-r2, Log file:
* Detected file collision(s):
*
* /usr/lib64/libthrift.so
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* dev-db/mariadb-10.6.17:10.6::gentoo
* /usr/lib64/libthrift.so |
|
=dev-db/mariadb-10.6.17 previously installed /usr/lib64/libthrift.so. Now dev-libs/thrift-0.16.0-r2 wants to install the same file. This is not allowed. | Nreal wrote: | | Code: | !!! existing preserved libs:
>>> package: dev-libs/thrift-0.16.0-r2
* - /usr/lib64/libthrift.so.0.16.0
* used by /usr/lib64/libparquet.so.1500.2.0 (dev-libs/apache-arrow-15.0.2) |
|
This is incidental noise, and can be ignored here. | linux_os2 wrote: | | Nreal wrote: | You can use a command such as `portageq
owners / <filename>` to identify the installed package that owns a
file. |
|
Yes, or OP can rely on the output that Portage itself provided when it reported the ownership further down. I think OP wants to know whether to (a) delete the file, (b) file a bug report, (c) change some configuration to avoid this. |
|
| Back to top |
|
|
Nreal
Apprentice
Joined: 06 Jan 2009
Posts: 266
|
| Posted: Sat Mar 23, 2024 5:51 pm Post subject: Re: File collision /usr/lib64/libthrift.so |
|
|
| Hu wrote: | | Nreal wrote: | | What can I do with this collision? |
Determine if it is real. If it is real, report it as a bug. Note also the big banner from Portage telling you this, and when not to report it. Incidentally, this was already reported as dev-libs/thrift-0.16.0-r1 - file collision with dev-db/mariadb-10.6.8-r1, which I found by using quick search for thrift. This suggests it is a real bug, and does not need another report. | Nreal wrote: | | Code: | >>> Failed to install dev-libs/thrift-0.16.0-r2, Log file:
* Detected file collision(s):
*
* /usr/lib64/libthrift.so
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* dev-db/mariadb-10.6.17:10.6::gentoo
* /usr/lib64/libthrift.so |
|
=dev-db/mariadb-10.6.17 previously installed /usr/lib64/libthrift.so. Now dev-libs/thrift-0.16.0-r2 wants to install the same file. This is not allowed. | Nreal wrote: | | Code: | !!! existing preserved libs:
>>> package: dev-libs/thrift-0.16.0-r2
* - /usr/lib64/libthrift.so.0.16.0
* used by /usr/lib64/libparquet.so.1500.2.0 (dev-libs/apache-arrow-15.0.2) |
|
This is incidental noise, and can be ignored here. | linux_os2 wrote: | | Nreal wrote: | You can use a command such as `portageq
owners / <filename>` to identify the installed package that owns a
file. |
|
Yes, or OP can rely on the output that Portage itself provided when it reported the ownership further down. I think OP wants to know whether to (a) delete the file, (b) file a bug report, (c) change some configuration to avoid this. |
So the bug has been reported, All right, thank you! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
