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.ba
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
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
> (100<200). It has a lower priority because that version is not available
> in any archive. Probably b
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
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
5 matches
Mail list logo
