On Wed 2017-10-18 13:18:00 +0200, Alessandro Vesely wrote: > at publicsuffix.org they recommend to avoid downloading the list too often, > and > recommend once a day. A dependant package, python-publicsuffix, offers a > fetch() function which is explained in a blog: > https://www.tablix.org/~avian/blog/archives/2015/07/python_publicsuffix_release_1_1_0/
python-publicsuffic is not built from the publicsuffix sources. perhaps you meant to assign this bug to python-publicsuffix instead? > What is the Debian philosophy here? A debian server could fetch the list > daily > and then issue a new release only when there is an effective change. That > would seem to be optimal. Or maybe that would lead to unmanageably high > version numbers? 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. 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? --dkg
signature.asc
Description: PGP signature
