* Messages for package dev-ruby/bcat-0.6.2: * 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/bin/bcat * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-accessibility/speech-tools-2.1-r1 * /usr/bin/bcat * * Package 'dev-ruby/bcat-0.6.2' NOT merged due to file collisions. ...
I've now made this explicit in the dev-ruby/bcat ebuild by adding a blocker. Leaving the bug open until we have a more permanent solution.
The /usr/bin/bcat in app-accessibility/speech-tools doesn’t do anything much: :; bcat --help Usage: bcat -o [ofile] [files...] Summary; concatenate files in binary mode -o <ofile> Ouptut file of binary data bcat_main.cc says: /* A simple file concatenator which does everything in binary */ /* mode. For use in the tests on Windows etc. */ It shouldn’t be installed. The speech-tools ebuild should elide /usr/bin/bcat (and /usr/lib64/speech-tools/bcat?) and the dev-ruby/bcat can then remove the blocker.
Re-assigning to the speech-tools maintainers since the initial action is there. Please assign back to ruby once this is fixed in speech-tools.
Here's what the bcat source from speech_tools has to say about the program: /** bcat is a trivial file concatenation program. It exists to allow testing of various file splitting operations under the cygwin environment on Windows where the distinction between binary and text data is important. */ So basically, it's a cat program that can concatenate binary files under Cygwin. And it's only used for testing purposes? I wonder why it is even installed on Linux. Maybe we can just remove the binary in src_install?
(In reply to Chris Brannon from comment #4) > So basically, it's a cat program that can concatenate binary files under > Cygwin. Do note that cat from GNU coreutils is perfectly capable of concatenating binary files. Even POSIX cat doesn't offer any opinion on the contents of the files you concatenate. > And it's only used for testing purposes? I wonder why it is > even installed on Linux. Maybe we can just remove the binary in > src_install? Yes we can.
bcat has been removed from 2.1-r3. Reassigning to ruby, so they can remove their blocker.
I have updated the blockers in dev-ruby/bcat to only block on the old speech-tools versions that are not fixed.
