:: Re: [DNG] Accepting changed priorit…
Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Boian Bonev
Fecha:  
A: dng
Asunto: Re: [DNG] Accepting changed priority for chimaera-backports- what action?
Hi,

On Sun, 2022-01-23 at 20:17 +1100, terryc wrote:
> So exactly what does this message mean and exactly what do I need to do.
> Previously I've just repeated the command and the nag message went
> away but this time it stays.
>
> user@system: sudo apt-get update
> Get:1 http://deb.devuan.org/merged chimaera InRelease [33.9 kB]

...
> Get:10 http://deb.devuan.org/merged chimaera-updates/main amd64
> Packages [2,608 B]
> Get:11 http://deb.devuan.org/merged chimaera-updates/main i386 Packages
> [2,612 B]
>
> Reading package lists... Done
> E: Repository 'http://deb.devuan.org/merged chimaera-backports InRelease'
> changed
>  its default priority for apt_preferences(5) from 500 to 100.
> N: This must be accepted explicitly before updates for this repository can be
>  applied. See apt-secure(8) manpage for details


Not long ago the priority of chimaera-backports was decreased. The problem is
that with 500 apt would automatically install everything from backports and
that is not a good idea at all. Ideally one would install only what they need
from backports by manual selection - it is not guaranteed that installing
everything from backports over stable will result in a working package
combination.

Generally recent apt version warn and refuse to continue without confirmation
in case some data in the repos changes. E.g. if you used stable that was
beowulf and you update after stable became chimaera, you would get a similar
warning. The idea is to avoid users unknowingly doing major changes...

> Except man apt-secure doesn't give me anything I understand.


Use "sudo apt update" and confirm on the prompt (should happen only once) or
see the answer from Ralph...

With best regards,
b.