On Thu, Jan 12, 2006 at 09:54:50PM +0100, Hans wrote:
Clive Menzies wrote:
Good advice, thank you. I've been using Debian for seven years now,
mostly stable and since a year testing. My needs are not great: I can do
with stable for most packages, just the few I want fairly new (not
bleedig edge, otherwise I would install from source).
I've been happy with testing, and I understand the issues with it right
now. I really want to avoid the semi-broken state it is in now once it
happens again. I will check apt-listbugs, but my fear is that once I go
up to unstable I can't go back if that gets broken (which it will, one
day). You say that you use apt-listbugs to avoid a broken system or
installing packages with criticl bugs. What is your method of pinning
them down? Using "=" in dselect? (Sorry, I am stubborn: I learned to use
dselect when I started with Debian and I'm too lazy to learn something
new. dselect just works for me, so why change? :-)
On (11/01/06 22:52), Hans wrote:
For some time now many KDE-related packages are missing from testing
(eg. K3B, Rosegarden4, etc.). I really want to upgrade my
testing-system, so what is the best solution?
1) pin down packages in dselect, which are going to be deleted, with =,
then upgrade
2) use apt-pin and upgrade from testing/unstable
(http://jaqque.sbih.org/kplug/apt-pinning.html)
Read about apt pinning in apt_preferences(5) (really). You can often
downgrade to testing, except that there are lots of library
transitions happening recently. It might make sense to run testing,
but not update every package during such transitions.