On 10/21/2011 10:59 AM, Tshepang Lekhonkhobe wrote:
On Fri, Oct 21, 2011 at 16:52, David Liontooth<lionte...@cogweb.net> wrote:
Package: wajig
Version: 2.0.47
Severity: wishlist
wajig currently appears to ignore apt policy (pinning), and perhaps it should
stay that way!
Here's what happens when you pin (see apt policy below):
# wajig toupgrade
Package Available Installed
========================-========================-========================
gcc-4.6-base 4.6.1-16 4.6.1-15
libffi5 3.0.10-3 3.0.10-1
libglib2.0-0 2.28.8-1 2.28.6-1
libglib2.0-bin 2.28.8-1 2.28.6-1
libglib2.0-data 2.28.8-1 2.28.6-1
libglib2.0-dev 2.28.8-1 2.28.6-1
libgtk2.0-0 2.24.7-1 2.24.4-3
libgtk2.0-bin 2.24.7-1 2.24.4-3
libgtk2.0-dev 2.24.7-1 2.24.4-3
libstdc++6 4.6.1-16 4.6.1-15
# wajig upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
libgtk2.0-0 libgtk2.0-bin libgtk2.0-dev
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (990, 'stable'), (100, 'testing'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
I don't really understand this report. What happens when you run
'apt-get' directly?
apt-get upgrade produces the same result as wajig upgrade (apt-policy is
respected). wajig toupgrade doesn't respect apt-policty (thus the
contrast between the two commands in the bug report).
David
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
