[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#944968: popularity-contest: Program accesses internal dpkg database



On Tue, Nov 19, 2019 at 09:34:57AM +0100, Guillem Jover wrote:
> Hi!
> 
> On Mon, 2019-11-18 at 06:51:00 +0000, Niels Thykier wrote:
> > On Sun, 17 Nov 2019 22:59:58 +0100 Bill Allombert wrote:
> > > On Sun, Nov 17, 2019 at 10:44:02PM +0100, Guillem Jover wrote:
> > > > Source: popularity-contest
> > > > Source-Version: 1.69
> > > > Severity: important
> > > > User: debian-dpkg@lists.debian.org
> > > > Usertags: dpkg-db-access-blocker
> 
> > > > This package contains the «popularity-contest» program, which directly
> > > > accesses the dpkg internal database, instead of using one of the public
> > > > interfaces provided by dpkg.
> > > > 
> > > > The program should stop reading the files list files, and switched to
> > > > use something like:
> > > > 
> > > >   «dpkg-query \
> > > >     --showformat 'Package: ${Package}\nFiles:\n${db-fsys:Files}\n' \
> > > >     --show»
> > > > 
> > > > to get them.
> 
> > > the last time this comes up the performance of using dpkg-query was poor. 
> > > Was it improved ? What is the first release to support this syntax ?
> 
> Just to clarify, the command above, does not need packages specified,
> it will dump contents for the entire database.

...which is a problem because then it requires much more memory to proceed than the
current popcon.

So last time the solution was to do a separate dpkg-query for each packages,
but this was much slower.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 


Reply to: