Thanks for the replies.
So I've edited /etc/apt/preferences such:
stuckey@debian:~$ cat /etc/apt/preferences
Package: *
Pin: origin www.debian-multimedia.org
Pin-Priority: 200
And now, when I do "apt-cache policy mplayer" I get:
debian:/home/stuckey# apt-cache policy mplayer
mplayer:
Installed: (none)
Candidate: 1.0~rc3+svn20090405-1+b1
Version table:
1:1.0.rc2svn20100219-0.0 0
200 http://www.debian-multimedia.org sid/main Packages
1.0~rc3+svn20090405-1+b1 0
500 http://ftp.de.debian.org unstable/main Packages
1.0~rc3+svn20090405-1 0
100 /var/lib/dpkg/status
I assume that means that when I just removed it, and then reinstalled
it, that it took it from ftp.de.debian.org.
So with such a configuration, how can I tel it that I want to install
mplayer from debian-multimedia?
Gruesse,
Stuckey
Quoting Andrei Popescu <andreimpopescu@gmail.com>:
On Sun,21.Feb.10, 23:00:25, Freeman wrote:
Nevertheless, my read is that if you install one of Marillat's sid packages,
it will be 1.) a higher version of the 2.) same release from the 3.)
Multimedia distribution.
If you set your target release as described to unstable, unstable packages
from the debian distribution will receive a priority of 990. That will not
allow an automatic upgrade to a different distribution (Multimedia) but it
also will not allow an automatic downgrade from a higher release.
Only debian-multimedia is not a different distribution, just a different
source:
$ apt-cache policy mplayer
mplayer:
Instalat: 1:1.0.rc2svn20100219-0.0
Candidează: 1:1.0.rc2svn20100219-0.0
Tabela de versiuni:
*** 1:1.0.rc2svn20100219-0.0 0
500 http://www.debian-multimedia.org sid/main Packages
100 /var/lib/dpkg/status
1:1.0.rc2svn20091220-0.0 0
500 http://www.debian-multimedia.org squeeze/main Packages
1.0~rc3+svn20090405-1+b1 0
500 http://debian.networx-bg.com sid/main Packages
500 http://ftp.at.debian.org squeeze/main Packages
1.0~rc2-17+lenny3 0
500 http://ftp.at.debian.org lenny/main Packages
As you can see, debian-multimedia and my regular Debian source have same
priority and setting Default-Release will affect both, but the
"higher"[1] version from debian-multimedia is still installed
automatically.
[1] I write "higher" with quotes because the actual version is smaller,
but Christian Marillat is using an epoch to get his version before the
official one.
I think you should just set your target release to unstable and leave
Multimedia open.
If you have to pin a package with a target release set, you'll have to pin
it between 991-1000 to get the upgrade.
Package: < package_name >
Pin: version < n.n.n* >
Pin-Priority: 991
Just pinning debian-multimedia to a lower priority than the official
source should be enough. What ever you (the OP) are trying out, use
apt-cache policy <package> to test. mplayer is a good package to test
because it exists in both repos.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100222140652.784745m35g0o9pik@webmail.uni-wuerzburg.de">http://lists.debian.org/20100222140652.784745m35g0o9pik@webmail.uni-wuerzburg.de
Debian-Multimedia
