dubois wrote:A question though: is the default pinning set up during a Debian netinst sufficient if backports is uncommented even though that set up didn't create a file in /etc/apt/preferences or /etc/apt/apt.conf or would it be better, would my system be safer, if I create those files?? How should they look??
It is quite sufficient. in case of a regular netinstall, the default value for either Stable or Testing (depending what installer you used) get a priority of 500. This is handled by the release file or something, I'm not a 100 percent sure, dpkg is a cryptic beast.
Packages from backports get a priority of 100, so they won't conflict with the squeeze packages. Other third party repos vary. Debian multimedia packages get a priority of 500 as well, so they will get a priority over the stable packages, which is what you want really most of the time. Check this out, it's from a Squeeze install with backports and Multimedia added:
lekoraco@mrdeb ~ % apt-cache policy mplayer
mplayer:
Installed: 2:1.0~rc3++svn20100804-0.2squeeze1
Candidate: 2:1.0~rc3++svn20100804-0.2squeeze1
Version table:
2:1.0~rc4.dfsg1+svn33713-2~bpo60+1 0
100 http://backports.debian.org/debian-backports/ squeeze-backports/main amd64 Packages
*** 2:1.0~rc3++svn20100804-0.2squeeze1 0
500 http://www.debian-multimedia.org/ squeeze/main amd64 Packages
100 /var/lib/dpkg/status
2:1.0~rc3++final.dfsg1-1 0
500 http://ftp.de.debian.org/debian/ squeeze/main amd64 Packages
Look at the values - 100 for bpo, 500 for squeeze and multimedia.
When you add a default release in apt.conf, it gets a value of 990 - that's the case with packages from Statler on a regular #! install. In your case, if you plan to use Debian Stable as the base and add the Statler packages, declare Statler as the default release in apt.conf, don't even make a preferences file, and you're good to go. The main reason for the problems in #!, ie. backports upgrading everything they come into contact with, is the fact that Squeeze got a pin value of 100 in preferences.