I accidentally installed lenny's linux-image/linux-header packages and I'm running Squeeze. What to do?
Hello,
Basically what happened was I did sudo aptitude update && sudo
aptitude upgrade and I hit 'Y' to accept the packages being installed.
Only afterwards did I realise it would be installing packages from
Lenny. I tried to hit ctrl-c and ctrl-d to abort aptitude but this
didn't seem to work.
To give more information, I am running Squeeze amd64. I have not
rebooted since these packages were installed.
In my /etc/apt/sources.list I had Lenny repositories on lines below
the Squeeze lines. I had done this a while ago on the advice on some
webpage. I believe the idea was that if a package wasn't found in
Squeeze, aptitude would fall back to the Lenny repositories. So
packages from Lenny would only be used if those packages were not
found in Squeeze. There was a particular package I wanted from Lenny
at the time and this seemed like a reasonable way to install it (I do
not remember what that package was).
Assuming the advice about multiple repositories in sources.list was
correct, I wonder why the linux-image packages were installed from
Lenny? I think it may be because the Squeeze amd64 repository was for
some reason (perhaps my mirror dropped it?) not accessible (when
update was run, it gave Err on that line), so the Lenny repositories
were considered the most relevant by aptitude. This is only a guess,
without really knowing how it is supposed to work.
I have tried to rectify the situation by commenting out the Lenny
lines in sources.list , adding additional Squeeze lines to
sources.list (to remedy the potential of the first mirror being down),
then doing aptitude update and aptitude upgrade. I have also performed
aptitude reinstall linux-image-amd64 . I do not think anything was
installed because I did not see aptitude do anything after it had
grabbed and unpacked the packages.
Here is the output of a few commands to show you the current state of my system:
$ cat /var/log/dpkg.log* | grep "linux\-" |grep "\ installed" |sort
2012-03-22 19:36:00 status installed linux-image-2.6.26-2-amd64 2.6.26-29
2012-03-22 19:36:08 status installed linux-headers-2.6.26-2-amd64 2.6.26-29
2012-03-22 19:36:08 status installed linux-headers-2.6.26-2-common 2.6.26-29
2012-03-22 20:46:54 status installed linux-image-amd64 2.6.32+29
$ aptitude search linux-headers |grep '^i'
i A linux-headers-2.6-amd64 - Header files for Linux amd64 configuration
i A linux-headers-2.6.26-2-amd64 - Header files for Linux 2.6.26-2-amd64
i A linux-headers-2.6.26-2-common - Common header files for Linux 2.6.26-2
i A linux-headers-2.6.32-5-amd64 - Header files for Linux 2.6.32-5-amd64
i A linux-headers-2.6.32-5-common - Common header files for Linux 2.6.32-5
$ aptitude search linux-image |grep '^i'
i linux-image-2.6.26-2-amd64 - Linux 2.6.26 image on AMD64
i A linux-image-2.6.32-5-amd64 - Linux 2.6.32 for 64-bit PCs
i linux-image-amd64 - Linux for 64-bit PCs (meta-package)
$ uname -mrs
Linux 2.6.32-5-amd64 x86_64
Any help or explanation would be greatly appreciated!
Thanks,
Alex
Reply to: