Apt-pinning / checkinstall to remedy fatsort bug

Background:

The "fatsort" version in testing/unstable has a grievous bug. The bug does not exist in the version in stable, and the bug has been corrected in the latest release from the developers, which has not made its way into testing or unstable.

I am running Debian testing with a few unstable packages under a 2.6.26-3 kernel that I have custom-compiled via the kernel-package/linux-kbuild packages.

Current solution:

I added the following to /etc/apt/preferences:

Package: fatsort
Pin: release a=stable
Pin-Priority: 1000

and it seems to be working to keep the fatsort package at the appropriate version.

Question:

I am thinking of compiling the sources from the developer via checkinstall.

Does anyone know of any reason why I shouldn't go this route?

Thank you for your time.

0
Syndicate content