[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Removing "unstable" package sets

On Thu, 2003-01-02 at 14:08, James Walker wrote:
> Hi,
> I hope this is the appropriate mailing list, please correct me if it is not.
> I recently, rather unthinkingly, added an "unstable" set to my apt sources 
> list.
> The next time I ran dpkg it of course found a heap of "upgrades" and 
> proceeded to update my system with a large bunch of unstable packages.
> Luckily, thus far, the packages have caused no problem at all.

As long as you don't have a mission-critical system, I would recommend
running sarge/testing and just wait until the versioning has caught up
with your installed set of packages. If you have problems, you can
always try to downgrade just the offending package - but downgrading
everything (especially libc) is probably more dangerous than just
running the new version.

Recommended read if you're dealing with this: the apt_preferences
manpage. If you understand everything in there, you understand most of
the Debian packaging system (from a users perspective, that is).

I have, in /etc/apt/preferences:
Package: *
Pin: release a=testing
Pin-Priority: 700

Package: *
Pin: release a=stable
Pin-Priority: 600

and I have all stable, testing and unstable sources in my sources.list.
Obviously, I run mostly run testing. As an addition, some people like
having unstable at very low priorities (<100? or even <0? IIRC there's
some magic value somewhere down there).

-- vbi

featured link: http://fortytwo.ch/gpg/subkeys

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: