Debian Kept Back Packages
by unixform from LinuxQuestions.org on (#6CJD5)
Hi Everyone,
I am a Debian Testing user. In my sources.list I am tracking "testing" and not each Debian version by name.
As Debian 12 came around, Debian Testing systems underwent massive upgrades (and dist-upgrades).
In my system there are three packages that are being kept back for some weeks now:
libtbb12 , libtbbbind-2-5 , libtbbmalloc2
If I try "apt-get install libtbb12 libtbbbind-2-5 libtbbmalloc2" to upgrade to the new versions,
then the system will remove 16 libopencv* packages.
If I try "apt-get remove libtbb12", then the system will remove 20 libopencv* and mupen64plus* packages!
So, what must be done? Do I leave them as they are? As a Debian Testing user I dist-upgrade my system once a week. The general rule is that kept-back packages are not good for such a system.
Thanks!
I am a Debian Testing user. In my sources.list I am tracking "testing" and not each Debian version by name.
As Debian 12 came around, Debian Testing systems underwent massive upgrades (and dist-upgrades).
In my system there are three packages that are being kept back for some weeks now:
libtbb12 , libtbbbind-2-5 , libtbbmalloc2
If I try "apt-get install libtbb12 libtbbbind-2-5 libtbbmalloc2" to upgrade to the new versions,
then the system will remove 16 libopencv* packages.
If I try "apt-get remove libtbb12", then the system will remove 20 libopencv* and mupen64plus* packages!
So, what must be done? Do I leave them as they are? As a Debian Testing user I dist-upgrade my system once a week. The general rule is that kept-back packages are not good for such a system.
Thanks!