Bug 92802

Summary:	Source tree includes AGPL code (qpaeq) without disclosing it at the top level
Product:	PulseAudio	Reporter:	Marc MERLIN <marc>
Component:	tools	Assignee:	pulseaudio-bugs
Status:	RESOLVED FIXED	QA Contact:	pulseaudio-bugs
Severity:	major
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	96750

Description Marc MERLIN 2015-11-04 01:25:15 UTC

https://github.com/pulseaudio/pulseaudio/blob/master/src/utils/qpaeq
is AGPL but pulseaudio is not.

AGPL is obviously a license that is problematic for some, and qpaeq seems to be a default build target for pulseaudio.
I'm putting this as major since it's important that each user knows what licenses they have to abide by and as of now they could be unknowingly violating the license.

IMO, one of those things ought to happen
1) qpaeq gets relicensed under GPL or some other license
2) qpaeq gets removed entirely or removed from default builds
3) top level https://github.com/pulseaudio/pulseaudio/blob/master/LICENSE warns about this AGPL bit and AGPL added in full at the top level

Comment 1 Tanu Kaskinen 2016-12-16 13:17:38 UTC

Thanks for the report! I'd like to change the qpaeq license from AGPL to LGPL, and I started that process by sending this email:
https://lists.freedesktop.org/archives/pulseaudio-discuss/2016-December/027252.html

If we don't get the license changed before the 10.0 release, I'll fix the top-level LICENSE file.

Comment 2 Tanu Kaskinen 2017-09-19 18:33:28 UTC

This was fixed already a while ago by adding a note about AGPL to the LICENSE file, but I forgot to close this bug. Now another thing happened: qpaeq changed its license to LGPL v2.1.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=61217528a1cb5043ca3fa1051a73ad3268cfb3d8

Comment 3 Marc MERLIN 2017-09-19 20:54:52 UTC

Thanks for resolving this, in this case in the best way possible.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.