Serafim Zanikolas <[EMAIL PROTECTED]> wrote: > Why does gcc-2.95 conflicts with gcc-doc? They don't share any > common files ... The same applies to gpc and gpc-doc (which i've > installed using ``dpkg -i --force-things conflicts gpc-doc''). > --snip-- <
I had the same problem on my DEC Alpha about 10 days ago. You can see the thread entitled "Compiler in "testing"" dated around 16 Dec 2001 on the Debian-Alpha Mailing list if you want the gory details. If I let the system (apt-get upgrade and/or dselect) do what it wanted to do, it would remove gcc-2.96-4 from my system! This is NOT what I wanted <g>. I don't know about the gpc-doc problem, but I would suspect it's conflict is similar. In my case the "gcc-doc" program was suggested by BOTH the obsolete "task-c-dev" and "task-devel-common" meta-packages. Both of these packages only "suggested" the gcc-doc package, but it was enough to overide the presence of gcc-2.95-4 on my system and force its removal. Anyway, when I removed BOTH the "task-c-dev" and "task-devel-common" meta-packages, things returned to normal. The bottom line is that the info in "gcc-doc" has been moved into the gcc version-specific "doc" file and you no longer need it (gcc-doc) on your system if you have the version-specific doc file installed. You also have to remove any obsolete "task" packages that might call for it. I had to do some sleuthing around to discover this. Cheers, -Don Spoon-
