Re: preferences cahnges, once woddu becomes stable?
Sean is usually good but I had same impression as Vineet.
It is quite interesing topic. See http://bugs.debian.org/141495
and below experiment :)
On Thu, May 02, 2002 at 03:10:29PM -0700, Vineet Kumar wrote:
> * Sean 'Shaleh' Perry (shalehperry@attbi.com) [020502 08:24]:
> > >
> > > so I can yuse these "potato" "woody" "sid" in /etc/apt/preferences
> > >
> > > makes more sense
> > >
> > > a= Archive
> > > This is the common name we give our archives, such
> > > as stable or unstable. The special name now is used
> > > to designate the set of packages that are currently
> > > installed.
> > >
> > > I had an impression I can only use stable or unstable...
> >
> > if your apt line says 'woody' you can use woody, if it says testing you use
> > testing, etc.
>
> Are you sure about this? I've been running with my sources.list
> specifying release names but /etc/apt/preferences using 'states' (i.e.
> stable, testing, unstable). When I tried changing the latter to potato,
> woody, testing, and did apt-get -s dist-upgrade, I saw that it wanted to
> upgrade everything to the latest version. That means the pins didn't
> match, so it fell back to using version numbers to pick the preferred
> packages.
>
> In all my experience, the pins only work correctly if using "stable",
> "testing", "unstable": "potato", "woody", "sid", (and probably "sarge")
> just don't work.
I thought this was my experience few month ago.
> Please correct me if I'm wrong about this.
Let's experiment:
$ su -
..
# cd /etc/apt
# vim sources.list preferences
... s/unstable/sid/ s/testing/woody/ s/stable/potato/
# apt-get update
# apt-cache policy base-files
base-files:
Installed: 3.0.2
Candidate: 3.0.3
Version Table:
3.0.3 0
500 http://http.us.debian.org sid/main Packages
*** 3.0.2 0
500 http://http.us.debian.org woody/main Packages
100 /var/lib/dpkg/status
2.2.0 0
500 http://http.us.debian.org potato/main Packages
# cat preferences
Package: *
Pin: release a=woody
Pin-Priority: 800
Package: *
Pin: release a=sid
Pin-Priority: 70
# dpkg -l apt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii apt 0.5.4 Advanced front-end for dpkg
Well at least testing version of apt can not lock with "Pin: release a=sid".
lso does not look likeit will be able to.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki @ Cupertino CA USA
See "User's Guide": http://www.debian.org/doc/manuals/users-guide/
See "Debian reference": http://www.debian.org/doc/manuals/reference/
"Debian reference" Project at: http://qref.sf.net
I welcome your constructive criticisms and corrections.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: