Comment 5 for bug 1166230

Well, they are updated because their version number goes up with along with the related binary package. We theoretically should update it, in case the first version of such an oldlibs package didn't depend on exactly the right things or something. Seems unlikely, but we should do it.

We can't necessarily remove it because other packages are likely still depending on it. Until they are all cleaned up, we can't remove. At which point, it enters the "save to autoremove" list that apt-get generates. We might want to do something with those in update-manager, but that seems like a different bug.

We could say we will not show such updates, but silently update anyway. But we'd have to make sure the source was the Ubuntu archive, else malicious users could silently update packages. That would still solve most of the problem.