Forwarding more details to the bug with permission from the submitter.
Daniel
----- Forwarded message from Jan Muszynski <debianb...@jancm.org> -----
Date: Tue, 13 Jan 2009 14:45:51 -0500
Subject: Re: Bug#503175: aptitude shows false update count
From: Jan Muszynski <debianb...@jancm.org>
To: Daniel Burrows <dburr...@algebraicthunk.net>
You can close this bug. The problem arose from entries in my preferences file.
(Which I now understand much better then when I first set it up).
One thing I wasn't aware of (unless it's a bug, in which case a new
one will need to be opened)
is that if apt.conf specifies a default-release of say, testing, then
any 3rd part repos that use testing
as the release (no matter what else is specified) will also use the a
pinning priority of 990
So it looks, to me at least, like "default release" shouldn't really
be used in conjunction with an
extensive preferences file. Rather just set "release
o=Debian,a=testing" to 990 (which accomplishes
the same thing).
Long story short wine was being treated as a pinned program, and it
was picking up a high-priority,
from somewhere else (not sure where, things have changed too much
since then. I may have had an
erroneous etch/stable entry in there someplace though). But I'm sure
that that's what was happening.
Let's see - Bug#503175
Thanks, jan
On Sun, Dec 7, 2008 at 9:57 PM, Jan Muszynski <debianb...@jancm.org> wrote:
> That's correct, neither a full or "safe" upgrade actually downgraded
> wine. It just kept displaying the message about 1 package not
> upgraded. Update Manager also kept telling me I had 1 upgrade
> available - but wouldn't show me what it actually was.
>
> I don't think I tried Synaptic at that point I probably should have.
> Hold on, let me try and turn this back on :)
>
> OK, here's what happens with the different engines:
>
> aptitude:
> aptitude update, end of listing:
> Fetched 206kB in 24s (8330B/s)
> Reading package lists... Done
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Deleting obsolete downloaded files
>
> aptitude full-upgrade:
> # aptitude full-upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Need to get 0B of archives. After unpacking 0B will be used.
> Do you want to continue? [Y/n/?] y
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
>
> apt-get update:
> Fetched 4150B in 23s (174B/s)
> Reading package lists... Done
>
> apt-get dist-upgrade: (This one is interesting, comments follow)
> apt-get -s dist-upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following NEW packages will be installed:
> winbind
> 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
> Inst winbind (2:3.2.5-1 Debian:testing)
> Conf winbind (2:3.2.5-1 Debian:testing)
>
> Note that it wants to install winbind, which is a dependency of the
> winehq package (which is the "downgrade to" package), but not of the
> debian packages (it's only suggested). But it doesn't actually
> downgrade the wine package.
>
> Synaptic: No indication of any "upgrades"
>
> Update Manager: The little orange icon shows in the systray. Mouse
> hover indicates 1 update available. Click on the icon to actually
> start up update manager and it tells me "Your system is up to date".
>
> apt.conf
> APT
> {
> Cache-Limit "33554432";
> Default-Release "testing";
> Install-Recommends "false";
> Install-Suggests "false";
> };
> Aptitude
> {
> Recommends-Important "false";
> Autoclean-After-Update "true";
> Delete-Unused "true";
> Display-Planned-Action "true";
> Purge-Unused "true";
> CmdLine
> {
> Show-Deps "true";
> Show-Versions "true";
> Always-Prompt "true";
> };
> };
>
> preferences:
> Package: wine
> Pin: release o=winehq
> Pin-Priority: 101
> Explanation: This is winehq.org, Want the newest release, with
> testing getting priority
>
> Package: *
> Pin: release a=unstable,o=Debian
> Pin-Priority: 110
>
> experimental isn't listed, I let it take the default.
> A local repo is listed at 999
>
> That's everything that may be relevant. Drop winehq to a pin of 99 and
> no problem, it goes back to 0 upgrades.
>
> Bottom line it doesn't look like it's an aptitude problem per-se. But
> is it apt-get, dpkg, or something else? I don't know enough about how
> these things work. I initially noticed the bug in aptitude, which is
> why you got it. If you think it should be assigned to another package
> be my guest, you'd know better than I. I'm curious why it only happens
> with this one package though. I have other experimental stuff loaded
> and this doesn't trigger - but those other experimental packages also
> don't have a 3rd party repo involved. (Just thinking out loud).
>
> -jan
>
> On Sat, Dec 6, 2008 at 9:47 AM, Daniel Burrows
> <dburr...@algebraicthunk.net> wrote:
>> On Fri, Dec 05, 2008 at 12:32:14AM -0500, Jan Muszynski
>> <debianb...@jancm.org> was heard to say:
>>> Sorry about the bottom post. I'll keep it in mind for the future. The
>>> real question (in my mind, and I may be off base) is why is this being
>>> flagged as an auto-downgrade. I thought that auto-downgrades only come
>>> into play with a pin of over 1000. In this case I had to pin at <100
>>> to make it go away. I'm just really curious why this package got
>>> flagged.
>>>
>>> Of course it doesn't actually try to process the downgrade :) It's
>>> just an informational glitch which drove me crazy for about 2-3 weeks
>>> before I finally decided to track it down.
>>
>> Hm, so running "full-upgrade" doesn't actually downgrade wine?
>> That might be an indication that it's the "not upgraded" count that's
>> wrong, not the "updates" count.
>>
>> Daniel
>>
>
----- End forwarded message -----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
