>From: Daniel Burrows <[EMAIL PROTECTED]>
...
> I think new packages that are upgradable have always gone into the
>"new packages" section. It might make sense to pull them out of there
>automatically, though.
Hmm --- maybe I misunderstand what a "new package" is...
In the particular instance I noticed/reported last night:
o libmyth-0.20 was already installed, at version 0.20-0.0.
o A younger version, 0.20-0.2, became available.
o After updating the package cache, aptitude displayed
libmyth-0.20 in the "new packages" section.
Since libmyth-0.20 had already been installed, and it wasn't listed
as a "new package" before the latest update, why did it become new
again after the update?
(libmyth-0.20 is from a foreign repository, so maybe it is a poor
sample point, but I'm positive that I've seen this occur now and
again with mainline Debian packages.)
-matt m.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
