Why a relevant number of packages appears to have different priority
depending on where you look for that field?
For example if you get "aptitude_0.6.11-1_amd64.deb" from a Debian
mirror and you look inside "debian/control" file, you'll see:
Priority: important
But if you get /debian/dists/sid/main/binary-amd64/Packages.gz from the
same mirror and search for "Package: aptitude", you'll see:
Priority: standard
Why the priority field doesn't match? Is there something that i'm missing?
That difference emerges also if you search for the same information at a
higher level, using dpkg or apt or aptitude. The former will agree with
the control file inside the deb file, while apt/aptitude will agree with
Packages.gz.
Compare these:
dpkg-query -W -f '${Package};${Version};${Priority}\n' aptitude
apt-cache show aptitude
aptitude show aptitude
The aptitude package is just an example. On my Debian unstable i also
see priority differences for these packages:
aptitude-common
info
init-system-helpers
install-info
libcwidget3
libevdev2
libgpgme11
libmozjs185-1.0
libpython2.7
libpython2.7-minimal
libpython2.7-stdlib
libsystemd-daemon0
libsystemd-id128-0
libsystemd-journal0
libsystemd-login0
libxapian22
libyajl2
python2.7-minimal
systemd
systemd-sysv
And i've found similar differences also on a Jessie and a Wheezy box.
Thanks in advance for any clarification.
Cesare.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/542a006b.90...@gmail.com
