[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

libidn re-license

I co-maintain the libidn package.  As upstream, I recently relicensed it
from LGPLv2+ to GPLv2+|LGPLv3+.  I'd like to upload the latest version
into Debian before Wheezy since a pretty nasty inifinte-loop bug has
been fixed.  However, I am not certain what should be done before
uploading a re-licensed package, so I am asking for guidance.  I have
looked at licenses of reverse dependencies, and I did found some
GPLv2-only packages.  That caused me to dual license the package instead
of going to LGPLv3+. (GPLv2-only and LGPLv3+ are incompatible.)  I am
not aware of any other license that could pose any problem with a
dual-licensed GPLv2+|LGPLv3+ package.  I didn't find any other obvious
problem when I looked at the reverse dependencies.

Is there any policy or best current practice about what needs to be done
in this situation?  Should I just upload to unstable and let people work
out license (in)compatibility later on?  I'm sure this must have come up
before for other packages that have been relicensed, but I couldn't find
any generic advice.


Reply to: