Elive

There’s a big problem with the updates of the system that will broke the graphical system, this bug has Critical severity

The problem is that, if you upgrade your system, it will update the GLX package of your ati/nvidia drivers, this means, that you will have a X version of the kernel with an ati (or nvidia) module in the version Y, that is incompatible with the updated version Z of the GLX package

To solve that problem, I have used all this time a block (hold mark) of the GLX package (the user should have the same kernel all the time)

But the problem is, for example, that if the user update the system that include an updated kernel, and an update of the ati kernel module, the GLX package for ati is not updated so it is incompatible and the user can’t reach the graphical system

Actual case: updated system: update the kernel, but the packages fglrx-driver, fglrx-glx and fglrx-kernel-2.3.26.8-elive-686 are holded, so not updated, the kernel can’t simply load that old version of the ati driver and the user can’t reach the graphical system

If we hold the packages, there’s the problem that everything needs to be updated (so, do not hold anything) in order to work correctly. But if we don’t lock them, also if the user upgrade the system, will use the same version of the kernel, so then the ati GLX package will be updated and not work with the old kernel/module, the only solution for that and everything is that update the version of the kernel too (with a virtual-package for example)... this was requested by some users but, it is a good idea ? what happens if a user dont want to update his kernel ? what about if a version of the kernel mades the computer of a user to NOT boot or not work ? and finally... the grub menu needs to be updated on that case then

Comments about this problematic issue ?