[Pkg-privacy-maintainers] Bug#829740: RFP: corridor - a Tor traffic whitelisting gateway

[u]

Hi,

Patrick Schleizer:
> Is someone from the PkgPrivacyMaintainers team interested / willing to
> help get corridor [4] [5] [6] into Debian?

I'm not sure how useful this is exactly. It's still beta?

> I got a working prototype of a Debian package which is almost free of
> lintian warnings. [1] [2] [3] There are just some remaining --pedantic
> lintian warnings that are fixable. First questions...
> 
> 1)
> 
> I: corridor source: unused-file-paragraph-in-dep5-copyright paragraph at
> line 3
> 
> https://github.com/adrelanos/corridor/blob/debian_new/debian/copyright
> 
> Any idea what is wrong in the debian/copyright file?

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#files-paragraph

Multiple Files paragraphs are allowed. The last paragraph that matches a
particular file applies to it. More general paragraphs should therefore
be given first, followed by more specific overrides.

So I suppose the problem is that you declare * after Files/* and that
overrides the first paragraph.

> 2)
> 
> Would a combined manpage, i.e. 'man corridor', symlinked to the
> individual command names (corridor-init-forwarding, corridor-init-snat,
> ...) be acceptable by Debian policy and otherwise or should a separate
> man page per binary be provided?

https://www.debian.org/doc/debian-policy/ch-docs.html

"Each program, utility, and function should have an associated manual
page included in the same package. [..] Manual pages for protocols and
other auxiliary things are optional."

Symlinking man pages is allowed, as described in this policy, but I do
not have an example in mind where this has been done.

Cheers!
u.