Bug#869921: marked as done (apt: Pinning the local version of a package no longer works)
Your message dated Thu, 27 Jul 2017 18:24:52 +0200
with message-id <20170727182235.GA21474@debian.org>
and subject line Re: Bug#869921: apt: Pinning the local version of a package no longer works
has caused the Debian Bug report #869921,
regarding apt: Pinning the local version of a package no longer works
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.debian.org
immediately.)
--
869921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869921
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.1
Severity: normal
Pinning the local version of a package, as documented in
apt_preferences(5), seems to have been broken between jessie and
stretch:
Contents of /etc/apt/preferences:
Package: hello
Pin: origin ""
Pin-Priority: 999
Output of "apt-cache policy hello" on jessie:
hello:
Installed: 2.8-1
Candidate: 2.8-1
Package pin: (not found)
Version table:
2.9-2+deb8u1 999
500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages
*** 2.8-1 999
100 /var/lib/dpkg/status
Output of "apt-cache policy hello" on stretch:
hello:
Installed: 2.8-1
Candidate: 2.10-1+b1
Version table:
2.10-1+b1 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
*** 2.8-1 100
100 /var/lib/dpkg/status
The behavior of "apt-get upgrade" confirms this: the package is pinned
to the local version on jessie, but is upgraded on stretch (and sid).
After bisecting a bit with snapshots, this was apparently introduced
between 1.0.10.2 and 1.1.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Thu, Jul 27, 2017 at 06:12:14PM +0200, Julian Andres Klode wrote:
> On Thu, Jul 27, 2017 at 11:44:31AM -0400, Frédéric Brière wrote:
> Yay, everything working. So I guess the question is more if /var/lib/dpkg/status
> should match origin "" or not.
So I did some further digging, and the status file has been excluded from matching
origin pins since:
Fix origin pins for file:// uris.
Author: doogie
Date: 2003-04-24 03:16:58 GMT
Fix origin pins for file:// uris.
(That's in or before 0.5.15)
I guess we should not suddenly make it match them, so closing this
bug. If you want to pin against the status file, pin release a=now.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
--- End Message ---
Reply to: