What I often do is backport myself. Add a deb-src line from testing or unstable to the stable
machine then do
apt-get build-dep package-foo
(any libraries or other tools complained about in this step need to be backported as well.
This
process can get a bit recursive. If it turns out I'm going to be building 4 or 5 support
libraries or
worse then I won't bother.)
mkdir package-foo
cd package-foo
apt-get source package-foo
cd package-foo-<version #>
dpkg -rfakeroot -b
dpkg -i ../package-foo-<ver#).deb
Posted Aug 9, 2008 5:09 UTC (Sat) by undefined (guest, #40876)
[Link]
may i also recommend pbuilder which makes backporting easier by providing an easy-to-manage
pristine chroot environment for building packages.
using pbuilder on my testing/"lenny" desktop, i backport applications for servers running
stable/"etch" and even desktops running ubuntu hardy/8.04.
i also use apt-proxy for caching packages for both pbuilder and other machines, but it's not
that specific to backporting or pbuilder.