On Wed, Aug 08, 2012 at 12:51:40AM -0400, Mathieu Trudel-Lapierre wrote: > On Tue, Aug 7, 2012 at 4:59 PM, Brian van den Broek > <[email protected]> wrote: > > You can work around that by installing packages from unstable directly > by including unstable in your sources.list; and using a technique > called pinning. See 'man apt_preferences' for the details... or ask on > the list, I'll be happy to share examples.
Don'tt really need pinning. It's possible to download the unstable package file from packages.debian.org and install it with dpkg. dpkg just installs the file you give it without asking many questions. And you don't have to shange your sources.list file. > > > So, I'm a bit confused about which to choose. Advice? > > Choose testing; if only because there's a slightly higher chance that > issues are caught while new packages are still in unstable and not yet > transitioned to testing. If you want something really safe though, > better stick with stable. It's not super old at this point, and there > will be a new Debian release eventually (like, reasonably soon, though > I can't say when). I use stable for my servers. I use testing for my desktop. I also use stable on my wife's machine. She doesn't like change. > > > As I've already downloaded a stable live CD, my plan was to install > > that, then update the repos to point at testing, and possibly once > > again to point at unstable. So, unless I misunderstand the way things > > work, I can try testing for a while and then go to unstable if > > desired. (I do understand that testing -> unstable is largely a > > one-way journey.) Does that install plan sound sound to those with > > experiencing running other than stable debian? > > Installing from stable and upgrading to testing or unstable should > work. I sometimes used that to install my debian system. But the new installer that's intended to be the installer for wheezy when it becomes stable is already available. They're eager to get people to try it out. I used it to install a testing system a month or two ago, and had no problems with it. Everything just worked. > You could run > into issues though, since the upgrading process from the current > stable version to what will be the new one hasn't necessarily all been > tested. It not only hasn't been thoroughly tested, they're still arguing about what to do about udev/kernel incompatibilities. It seems that they have to be upgraded in sync. And you can't talk to the upgrade process using screen (not that I would, anyway) -- apparently there's a change in protocol that can disrupt connexions. > If it's a new install, it should be fine. If you run stable > for a while before, install a bunch of packages, and upgrade to > testing/unstable then, you could have surprises. You can install testing directly. > > [1] - https://lists.debian.org/debian-devel-announce/2012/06/msg00009.html > > / Matt > _______________________________________________ > mlug mailing list > [email protected] > https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
