After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683503 - Please clarify license of brasero (GPL-2.0+ or GPL-3.0+)
Please clarify license of brasero (GPL-2.0+ or GPL-3.0+)
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-06 14:42 UTC by Vincent Untz
Modified: 2018-09-21 17:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2012-09-06 14:42:58 UTC
COPYING for brasero is a GPL-2.0 COPYING. There are, however, examples of GPL-3.0 and LGPL-3.0 code in the tree. For example:

src/brasero-search-tracker.c
src/brasero-search-tracker.h
src/brasero-song-control.c
src/brasero-song-control.h
src/brasero-setting.c
src/brasero-setting.h

Compiling and linking these files with the rest of the (GPL-2.0+) code in
brasero is presumptively fine - but the license of the resulting derived work
should be GPL-3.0+, not GPL-2.0+.

I guess those headers were automatically created and using GPL-3.0+ by mistake.

Can this be confirmed and fixed? Alternatively, can the COPYING file be changed?
Comment 1 GNOME Infrastructure Team 2018-09-21 17:40:28 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/238.