[Debian-iot-maintainers] ocf-spec-core_2.1.0-1_amd64.changes REJECTED

[David Suarez]

HI,

That's my fault, the license in d/copyright should point to
BSD-2-clause (instead of 3 clause). The packaged files (the json
swagger specs) point's to it, eg:

> "swagger": "2.0",
> "info": {
> "title": "Atomic Measurement links list representation",
> "version": "2019-03-04",
> "license": {
>      "name": "OCF Data Model License",
>      "url": "https://openconnectivityfoundation.github.io/core/LICENSE.md",
>      "x-copyright": "Copyright 2018-2019 Open Connectivity Foundation, Inc. All rights reserved."
>    },

Changin d/copyright to point to BDS-2-clause is sufficient to clarify
the package license ? Let us know and will reupload it with the
proposed changes.

Thanks,


El dom., 24 may. 2020 a las 19:00, Sean Whitton
(<ftpmaster at ftp-master.debian.org>) escribió:
>
>
> +----------------------+
> |   REJECT reasoning   |
> +----------------------+
>
> It is not clear whether this package is BSD-2-clause or BSD-3-clause.
>
> Copies of both licenses are included in the source package.  The file
> https://openconnectivityfoundation.github.io/core/LICENSE.md is
> BSD-2-clause.  But d/copyright says BSD-3-clause.
>
> Please seek clarification from upstream.
>
> +----------------------+
> |         N.B.         |
> +----------------------+
>
> This review may not be exhaustive.  Please check your source package
> against your d/copyright and the ftpmaster REJECT-FAQ, throughly,
> before uploading to NEW again.
>
> Thank you for your time and contribution!
>
> Sean
>
>
>
>
> ===
>
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
>