Control: tags -1 + moreinfo

On Thu, 2016-07-14 at 19:49 +0200, Daniel Kahn Gillmor wrote:
> I think debian should offer publicsuffix via stable-updates.
> 
> publicsuffix ships a file that is updated semi-regularly to reflect the
> state of the network (a list of all DNS domains which members of the
> public might be able to register immediate subzones).  It's used for
> HTTP cookie policy and for X.509 wildcard certificate issuance, among
> other uses.
> 
> In this way, it's similar to tzdata.
> 
> I've prepared a "jessie" branch on the debian packaging repo, which
> currently builds fine on stable, and is a simple package:
> 
>   https://anonscm.debian.org/git/collab-maint/publicsuffix

Please could we have a debdiff, relative to the current package in
jessie, in this bug log? (We prefer p-u bugs to be self-contained, and
not have to rely on your git tree existing for arbitrary periods in the
future, or on it not changing after we give an ack.)

> The only difference in the resultant package (beyond the updated data)
> is that the version in jessie (20140902-1) ships with only the legacy
> location for the data file
> (/usr/share/publicsuffix/effective_tld_names.dat) while the updated
> file ships that as a symlink to the modern location of the file
> (/usr/share/publicsuffix/public_suffix_list.dat)
> 
> Any concerns if i upload this to proposed-updates with an eye toward
> stable-updates?

How frequently would you imagine that the package would need to be
updated in stable?

Regards,

Adam

Reply via email to