This is bug [https:\/\/bugs.launchpad.net\/ubuntu\/+source\/popularity-contest\/+bug\/742017 #742017]<\/p>\n
The solution is yet to be devised, but at least we know<\/p>\n
= How popularity-contest works =<\/p>\n
”’popularity-contest”’ is a script that sends a periodic report to Ubuntu (or Debian) about the installed and ”’used”’ packages. At the time of this writing (popularity-contest version 1.51 on Ubuntu 11 \/ Natty Narwhal), popularity-contest is a Perl script.<\/p>\n
How does it work ?<\/p>\n
At the heart of the script are two imbricated loops.
\n
\nThis is bug [https:\/\/bugs.launchpad.net\/ubuntu\/+source\/popularity-contest\/+bug\/742017 #742017]<\/p>\n
The solution is yet to be devised, but at least we know<\/p>\n
= How popularity-contest works =<\/p>\n
”’popularity-contest”’ is a script that sends a periodic report to Ubuntu (or Debian) about the installed and ”’used”’ packages. At the time of this writing (popularity-contest version 1.51 on Ubuntu 11 \/ Natty Narwhal), popularity-contest is a Perl script.<\/p>\n
How does it work ?<\/p>\n
At the heart of the script are two imbricated loops. The outer one runs through all the installed packages and is fed with something like
\n dpkg-query –show
\nThe inner loop then takes each package and run through all the installed files of the said package, checking for the ”atime” (the last access time) of each file. If one file has been accessed, said, more recently than the last 30 days, the package is declared “used”.<\/p>\n
(Side note: that means that ”’popularity-contest”’ performs a stat on every file installed on your machine via the packaging system, a rather heavy task).<\/p>\n
The inner loop get the file list by opening directly the package repository, thus ”’popularity-contest”’ depends on its knowledge of the structure of the repository. Traditionally, the repository is in == This is were things go awry ==<\/p>\n The point is that some packages are architecture-dependent: the list of files depends on your processor, for example. For those packages, the name of the file list is not For example, in my case, the list of files of the base package for gcc v4.5 is called gcc-4.5-base”’:386”’.list. ”’popularity-contest”’ looks fot gcc-4.5-base.list and doesn’t get it right (for a reason unknown to me at the time of this writing), hence the error in the log.<\/p>\n","protected":false},"excerpt":{"rendered":" This is bug [https:\/\/bugs.launchpad.net\/ubuntu\/+source\/popularity-contest\/+bug\/742017 #742017] The solution is yet to be devised, but at least we know = How popularity-contest works = ”’popularity-contest”’ is a […]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[200,206,210,208,202,204],"class_list":["post-349","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-debian","tag-natty-narwhal","tag-perl","tag-popularity-contest","tag-ubuntu","tag-ubuntu-11"],"_links":{"self":[{"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/posts\/349","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/comments?post=349"}],"version-history":[{"count":0,"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/posts\/349\/revisions"}],"wp:attachment":[{"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/media?parent=349"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/categories?post=349"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tronche.com\/blog\/wp-json\/wp\/v2\/tags?post=349"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n \/var\/lib\/dpkg\/info
\nwhere lives (among others) a file