I installed Gentoo/FreeBSD x86 inside a virtual machine yesterday and came across this issue where dev-util/dialog-1.1.20100428 has file collisions with sys-freebsd/freebsd-contrib-8.0. I would try fixing this in my virtual machine and then filing with the fix, but I am not sure about what is the correct way to resolve this. * 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/libdialog.a * /usr/include/dialog.h * /usr/share/man/man3/dialog.3.bz2 * /usr/lib/libdialog.so.7 * /usr/lib/libdialog.so * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-freebsd/freebsd-contrib-8.0 * /usr/include/dialog.h * /usr/lib/libdialog.a * /usr/lib/libdialog.so * /usr/lib/libdialog.so.7 * /usr/share/man/man3/dialog.3.bz2 * * Package 'dev-util/dialog-1.1.20100428' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message.
Is there a reason that freebsd-contrib installs a libdialog library? Is dev-util/dialog only usable on linux?
(In reply to comment #1) > Is there a reason that freebsd-contrib installs a libdialog library? Is > dev-util/dialog only usable on linux? their version differs; they made some additions needed by other freebsd programs; I've had no luck trying to port the freebsd programs to "standard" libdialog
I think it's safe to say any version of dev-util/dialog will collide.
I lost the virtual machine where I first identified this issue earlier this year in a hardware failure. I haven't had time to do a new installation since then. If anyone wants to do a new installation to examine this issue, there are some notes on the forums about how I did this earlier this year. They might be useful. http://forums.gentoo.org/viewtopic-t-861229.html
Should we drop the bsd keywords from dev-util/dialog then, or make the two packages involved block each other?
FreeBSD has since deprecated the version of the library which was provided in 8.0, and is using the same code as dev-util/dialog
The code seems quite different as of FreeBSD-8.x. It would be better to drop ~x86-fbsd from dev-util/dialog
Actually I was referring to current (9.0, etc). It's been using this version of dialog since April 2011. (That's much the same case as with ncurses).
(In reply to comment #5) > Should we drop the bsd keywords from dev-util/dialog then, or make the > two packages involved block each other? Preserve bsd keyword but add "!<=sys-freebsd/freebsd-contrib-8.9999" would solve this situation. I'll do the change in a week.
Block added. Thanks.
