On Sat, Aug 03, 2024 at 09:52:47AM +0200, Niels Thykier wrote: > Package: popularity-contest > Version: 1.77 > Severity: wishlist > X-Debbugs-Cc: [email protected] > > Hi, > > The popularity-contest provides the columns `Inst`, `Vote`, `Old`, `Recent` > and `No Files`. > > I feel it would be interesting to see how many are `Old` because the system > has disabled `atime` on its mount point (either directly or because the > mount point is read-only). For these systems, you can basically never get a > `Vote` - at least you will see a `Recent` as I understand the current logic.
Yes, but I do not think this is a major issue, since it is uniform across all packages. For example 36 libc6 233754 216998 545 16197 14 (Gnu Libc Maintainers) so this affects probably less than 0.5% of submissions. > Therefore, I would like to see popularity-contest track whether the mount > points would ever update its atime (the mount flags I know of that are > relevant are `noatime` or `ro`[1]) when popularity-contest tracks whether it > should count a given file as giving a Vote. So instead of undercounting votes by 0.5%, this would overcount them by 0.5% ? This does not seem to be worth the effort. > I see this proposal as an alternative to #87619 that does not rely on a new > dependency (/etc/mtab, /proc/mounts, or `mount` can all provide the data) #87619 was reported at a time where relatime was not available and noatime was much more popular. Cheers, -- Bill. <[email protected]> Imagine a large red swirl here.
