On Thu 19/Oct/2017 08:06:27 +0200 Daniel Kahn Gillmor wrote: > > The publicsuffix package itself is what most debian packages should rely > on -- It will be updated regularly, and you'll have not only a recent > psl but you won't have to fetch any other data besides package upgrades. > > This is a similar pattern to: > > * tzdata > * dns-root-data > > the update cadence is likely to be faster than dns-root-data, but > probably about the same as tzdata.
No, it's much faster. They say once every few days, but there are longer periods of quiescence, irregularly distributed along time. For details see: https://github.com/publicsuffix/list/commits/master > Or is this bug report just asking for a new upload of publicsuffix to > stretch-updates to catch the few dozen domains that have been updated > since stretch was released? That would not be enough. Many servers run on wheezy or jessie. Their best option is to set up a cron job to download the file daily. A more sophisticated user might download the file to a temporary directory, compare it to the existing one, and in case they differ replace the old file and then send a SIGHUP to any daemons which maintain a memory structure of it. Even better, use svn or git to download from github directly. However, this method requires hidden subdirectories, and hence may not seem to be compatible with the current packaging. Finally, consider issuing updates for all debian versions still enjoying long term support (https://wiki.debian.org/LTS). Is it better or worse than the former methods? If a cron job is better, one could be installed in cron.d... What do you reckon? Ciao Ale
