I have recently installed Debian Squeeze Testing and since I recently moved from Ubuntu 10.10 Maverick Meerkat (which has 2.6.35), I wanted to install it in my Debian Squeeze (which has 2.6.32). However, compiling kernel is time consuming and tiresome, I decided to use the Ubuntu Kernel Mainline PPA like I always do. I navigated to the latest 2.6.37 directory (which is v2.6.37-rc1-maverick as of today) and downloaded the following files:
linux-headers-XXXXXX_all.deb
linux-headers-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)
linux-image-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)
Also, if you are not using Ubuntu, you may need to download wireless crda package from maverick packages.
After downloading, install in the following order (using dpkg or gdebi):
wireless-crda
linux-headers-XXXXXX_all.deb
linux-headers-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)
linux-image-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)

Continue Reading

Sometimes when you are using PPA repositories or mixing multiple repositories or using a Development version, you encounter a problem and some of your applications might be removed. I want to illustrate the problem with my current Ubuntu 10.10 Maverick Meerkat Alpha installation, which I use as the only OS in my computer. This is not recommended but since I have always managed to solve issues that come up due to development versions, I have mostly used development versions because I get to see the upcoming changes and report problems if anything that bothers me.
With the latest repositories list update, I got into a problem with Filezilla, because I have been using Lucid getdeb repo with my system and Filezilla is in their repo as well as the official repo. When I marked for the latest updates in Synaptic Package Manager, I could see that filezilla, amongst others, was in the package to be removed which was because the package filezilla-common was to be upgraded and the filezilla that was installed, and had no update, had dependency issues. I upgraded the package filezilla-common anyways and lost filezilla. Ideally, since I am using a development version, I should have marked all the changes, and then reviewed the list of programs that are to be removed and unmark them or mark them for reinstallation which automatically unmarks the conflicting updates. Since packages like gdm, gnome-panel and some others which are required for the system to boot properly into the desktop were also marked for removal, I marked them for re-installation or unmarked them so that they remained in the system. But for experimenting, I did not mark it and it got removed. Now, when I try to install the package, I get the error: Continue Reading