Description of problem:
When installing tcl-devel 8.4 via yum, quite every single package is updated/
Version-Release number of selected component (if applicable):
Fedora 8 126.96.36.199-49.fc8
try install tcl-devel tcl-devel-8.4.15-5.fc8 via graphical yum interface (be
careful it will make your system unusable)
Steps to Reproduce:
1. Run graphical yum as root
2. search for tcl-devel tcl-devel-8.4.15-5.fc8
3. try to install it and see
System icons disappear, most apps are erased, cannot reboot to X server.
Just needed tcl-devel to compile 8Kingdoms game.
After reboot got message id 'X' respawning too fast...
btw. programs like firefox are erased
Sorry i'm not trying to flood, but here's some info that might be important
about the Fedora installation i had that made up that bug:
- Fedora 8 with gnome, without any KDE or server package, developpment packages
were installed, still wonder why tcl-devel package was missing actually.
I guess if i've had installed whole Fedora DVD the tcl-devel package would
already have been there and thus not erased half of my system (sorry can't give
better explanation, being noob :) But i still wonder what would happen if
someone updates his tcl & tcl-devel packages on F8.
which graphical yum interface did you use? Can you check your /var/log/yum.log
and look for the date stamp of this? I'm curious what was in the transaction.
(In reply to comment #3)
> which graphical yum interface did you use? Can you check your /var/log/yum.log
> and look for the date stamp of this? I'm curious what was in the transaction.
Already reinstalled, sorry. Btw tried to reinstall tcl-devel, this time it
okay well, I can't recreate this and that makes this a bit impossible to debug.
(In reply to comment #5)
> okay well, I can't recreate this and that makes this a bit impossible to debug.
Deajan again, i had the same bug while installing jack-audioconnection-kit
This time, i kept the installation so i'd like you to re-examine that case by
supplying the /var/log/yum.log file. Could you please tell me if you will handle
the yum log file won't really help but sure, attach it.
Closing due to inactivity; please reopen if you continue to see this problem or
have more information to add to this report