Bug#641153: document Built-Using field for binary packages

2012-08-12 Thread Russ Allbery
Charles Plessy writes: > Le Sun, Jul 08, 2012 at 09:01:47PM -0500, Jonathan Nieder a écrit : >> Here's the same patch with the above fixes applied. Sensible? > Thanks for the corrections. > The patch is seconded by me, Russ and Ansgar, and is ready to be applied. Applied for the next release.

Bug#641153: document Built-Using field for binary packages

2012-07-14 Thread Charles Plessy
user debian-pol...@packages.debian.org tags 641153 - patch usertags 641153 seconded thanks Le Sun, Jul 08, 2012 at 09:01:47PM -0500, Jonathan Nieder a écrit : > > Here's the same patch with the above fixes applied. Sensible? Thanks for the corrections. The patch is seconded by me, Russ and Ans

Processed: Re: Bug#641153: document Built-Using field for binary packages

2012-07-14 Thread Debian Bug Tracking System
usertags 641153 seconded Bug#641153: document Built-Using field for binary packages Usertags were: normative. Usertags are now: normative seconded. > thanks Stopping processing here. Please contact me if you need assistance. -- 641153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64115

Bug#641153: document Built-Using field for binary packages

2012-07-08 Thread Jonathan Nieder
Hi, Jakub Wilk wrote: > * Charles Plessy , 2011-12-30, 15:39: >>+ A Build-Using field must list the corresponding source >>+ package for any such binary package incorporated during the build > > s/Build-/Built-/ > >>+ The archive software might reject packages that refer to >>

Bug#641153: document Built-Using field for binary packages

2012-02-26 Thread Ansgar Burchardt
Charles Plessy writes: > here is a proposed patch that uses a slimed version of the paragraphs proposed > by Russ (quoted below) and keeps the original examples. Looks good to me; seconded as well and thanks for your work. > I agree with Russ that a binary/binary relationship may be preferrable.

Bug#641153: document Built-Using field for binary packages

2011-12-30 Thread Russ Allbery
Charles Plessy writes: > here is a proposed patch that uses a slimed version of the paragraphs > proposed by Russ (quoted below) and keeps the original examples. It > documents the field as new section, number 7.8, the last one of its > chapter, because it introduces a new type of relationship,

Bug#641153: document Built-Using field for binary packages

2011-12-30 Thread Russ Allbery
Ansgar Burchardt writes: > I think source packages better reflect the meaning of the field (keep > the source available). Listing them will hopefully soon no longer be > more complicated than binary package, see [1]. > [1] > In addition listing binaries would

Bug#641153: document Built-Using field for binary packages

2011-12-30 Thread Ansgar Burchardt
Hi, Russ Allbery writes: > Ansgar Burchardt writes: >> A try at this: > >> Some binary packages incorporate material derived from source >> or compiled code derived from other source packages. In this case >> this field must be used to list all other source packages necessary >> to obta

Bug#641153: document Built-Using field for binary packages

2011-12-30 Thread Jakub Wilk
* Charles Plessy , 2011-12-30, 15:39: + A Build-Using field must list the corresponding source + package for any such binary package incorporated during the build s/Build-/Built-/ + The archive software might reject packages that refer to + non-existant sou

Bug#641153: document Built-Using field for binary packages

2011-12-30 Thread Charles Plessy
Dear all, here is a proposed patch that uses a slimed version of the paragraphs proposed by Russ (quoted below) and keeps the original examples. It documents the field as new section, number 7.8, the last one of its chapter, because it introduces a new type of relationship, from binary package to

Bug#641153: document Built-Using field for binary packages

2011-12-24 Thread Russ Allbery
Russ Allbery writes: > One basic question about this before I dive into wording: why is the > Build-Depends field not adequate? Never mind this question; I figured it out but forgot to remove this part of my mail. -- Russ Allbery (r...@debian.org)

Bug#641153: document Built-Using field for binary packages

2011-12-24 Thread Russ Allbery
One basic question about this before I dive into wording: why is the Build-Depends field not adequate? Ansgar Burchardt writes: > A try at this: > Some binary packages incorporate material derived from source > or compiled code derived from other source packages. In this case > this fiel

Bug#641153: document Built-Using field for binary packages

2011-12-12 Thread Ansgar Burchardt
Am 12.12.2011 15:14, schrieb Jakub Wilk: * Ansgar Burchardt , 2011-12-12, 14:44: Also, §7.1 specifies differently the architecture restrictions for build relationship fields (Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep) and binary relationship fields. According

Bug#641153: document Built-Using field for binary packages

2011-12-12 Thread Jakub Wilk
* Ansgar Burchardt , 2011-12-12, 14:44: Also, §7.1 specifies differently the architecture restrictions for build relationship fields (Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep) and binary relationship fields. According to what is expected for Built-Using, §7.

Bug#641153: document Built-Using field for binary packages

2011-12-12 Thread Ansgar Burchardt
Hi, thanks for your comment and sorry for the late reply, I forgot about this bug for a while. Am 11.09.2011 04:38, schrieb Charles Plessy: thanks for documenting Built-Using in the Policy. I have a couple of comments about your patch. @@ -3061,7 +3061,8 @@ Package: libc6 Depends,Pr

Bug#641153: document Built-Using field for binary packages

2011-11-24 Thread Charles Plessy
user debian-policy@lists.debian.org usertags 641153 + normative discussion thanks Le Sun, Sep 11, 2011 at 11:38:05AM +0900, Charles Plessy a écrit : > Le Sat, Sep 10, 2011 at 10:44:49PM +0200, Ansgar Burchardt a écrit : > > > > some months ago support for the Built-Using field was added to the >

Bug#641153: document Built-Using field for binary packages

2011-09-11 Thread Charles Plessy
Le Sun, Sep 11, 2011 at 08:32:33AM +0200, Raphael Hertzog a écrit : > On Sun, 11 Sep 2011, Charles Plessy wrote: > > This adds Built-Using in §5.6.10 (“Package interrelationship fields: > > Depends, > > Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces, > > Enhances”). In P

Bug#641153: document Built-Using field for binary packages

2011-09-10 Thread Raphael Hertzog
On Sun, 11 Sep 2011, Charles Plessy wrote: > This adds Built-Using in §5.6.10 (“Package interrelationship fields: Depends, > Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces, > Enhances”). In Policy's chapter 5, the fields in that list are documented to > be present in sour

Bug#641153: document Built-Using field for binary packages

2011-09-10 Thread Charles Plessy
Le Sat, Sep 10, 2011 at 10:44:49PM +0200, Ansgar Burchardt a écrit : > > some months ago support for the Built-Using field was added to the > archive software. It is used by binary packages to refer to additional > source packages that were used during the build and need to stay in the > archive

Bug#641153: document Built-Using field for binary packages

2011-09-10 Thread Ansgar Burchardt
Package: debian-policy Severity: normal Hi, some months ago support for the Built-Using field was added to the archive software. It is used by binary packages to refer to additional source packages that were used during the build and need to stay in the archive to have the full source available.