• Bug#688251: #688251: Built-Using description too aggressive

    From Sean Whitton@21:1/5 to Charles Plessy on Sat Aug 26 23:30:01 2017
    XPost: linux.debian.bugs.dist

    control: tag -1 +patch

    Hello,

    On Sun, Oct 06, 2013 at 05:30:12PM +0900, Charles Plessy wrote:
    The attached patch is a third attempt, which underlines that the Built-Using field is particularly useful when a given package, contributing contents included in another package, can not be replaced by a later version. It also explains that the Debian archive uses the Built-Using field to retain source packages.

    Here is a patch for which I am seeking seconds.

    - try to improve explanation of "cannot be replaced by a later version"

    - state that built-using is NOT for tracking packages that need to be
    rebuilt

    The release team have made it clear that they don't want built-using
    used for this purpose as it generates work close to the release.

    diff --git a/policy/ch-relationships.rst b/policy/ch-relationships.rst
    index 3a73f7b..499bed9 100644
    --- 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``
    ---------------------------------------------------------------------

    -Some binary packages incorporate parts of other packages when built but
    -do not have to depend on those packages. Examples include linking with
    -static libraries or incorporating source code from another package
    -during the build. In this case, the source packages of those other
    -packages are a required part of the complete source (the binary package
    -is not reproducible without them).
    -
    -A ``Built-Using`` field must list the corresponding source package for
    -any such binary package incorporated during the build, [#]_ including
    -an "exactly equal" ("=") version relation on the version that was used
    -to build that binary package. [#]_
    +Some binary packages incorporate parts of other packages when bu
  • From Ansgar Burchardt@21:1/5 to Sean Whitton on Mon Aug 28 10:10:04 2017
    XPost: linux.debian.bugs.dist

    Sean Whitton writes:
    +This field should not be used for purposes other than satisfying
    +license requirements to provide full source code.

    The DFSG requires source code to be provided too...

    Ansgar

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sean Whitton@21:1/5 to Ansgar Burchardt on Tue Aug 29 01:10:01 2017
    XPost: linux.debian.bugs.dist

    Hello Ansgar,

    On Mon, Aug 28 2017, Ansgar Burchardt wrote:

    Sean Whitton writes:
    +This field should not be used for purposes other than satisfying
    +license requirements to provide full source code.

    The DFSG requires source code to be provided too...

    Can you suggest a better word than 'full' to express the extra copyleft requirements that the Built-Using field is getting at?

    --
    Sean Whitton

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlmkk3MACgkQaVt65L8G YkDkNQ//ZvMrFAYqLFYSF8z85yrDb5W1y82SHDFzRos4KEtxeRr/8+pEaJEqUObr 9QCnRU6Q4GSIh3j7DgMr247NWyvXDo34/vE9IPWCLcazYjY4bxjPePYnNqqMwp6N bEZOI1V/9qWMTRAhq3id41KHIW/d4PiFu5MLGKz/GKv7qpUg5zpg9kY0sul8sZ0j AazqT0ZYLnhHL+YwQlZQNq73uQZbDCCJOV3RY/fO8TYaCK9mkFLzJTC8QJM1Tj9M NIkXc6N+ON/8xVdDJhppcRX45OSu82WgjC+mo+GHlh9oiInc9obmw05UNfyciXaS 2QOJRX4NVaaXv1Q9W2dNyCcLhhr5DbRCjxA/yS3/wtnzUob3xrwTl1HHYEgZA19Z ZsOA166lsyzs4+2PF5zlD6FWh42qiytMXLM+AtEV9fOXX2V2cf6P1kKagDP1OVzv urnor29h3S7y249LE15/rBENgJTvEq0lA6w7VbtmNuq3V1QeKRGth1VoN0SwYoOP 3yeU/0WpLYJYiPz8qg2vQ+m+2STOEotUycC6WVJMVG0aAtesg3Y0Z/h+GTa6c2Ml xuFMnbvsZsoPz722GtQmPAajIE/PZBLaTvtrofgAxx9J9XYdV9ttWRmI7zObf2En paE2ILgBXJvtvFLEJ64KcG7Ye+PpytmncSNTMi4lRcs+T4MO4GYSz9
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)