Re: Why backports packages not deactivated
Am 2006-03-08 00:05:52, schrieb T: $ grep -1 backports /etc/apt/preferences Package: * Pin: release a=sarge-backports Pin-Priority: 200 Why not use: Package: * Pin: origin www.backports.org Pin-Priority: 200 Greetings Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why backports packages not deactivated
On Wed, Mar 15, 2006 at 02:58:43PM +0100, Michelle Konzack wrote: Am 2006-03-08 00:05:52, schrieb T: $ grep -1 backports /etc/apt/preferences Package: * Pin: release a=sarge-backports Pin-Priority: 200 Why not use: Package: * Pin: origin www.backports.org Pin-Priority: 200 Michelle, that should pin the package in the same way but his problem was that the package version he had installed was at priority 100, as it was not available in any other archive. -- Steve Block http://ev-15.com/ http://steveblock.com/ [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why backports packages not deactivated
Hello T ([EMAIL PROTECTED]) wrote: I've been following the Debian Backports - Instructions at http://www.backports.org/instructions.html to use backports so as to _deactivate_ all packages from backports.org by default. No. You don't decativate them, you pin them to a lower priority than 500. 500 ist the default priority for packages available from some repository. This is the to-be-wrongly-updated package: $ apt-cache policy hplip-ppds hplip-ppds: Installed: 0.9.3-3 Candidate: 0.9.7-3bpo1 Version Table: 0.9.7-3bpo1 0 200 http://www.backports.org sarge-backports/main Packages ^^^ *** 0.9.3-3 0 100 /var/lib/dpkg/status ^^^ It will be automatically updated from sarge to backport. Why? It is upgraded because the installed version has a lower priority (100200). It has a lower priority because that version is not available in any archive. Probably because that version is outdated. By the way, where did you get it from? It is not part of stable. I recommend that you either upgrade or pin the installed version to 200. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why backports packages not deactivated
On Wed, 08 Mar 2006 09:11:55 +0100, Andreas Janssen wrote: It will be automatically updated from sarge to backport. Why? It is upgraded because the installed version has a lower priority (100200). It has a lower priority because that version is not available in any archive. Probably because that version is outdated. By the way, where did you get it from? It is not part of stable. [...] Thanks for the explanation. I now feel relieved. FYI, my stable is downgraded from testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Why backports packages not deactivated
I've been following the Debian Backports - Instructions at http://www.backports.org/instructions.html to use backports so as to _deactivate_ all packages from backports.org by default. However, I noticed that at least one package is automatically updated from sarge to backport. First of all, I've done all the settings required in the instruction: $ grep backports /etc/apt/sources.list # backports deb http://www.backports.org/debian/ sarge-backports main $ grep -1 backports /etc/apt/preferences Package: * Pin: release a=sarge-backports Pin-Priority: 200 This is the to-be-wrongly-updated package: $ apt-cache policy hplip-ppds hplip-ppds: Installed: 0.9.3-3 Candidate: 0.9.7-3bpo1 Version Table: 0.9.7-3bpo1 0 200 http://www.backports.org sarge-backports/main Packages *** 0.9.3-3 0 100 /var/lib/dpkg/status It will be automatically updated from sarge to backport. Why? How can I prevent it? thanks FYI, Its Reverse Depends are: hplip-base hplip hpijs And none of the above depends will be updated: $ apt-cache policy hplip-base hplip-base: Installed: 0.9.3-3 Candidate: 0.9.3-3 Version Table: *** 0.9.3-3 0 100 /var/lib/dpkg/status $ apt-cache policy hplip hplip: Installed: (none) Candidate: 0.9.2-2 Version Table: 0.9.7-3bpo1 0 200 http://www.backports.org sarge-backports/main Packages 0.9.2-2 0 900 http://debian.yorku.ca sarge/main Packages $ apt-cache policy hpijs hpijs: Installed: 2.1.2+0.9.2-2 Candidate: 2.1.2+0.9.2-2 Version Table: 2.1.7+0.9.7-3bpo1 0 200 http://www.backports.org sarge-backports/main Packages *** 2.1.2+0.9.2-2 0 900 http://debian.yorku.ca sarge/main Packages 100 /var/lib/dpkg/status thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
