Re: Corrupt dpkg database? No kernels found
Hi Frans
On Dec 10, 5:00 pm, Frans Pop <elen...@planet.nl> wrote:
> If you really want to punish yourself, you could try to do a git-bisect
> using upstream kernel source to track down which change caused the
> regression. That is going to take quite a bit of time though.
My plan is to try each change made to the kernel between 2.6.18-5 and
2.6.18-6 in turn by checking out the appropriate revision in the debian
repository to see when it breaks. Hopefully, it is one of the early
changes :-)
Gordon
Reply to: