Your message dated Sat, 2 Mar 2019 14:13:48 +0100
with message-id <20190302131348.ga20...@gaara.hadrons.org>
and subject line Re: Bug#46825: dpkg: dselect unruly with 4000 packages
has caused the Debian Bug report #46825,
regarding dselect unruly with 4000 packages
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 ow...@bugs.debian.org
immediately.)
--
46825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.4.1.11
With the package count closely approaching 4000 for the potato release,
scrolling through the whole package list in dselect is a laborious
process and should be unecessary when simply looking for packages marked
for install.
I find this need occurs often and could save considerable time and eye
strain if a supplemental "Packages Marked for Installation" section was
added to the "by status" view.
--- End Message ---
--- Begin Message ---
Hi!
On Wed, 1999-10-06 at 18:35:53 -0700, Craig H. Block wrote:
> Package: dpkg
> Version: 1.4.1.11
> With the package count closely approaching 4000 for the potato release,
> scrolling through the whole package list in dselect is a laborious
> process and should be unecessary when simply looking for packages marked
> for install.
>
> I find this need occurs often and could save considerable time and eye
> strain if a supplemental "Packages Marked for Installation" section was
> added to the "by status" view.
So I'm reading this as an underlaying general complain about memory
usage, there are already some other bugs tracking this, so I'll take
this as the specific complain described there. The memory usage is always
going to be a function of how many packages are present in the
configured repositories. For Debian main that's currently aroun 60k,
so this report can clearly not be an issue anymore.
In any case I think current (and not so current) systems have enough
memory to hold the amount of data from our repositories and a bit
more.
So, I'm going to close this now.
Thanks,
Guillem
--- End Message ---
