BerkeleyDB has recently been relicensed by Oracle (to AGPLv3) -- Debian discussion as covered by LWN here:
http://lwn.net/Articles/557487/ http://lwn.net/Articles/557487/#Comments
Given that the older 5.x version is used by multiple packages (most notably RPM), not all of which are AGPLv3-compatible, perhaps we need to discuss the implications of this re-license?
1. Fork BDB 5.x 2. Audit the dependents to see which have incompatible licenses (off the top of my head, GPLv2-only, GPLv3, GPLv3+ -- GPLv2+ will simply become AGPLv3) 3. ... ?
Here are the packages we currently have that build against libdb-devel:
389-ds-base-0:1.3.1.2-1.fc19.src apr-util-0:1.4.1-8.fc19.src clisp-0:2.49-9.20130208hg.fc19.src compat-libgda-0:3.1.2-10.fc19.src cyrus-imapd-0:2.4.17-2.fc19.src cyrus-sasl-0:2.1.26-8.fc19.src cyrus-sasl-0:2.1.26-9.fc19.src dsniff-0:2.4-0.15.b1.fc19.src evolution-data-server-0:3.8.3-1.fc19.src exim-0:4.80.1-3.fc19.src hail-0:0.8-0.13.gf9c5b967.fc19.src iproute-0:3.9.0-1.fc19.src isync-0:1.0.6-1.fc19.src jigdo-0:0.7.3-17.fc19.src libetpan-0:1.1-5.fc19.src libgda-1:5.1.2-2.fc19.src libpinyin-0:0.9.92-1.fc19.src libpinyin-0:0.9.93-1.fc19.src libsolv-0:0.3.0-3.git7399ad1.fc19.src libsolv-0:0.3.0-5.git228d412.fc19.src nmh-0:1.5-4.fc19.src nss_updatedb-0:10-6.fc19.src nvi-0:1.81.6-7.fc19.src opendkim-0:2.8.3-2.fc19.src openldap-0:2.4.35-4.fc19.src openldap-0:2.4.35-5.fc19.src openser-0:1.3.4-28.fc19.src opensips-0:1.8.2-6.fc19.src pam-0:1.1.6-11.fc19.1.src pam_abl-0:0.5.0-2.fc19.src pam_ccreds-0:10-7.fc19.src perl-4:5.16.3-264.fc19.src perl-4:5.16.3-265.fc19.src perl-BDB-0:1.90-4.fc19.src perl-BerkeleyDB-0:0.51-4.fc19.src perl-Digest-MD4-0:1.9-1.fc19.src perl-Qt-0:0.96.0-6.fc19.src perl-eperl-0:2.2.14-23.fc19.src php-0:5.5.0-0.10.RC3.fc19.src php-0:5.5.0-1.fc19.src postfix-2:2.10.0-2.fc19.src postfix-2:2.10.1-1.fc19.src postler-0:0.1.1-12.fc19.src python-0:2.7.5-1.fc19.src qpid-cpp-0:0.20-6.fc19.src qpid-cpp-0:0.22-1.1.fc19.src qpid-cpp-0:0.22-2.fc19.src redland-0:1.0.16-2.fc19.src rpm-0:4.11.0.1-2.fc19.src ruby-0:2.0.0.195-8.fc19.src ruby-0:2.0.0.247-11.fc19.src sendmail-0:8.14.7-1.fc19.src sks-0:1.1.4-1.fc19.src spamprobe-0:1.4d-4.fc19.src squidGuard-0:1.4-17.fc19.src subversion-0:1.7.10-1.fc19.src tabled-0:0.5.2-2.fc19.src webalizer-0:2.23_05-7.fc19.src xemacs-0:21.5.33-5.fc19.src zinnia-0:0.06-16.fc19.src
Best regards,
On Thu, 2013-07-04 at 16:03 +0700, Michel Alexandre Salim wrote:
BerkeleyDB has recently been relicensed by Oracle (to AGPLv3) -- Debian discussion as covered by LWN here:
[... snip ...]
Here are the packages we currently have that build against libdb-devel:
Did libdb-cxx also get relicensed?
If so:
canl-c++-0:1.0.0-2.fc18.src libcangjie-0:0.0.1a-3.fc18.src nordugrid-arc-0:3.0.2-1.fc18.src poedit-0:1.5.4-4.fc18.src
On Thu, Jul 4, 2013 at 4:32 PM, Mathieu Bridon bochecha@fedoraproject.orgwrote:
On Thu, 2013-07-04 at 16:03 +0700, Michel Alexandre Salim wrote:
BerkeleyDB has recently been relicensed by Oracle (to AGPLv3) -- Debian discussion as covered by LWN here:
[... snip ...]
Here are the packages we currently have that build against libdb-devel:
Did libdb-cxx also get relicensed?
Yes, it's built from the same SRPM:
http://koji.fedoraproject.org/koji/buildinfo?buildID=422462
From upstream changelog, it would seem that the change was made in 6.0.20
so we might be able to upgrade up to 6.0.19
http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_6_0.ht...
I've also flagged the license change in the automatic bug created by upstream release monitoring: https://bugzilla.redhat.com/show_bug.cgi?id=973056
If so:
canl-c++-0:1.0.0-2.fc18.src libcangjie-0:0.0.1a-3.fc18.src nordugrid-arc-0:3.0.2-1.fc18.src poedit-0:1.5.4-4.fc18.src
Best regards,
On 07/04/2013 02:34 PM, Michel Alexandre Salim wrote:
From upstream changelog, it would seem that the change was made in 6.0.20 so we might be able to upgrade up to 6.0.19
The license change was already mentioned in the 6.0.19 release announcement, so the licensing status of 6.0.19 is at best unclear.