Package: wajig Version: 2.0.37 Followup-For: Bug #385318 Actually, install/<DISTRIBUTION> works fine, but only if you have that distribution in your /etc/apt/sources.list. Maybe it's worth explaining that somewhere in the documentation. It's also probably worth explaining the use of pinning to make sure that you don't simply get the newest packages all the time (in which case you may as well run unstable).
I'm not sure if there's an official Debian document on this subject; I found a useful page at http://jaqque.sbih.org/kplug/apt-pinning.html My only reservation is the suggestion that you can usefully mix stable, testing and unstable, which is fine until the first libc transition after stable is released. I run testing with some unstable and occasionally experimental mixed in, which is a bit more workable. Anyway, you can close this bug. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wajig depends on: ii apt 0.7.6 Advanced front-end for dpkg ii dselect 1.14.6 user tool to manage Debian package ii python 2.4.4-6 An interactive high-level object-o ii python-apt 0.7.3.1 Python interface to libapt-pkg ii python-central 0.5.15 register and build utility for Pyt wajig recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
