I have uninstalled tetex and am install texlive per http://www.gentoo.org/proj/en/tex/texlive-migration-guide.xml and up to the emerge of texlive. The first package to emerge is t1utils and this fails to install due to a file collission with freetype-1.3.1-r3. Reproducible: Always Steps to Reproduce: 1. emerge t1utils Actual Results: >>> Installing app-text/t1utils-1.34 * checking 14 files for package collisions * 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/t1asm * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * media-libs/freetype-1.3.1-r3 * /usr/bin/t1asm * * Package 'app-text/t1utils-1.34' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. >>> Failed to install app-text/t1utils-1.34, Log file: >>> '/var/tmp/portage/app-text/t1utils-1.34/temp/build.log' Expected Results: emerge correctly
The last freetype-1.3 ebuild has been removed from portage about three months ago: http://sources.gentoo.org/viewcvs.py/gentoo-x86/media-libs/freetype/ Does this also happen with the current freetype-1 package?
1.4* ebuilds do not install t1asm. Aballier: Not much left to do here, we can't add blockers to purged ebuilds. Do you want to add against <media-libs/freetype-1.4_pre20080316 in t1utils?
So, am I to understand that I have to uninstall freetype-1.3 to get t1utils to isntall? Or do I just need to upgrade freetype-1.3 to freetype-1.4xxx?
(In reply to comment #3) > So, am I to understand that I have to uninstall freetype-1.3 to get t1utils to > isntall? Or do I just need to upgrade freetype-1.3 to freetype-1.4xxx? Yup. Upgrade to 1.4: emerge -1 =freetype-1.4_pre20080316-r1:1
Upgrading to 1.4 works for t1utils. I now have texlive installed with no further issues. Thanks!
Hold on there, cowboy. The developer closes the bug, not the reporter :-). What you just performed was a workaround. The dev decides in borderline cases like this whether there is a bug.
Ok, ok, ok. Sorry, I did not mean to step on any toes. I guess that was a workaround after all even thought for me it was a solution.
I guess portage/emerge should have pulled the dependeny for freetype to upgrade it and it did not. That does need to get fixed.
(In reply to comment #2) > Aballier: Not much left to do here, we can't add blockers to purged ebuilds. Do > you want to add against <media-libs/freetype-1.4_pre20080316 in t1utils? added, thanks
