Re: Verification of apt-get config for mixed system.
On Thu, 2003-01-23 at 10:57, Lloyd Zusman wrote:
> Dale Hair <dale@meridian-electric.com> writes:
>
> > On Thu, 2003-01-23 at 06:32, Lloyd Zusman wrote:
> >>
> >> [ ... ]
> >>
> >> Do I have it right?
> >>
> >> [ ... ]
> >
> > This should work but I don't pin individual packages on mine just the
> > distributions. Once a package is installed from unstable apt-get
> > upgrade or dist-upgrade will upgrade those from unstable and testing
> > will follow testing. My preferences file contains
> >
> > Package: *
> > Pin: release a=testing
> > Pin-Priority: 600
> >
> > Package: *
> > Pin: release a=unstable
> > Pin-Priority: 550
> >
> > I always use the -s option for apt-get dist-upgrade to show me what will
> > happen before I actually perform the upgrade. I use gnome from unstable
> > and for the past week dist-upgrade wants to remove gnome and a few
> > others so I used apt-get upgrade.
>
> OK. So I guess a better way to do what I want is to remove the pinned
> packages like you said, and then simply use "-t unstable" when
> installing a package that I'd like to get from that distribution. And
> from that time forward (unless I do a downgrade or fool around with my
> apt configuration), when I do an upgrade or an install, I'll always get
> those packages from "unstable" and the others from "testing".
>
> Is that correct?
>
>
> --
> Lloyd Zusman
> ljz@asfast.com
That is what I do, but as I said earlier a dist-upgrade could remove
some packages you want to keep so the -s option will tell you what it
will do before you regret doing it. A dist-upgrade is not always a wise
thing to do when you dabble in unstable.
I think pinning a package is more for keeping a package from being
upgraded. If you are running testing you could keep a package at
stable, or you could pin it to a specific version in testing.
--
Dale Hair <dale@meridian-electric.com>
Reply to: