GNOME Bugzilla – Bug 777203
gnulib license information is not correct in glib2.0
Last modified: 2017-03-09 17:19:42 UTC
GPLv3 header file is presnt in in glib 2.48 https://github.com/GNOME/glib/blob/master/glib/gnulib/verify.h and this file in included in https://github.com/GNOME/glib/blob/master/glib/gnulib/vasnprintf.c which makes glib2.0 package as GPLv3. Above issue was discussed in this tread https://mail.gnome.org/archives/gtk-devel-list/2016-December/msg00024.html As per this discussion, licensing information is wrongly updated as GPLv3 for glib/gnulib/verify.h and needs to be fixed.
This could definitely use some maintainership attention - our lawyers turned this up during a routine pre-release check and it might block us if we can't come to a resolution - we might be stuck reverting to an older glib.
Created attachment 347516 [details] [review] Regenerate the vasnprintf gnulib module imported files Use gnulibg-tool --lgpl to import the vasnprintf module using the correct GNU Lesser General Public License, version 2.1 or later, like the rest of GLib.
Created attachment 347568 [details] [review] Regenerate the vasnprintf gnulib module imported files Use gnulibg-tool --lgpl to import the vasnprintf module using the correct GNU Lesser General Public License, version 2.1 or later, like the rest of GLib.
I've re-imported the files, and kept all the changes from commit 212e4232e7520b2e328e3e965ed792e17b12e144 (see bug 756382) except for the newly added annotation for pure functions when using GCC ≥ 3, which seemed appropriate and it's not going to hurt. The re-import also ensures that all the files are marked as using the Lesser General Public License version 2.1 or later, instead of a mix of Library GPL v2 and Lesser GPL v2.1.
Review of attachment 347568 [details] [review]: Yes.
Attachment 347568 [details] pushed as c689039 - Regenerate the vasnprintf gnulib module imported files