Re: 400+ unwanted package removal
On Tue, May 18, 2004 at 01:28:41PM +0100, John Stevenson wrote:
> >did you run dselect after this? isn't it that dselect re-resolved
> >package dependencies and set those packages that you changed to install
> >back to deinstall?
> >
> >i would try to deselect those new packages (those which selection for
> >install started that problem) using dselect until it doesn't want to
> >remove anything - if that is possible... but maybe you already tried...
> >
> >
> The trouble is that I dont have a list of the packages I initially
> installed with Aptitude and was not aware that you could find out what
> has been installed recently.
>
> Trying the dpkg --get/set-selections did not change dselects mind about
> uninstalling packages. I have check some of the list of packages for
> those packages that dselect wants to remove, they are now set to install.
>
> So it seems that something else is telling dselect to remove packages
> when I choose Install.
>
> I am just running apt-get upgrade and it does not seem to want to remove
> any packages, but will install a few new version of already installed
> packages (I am running the unstable distro).
>
> I will see what happens with dselect after the apt-get upgrade.
Have you done a dselect update? No doubt you are familiar with dselect,
but it seemed to me in the few times that I used dselect that it didn't
read apt-get's database. I'd have to do a dselect update before it
would work. If you haven't done so, perhaps the dependencies of the
packages have changed so that this is the reason dselect wants to remove
them.
Reply to: