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,
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
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
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.
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/.." &&
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
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
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
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
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
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
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
12 matches
Mail list logo