| 1 |
Keith Jackson <kjackson@×××××××××××.com> posted |
| 2 |
4A32DC99.7050208@×××××××××××.com, excerpted below, on Fri, 12 Jun 2009 |
| 3 |
15:54:17 -0700: |
| 4 |
|
| 5 |
> * Messages for package dev-texlive/texlive-latex-2008-r1: |
| 6 |
|
| 7 |
> * This package will overwrite one or more files that may belong to |
| 8 |
> * other packages (see list below). |
| 9 |
> * |
| 10 |
> * Detected file collision(s): |
| 11 |
> * |
| 12 |
> * /var/lib/texmf/ls-R |
| 13 |
> * |
| 14 |
> * Searching all installed packages for file collisions... * |
| 15 |
> * Press Ctrl-C to Stop |
| 16 |
> * |
| 17 |
> * dev-texlive/texlive-basic-2008 |
| 18 |
> * /var/lib/texmf/ls-R |
| 19 |
|
| 20 |
> So is there anything I can do about this? Am I correct in understanding |
| 21 |
> there is a collision in texlive-basic and texlive-latex? |
| 22 |
|
| 23 |
I'm not a tex user, but I use portage, and yes, your understanding looks |
| 24 |
correct. |
| 25 |
|
| 26 |
Some quick comments that may or may not help: |
| 27 |
|
| 28 |
1) There's a Gentoo TeX Live 2008 Guide, here: |
| 29 |
|
| 30 |
http://www.gentoo.org/proj/en/tex/texlive-migration-guide.xml |
| 31 |
|
| 32 |
Looking over the guide, a good part of it is about getting old versions |
| 33 |
uninstalled as apparently there's problems with that. Thus, particularly |
| 34 |
if you've had earlier versions of tex/texlive installed and you're not |
| 35 |
already doing so, read and follow the guide. |
| 36 |
|
| 37 |
(FWIW, I found the guide mentioned on this bug, while doing a quick bug |
| 38 |
check to see if the bug has already been reported. I didn't your current |
| 39 |
bug bug, but the dev comment in this bug stresses the importance of |
| 40 |
following the guide BEFORE the upgrade if you've had a previous install, |
| 41 |
because apparently otherwise it gets a bit messy. |
| 42 |
http://bugs.gentoo.org/show_bug.cgi?id=266305#c1 ) |
| 43 |
|
| 44 |
2) Sometimes with package collisions, the conflicting package may have |
| 45 |
already been updated to remove the conflict, possibly without a revision |
| 46 |
bump. Thus, remerging the other package and trying again sometimes works. |
| 47 |
|
| 48 |
3) If you've been smart, you're running with FEATURES=buildpkg, and as |
| 49 |
the binpkg is created before actually trying the installation, even if it |
| 50 |
didn't get installed due to the collision, the binpkg was already |
| 51 |
created. It's thus often possible to skip the build stages and simply |
| 52 |
emerge -k the binpkg once you take care of the collision (by deleting the |
| 53 |
file if you decide it's safe, or if rebuilding the other package took |
| 54 |
care of it). |
| 55 |
|
| 56 |
4) If the file's a config file, script, or otherwise human readable, you |
| 57 |
can compare the various versions (what's installed compared against the |
| 58 |
version in each of the binpkgs -- binpkgs are simply bzip2-ed tarballs |
| 59 |
with some extra data tacked on the end so you can open them in your usual |
| 60 |
tarball browsing utility and/or extract individual files manually) to |
| 61 |
figure out if you can safely overwrite it or if they are too different. |
| 62 |
Of course, for icons and the like it's also a fairly simple choice, but |
| 63 |
it may not be so for say binary executables, etc. |
| 64 |
|
| 65 |
5) If you aren't using FEATURES=buildpkg, you can at least check the |
| 66 |
installed version against the version in the the fake-install dir where |
| 67 |
portage put it previous to trying to merge to the live system. |
| 68 |
|
| 69 |
6) Again if you're using buildpkg and have the other package as a binpkg, |
| 70 |
even if the colliding files are different it's reasonably safe to simply |
| 71 |
delete the existing colliding version (assuming it's not a config file |
| 72 |
you've spent a lot of time modifying, or something system-critical like |
| 73 |
part of glibc), since if they're not functionally the same and you need |
| 74 |
the other one, you can always extract the old version from the binpkg |
| 75 |
tarball if you decide you need it. |
| 76 |
|
| 77 |
This of course is part of what I'm talking about all those times when I |
| 78 |
mention how nice binpkgs are for troubleshooting and the like, and why I |
| 79 |
call FEATURES=buildpkg my favorite under-advertised portage power-user |
| 80 |
feature. =:^) |
| 81 |
|
| 82 |
7) You can also avoid the collision being fatal (with portage then |
| 83 |
overwriting the colliding files) by using FEATURES=-collision_protect |
| 84 |
emerge <pkg>. (I don't remember if this works with the binpkg or not, |
| 85 |
however, as I'm not sure if portage will let you modify the features it |
| 86 |
was built with for installation, and I've only had a few collision- |
| 87 |
protects to worry about.) It'll still warn about the collision, but |
| 88 |
it'll go ahead and install anyway if collision-protect is off. |
| 89 |
|
| 90 |
-- |
| 91 |
Duncan - List replies preferred. No HTML msgs. |
| 92 |
"Every nonfree program has a lord, a master -- |
| 93 |
and if you use the program, he is your master." Richard Stallman |
Archives