Devuan bug report logs - #623
chimaera-backports repo being used unprompted- missing pin priority

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Package: chimaera-backports
Version: 4.0

I'm running Devuan Chimaera and recently discovered that packages were being upgraded from backports without me manually installing it from backports. I thought that these packages were just put into stable until realizing later that they were backported packages. As described here, a user on dev1galaxy forums realized that the Devuan release file does not put a pin priority of 100 on backports like it does in Debian.

The Debian bullseye-backports repository has a[Release file](http://deb.debian.org/debian/dists/bullseye-backports/Release)that contains these lines:

NotAutomatic: yes
ButAutomaticUpgrades: yes

This confers a pin priority of 100 for all packages, which means they will not be installed unless explicitly targetted (either by version or with the--targetoption forapt) but any packages that are installed from backports will be kept updated from there.

But the Devuan chimaera-backports repository[Release file](http://deb.devuan.org/devuan/dists/chimaera-backports/Release)does not have those lines.

For background, here is the thread where this is being discussed, starting at post #15 in the thread.
[https://dev1galaxy.org/viewtopic.php?id=4567](http://dev1galaxy.org/viewtopic.php?id=4567)

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, October 23rd, 2021 at 6:01 PM, juu <juu@protonmail.com> wrote:

> I'm running Devuan Chimaera and recently discovered that packages were being upgraded from backports without me manually installing it from backports. I thought that these packages were just put into stable until realizing later that they were backported packages. As described here, a user on dev1galaxy forums realized that the Devuan release file does not put a pin priority of 100 on backports like it does in Debian.
>
> The Debian bullseye-backports repository has a[Release file](http://deb.debian.org/debian/dists/bullseye-backports/Release)that contains these lines:
>
> NotAutomatic: yes
> ButAutomaticUpgrades: yes
>
> This confers a pin priority of 100 for all packages, which means they will not be installed unless explicitly targetted (either by version or with the--targetoption forapt) but any packages that are installed from backports will be kept updated from there.
>
> But the Devuan chimaera-backports repository[Release file](http://deb.devuan.org/devuan/dists/chimaera-backports/Release)does not have those lines.
>
> For background, here is the thread where this is being discussed, starting at post #15 in the thread.
> [https://dev1galaxy.org/viewtopic.php?id=4567](http://dev1galaxy.org/viewtopic.php?id=4567)

[Message part 2 (text/html, inline)]

Message #8 received at 623@bugs.devuan.org (full text, mbox, reply):

Control: forcemerge -1 624

Hi,

On Sat, Oct 23, 2021 at 11:22:56PM +0000, juu wrote:
>    Package: chimaera-backports
> 
>    Version: 4.0
> 
>    I'm running Devuan Chimaera and recently discovered that packages were
>    being upgraded from backports without me manually installing it from
>    backports. I thought that these packages were just put into stable
>    until realizing later that they were backported packages. As described
>    here, a user on dev1galaxy forums realized that the Devuan release file
>    does not put a pin priority of 100 on backports like it does in Debian.
> 
>    The Debian bullseye-backports repository has a Release file that
>    contains these lines:
> 
> NotAutomatic: yes
> ButAutomaticUpgrades: yes

Thanks for reporting this. I have changed the configuration in DAK. It may take
up to a day to be propagated. I will check again tomorrow before closing the bug
as fixed.

Mark

Message #21 received at 623-done@bugs.devuan.org (full text, mbox, reply):

On Sun, Oct 24, 2021 at 07:58:55AM +0100, Mark Hindley wrote:
> Thanks for reporting this. I have changed the configuration in DAK. It may take
> up to a day to be propagated. I will check again tomorrow before closing the bug
> as fixed.

The configuration change has propagated to the mirrors.

Closing.

Mark

Send a report that this bug log contains spam.