Bug#872895: debian-policy: Split html for policy lost

2017-08-23 Thread Guillem Jover
On Tue, 2017-08-22 at 17:26:32 -0700, Sean Whitton wrote: > On Tue, Aug 22 2017, Guillem Jover wrote: > > I guess there are two problems here, one is indeed completely losing > > the multi-page rendering from the package. The other is the default > > change in the web site. IMO the best solution,

Bug#873001: [debian-policy] get-orig-source documentation should include a pointer to devref and a minimal example

2017-08-23 Thread Bastien ROUCARIÈS
Package: debian-policy Version: 4.0.1.0 Severity: normal get-orig-source should include an example. If you use uscan this is safe and policy compliant (maybe opening a bug against dpkg-dev to get this rule by default) cd "$(subst ",\",$(dir $(lastword $(MAKEFILE_LIST/.." && uscan --destdir

Re: debian/upstream/signing-key.asc in policy 4.1.0

2017-08-23 Thread Russ Allbery
Osamu Aoki writes: > After all the discussion, Policy 4.1.0 goes as: > | 4.11. Optional upstream source location: debian/watch¶ > | > | This is an optional, recommended configuration file for the uscan > | utility which defines how to automatically scan ftp or http sites for

debian/upstream/signing-key.asc in policy 4.1.0

2017-08-23 Thread Osamu Aoki
Hi, After all the discussion, Policy 4.1.0 goes as: | 4.11. Optional upstream source location: debian/watch¶ | | This is an optional, recommended configuration file for the uscan | utility which defines how to automatically scan ftp or http sites for | newly available updates of the package.

Bug#873001: [debian-policy] get-orig-source documentation should include a pointer to devref and a minimal example

2017-08-23 Thread Russ Allbery
Bastien ROUCARIÈS writes: > get-orig-source should include an example. > If you use uscan this is safe and policy compliant (maybe opening a bug > against dpkg-dev to get this rule by default) > cd "$(subst ",\",$(dir $(lastword $(MAKEFILE_LIST/.." &&

Bug#873001: [debian-policy] get-orig-source documentation should include a pointer to devref and a minimal example

2017-08-23 Thread Russ Allbery
roucaries bastien writes: > you call the rules with something (using shebang or directly) make -f > somepath/package/debian/rules, uscan need to be excuted on > somepath/package/. Oh, I see the edge case this is trying to handle. I'll be honest: I'm

Bug#810381: debian-policy: Update wording of 5.6.26 VCS-* fields to reflect the need for security

2017-08-23 Thread Russ Allbery
Control: tags -1 patch Scott Kitterman writes: > On January 8, 2016 12:26:24 PM EST, Russ Allbery wrote: >> Scott Kitterman writes: >>> As is currently being discussed on #debian-devel, the git:// protocol >>> is insecure, but is

Processed: Re: Bug#810381: debian-policy: Update wording of 5.6.26 VCS-* fields to reflect the need for security

2017-08-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #810381 [debian-policy] Update wording of 5.6.26 VCS-* fields to recommend encryption Added tag(s) patch. -- 810381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, usertagging 661928 ...

2017-08-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to

Bug#871534: debian-policy: Clarify whether mailing lists in Maintainers/Uploaders may be moderated

2017-08-23 Thread Russ Allbery
Per the message below, I propose to close this bug because I think this is already addressed reasonably well. (There's probably some room to offer advice to maintainers on how to run the mailing list, but that feels more like devref material than Policy material.) Chris, any objections? Am I

Bug#661928: debian-policy: recipe for determining shlib package name

2017-08-23 Thread Russ Allbery
Russ Allbery writes: > Jakub Wilk writes: >> The actualy lintian code is: >> foreach my $expected_name (@sonames) { >> $expected_name =~ s/([0-9])\.so\./$1-/; >> $expected_name =~ s/\.so(?:\.|\z)//; >> $expected_name =~ s/_/-/g; >> if

Bug#873001: [debian-policy] get-orig-source documentation should include a pointer to devref and a minimal example

2017-08-23 Thread roucaries bastien
On Wed, Aug 23, 2017 at 6:29 PM, Russ Allbery wrote: > Bastien ROUCARIÈS writes: > >> get-orig-source should include an example. > >> If you use uscan this is safe and policy compliant (maybe opening a bug >> against dpkg-dev to get this rule