>>> Installing (1 of 1) dev-libs/uthash-1.9.7 * 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/include/uthash.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-cluster/torque-4.1.5.1:0::gentoo * /usr/include/uthash.h ----------- sys-cluster/torque-4.1.5.1 was built with the following: USE="crypt (multilib) syslog -cpusets -doc -drmaa -munge -nvidia -server -tk" ABI_X86="64" Reproducible: Always
I'm going on a limb here and suggest that you should probably dep on dev-libs/uthash instead.
"fixed" for now. Patch submitted to upstream at https://github.com/adaptivecomputing/torque/pull/282 + 17 Oct 2014; Justin Bronder <jsbronder@gentoo.org> torque-4.1.5.1-r1.ebuild, + torque-4.1.7.ebuild, torque-4.2.9.ebuild: + Add blocker on dev-libs/uthash. Note that we should be just depending on it, + but do to how upstream ships the tarfile, we cannot patch the build system. + http://www.supercluster.org/pipermail/torquedev/2014-October/004773.html. + #490000 +
