licensing missing in bluez recipe #224
Labels
Comments
pabigot
added a commit
to pabigot/meta-raspberrypi
that referenced
this issue
May 7, 2018
Remove the material covered by the Cypress license from the bluez5 package and move it to its own package, derived directly from the upstream sources. Closes agherzan#224 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pabigot
added a commit
to pabigot/meta-raspberrypi
that referenced
this issue
May 7, 2018
Remove the material covered by the Cypress license from the bluez5 package and move it to its own package, derived directly from the upstream sources. Closes agherzan#224 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pabigot
added a commit
to pabigot/meta-raspberrypi
that referenced
this issue
May 9, 2018
Remove the material covered by the Cypress license from the bluez5 package and move it to its own package, derived directly from the upstream sources. Closes agherzan#224 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
agherzan
pushed a commit
that referenced
this issue
May 11, 2018
Remove the material covered by the Cypress license from the bluez5 package and move it to its own package, derived directly from the upstream sources. Closes #224 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The meta-raspberrypi bluez recipe contains and installs firmware that is presumably from Broadcom, but lacks a corresponding license and SPDX information. When RPi-Distro/bluez-firmware#1 is settled the recipe should be updated with this information.
I'm a little concerned about linux-firmware-raspbian too. The logs for that repository lack detail on provenance ("upstream tarball" is not a traceable source).
The text was updated successfully, but these errors were encountered: