Devuan bug report logs -
#623
chimaera-backports repo being used unprompted- missing pin priority
Reported by: juu <juu@protonmail.com>
Date: Sat, 23 Oct 2021 23:32:02 UTC
Severity: normal
Merged with 624
Found in version chimaera
Done: Mark Hindley <mark@hindley.org.uk>
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 25 Oct 2021 19:28:17 +0100
with message-id <YXb3QeaSaGX2pLZh@hindley.org.uk>
and subject line Re: bug#623: chimaera-backports repo being used unprompted- missing pin priority
has caused the Devuan bug report #623,
regarding chimaera-backports repo being used unprompted- missing pin priority
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)
--
623: https://bugs.devuan.org/cgi/bugreport.cgi?bug=623
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (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 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
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.