Processed: Re: Bug#688251: Built-Using description too aggressive

2017-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 -patch +pending Bug #688251 [debian-policy] Built-Using description too aggressive Removed tag(s) patch. Bug #688251 [debian-policy] Built-Using description too aggressive Added tag(s) pending. -- 688251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688

Bug#688251: Built-Using description too aggressive

2017-12-27 Thread Sean Whitton
control: tag -1 -patch +pending Hello, On Wed, Dec 27 2017, Jonathan Nieder wrote: > Is this part just a line-wrapping change? If so, feel free to check > it in directly to make the normative diff easier to review. No: s/required part of the complete source/part of the complete source/. I can

Bug#688251: Built-Using description too aggressive

2017-12-27 Thread Jonathan Nieder
Hi, Sean Whitton wrote: > --- a/policy/ch-relationships.rst > +++ b/policy/ch-relationships.rst @@ -598,17 +598,26 @@ earlier for > binary packages) in order to invoke the targets in > Additional source packages used to build the binary - ``Built-Using`` > --

Bug#688251: Built-Using description too aggressive

2013-09-22 Thread Jonathan Nieder
Hi, Charles Plessy wrote: > --- a/policy.sgml > +++ b/policy.sgml > @@ -5563,7 +5563,13 @@ Replaces: mail-transport-agent > > > > - A Built-Using field must list the corresponding source > + When the licensing terms of the incorporated parts require to provide > +

Bug#688251: Built-Using description too aggressive

2012-09-20 Thread Russ Allbery
Package: debian-policy Severity: normal Based on discussion in debian-devel, the current Built-Using description would imply that it had to be present for, say, the code from libgcc incorporated into every binary build. The description should be modified to be clear that it is only mandatory if t