bugGNU dbm - Bugs: bug #157, License change back to GPLv2+

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #157: License change back to GPLv2+

Submitted by:  Honza Horak <hhorak>
Submitted on:  Tue Dec 13 09:14:38 2011  
 
Category: NonePriority: 5 - Normal
Severity: 5 - NormalStatus: Wont Fix
Privacy: PublicAssigned to: None
Open/Closed: Closed

Mon Jan 29 14:11:50 2018, comment #5:

Hi,
what it status of this? Did you find a solution with Thorsten?

I see that ypserv is still GPLv2 so it can't be linked with gdbm under GPLv3 - https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility

Marek Skalický <mskalick>
Thu Apr 12 07:59:21 2012, comment #4:

Thanks, I'll contact Thorsten and try to find out a solution. I'll let you know about the result.

As to the "why", GDBM is a GNU package and GPLv3 is a part of GNU policy, which it is my duty as a maintainer to promote.

Sergey Poznyakoff <gray>
Project Administrator
Thu Apr 12 07:23:44 2012, comment #3:

I'm very sorry to hear that, because ypserv's maintainer Thorsten is not willing or even able to change the license as well. He sais it's because he can't get all needed permissions from all former contributors and he also simply doesn't like GPLv3. If you can speak to him, try to convince, I'd be very grateful. You can find his mail at https://www.linux-nis.org.

Anyway, why is it impossible to change the license back to GPLv2+ or LGPLv2.1? If you made all changes since version 1.9, it should be legal re-license it. Do you have any other particular reason?

Honza Horak <hhorak>
Wed Apr 11 08:22:49 2012, comment #2:

Sorry, but that's impossible. If anybody has problems upgrading their license, please tell him to get in touch with me. Perhaps we will be able to make out a solution for a particular case.

In any case, changing back the license of GDBM is not an option.

Sergey Poznyakoff <gray>
Project Administrator
Wed Apr 11 07:22:28 2012, comment #1:

Please, consider changing gdbm license, since it's a pain issue for anybody who cares about licenses. Another compatible solution would be changing gdbm to LGPLv2.1(+). I'd like to hear your opinion.

Honza Horak <hhorak>
Tue Dec 13 09:14:38 2011, original submission:

It turned out recently, that the license change from GPLv2+ to GPLv3+ introduced license incompatibility between projects, which are GPLv2 only. Projects with conflict I'm aware of are ypserv (NIS) and ruby-libs-1.8.3.

Negotiation with the authors of that packages also turned out that it is not possible to re-license these projects to a compatible license, which placed us in the position where we cannot legally use gdbm in these projects.

There are probably some more projects with the same incompatibility, that I'm not aware of, and I expect it will became a bigger problem as soon as gdbm-1.9 or later will be used in other distributions as well (now it is problem in Fedora at least).

I'd like to ask you if gdbm could be re-license back to GPLv2+, which will solve all the problems.

Honza Horak <hhorak>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by mskalick (Posted a comment)
  • -unavailable- added by gray (Posted a comment)
  • -unavailable- added by hhorak (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    2 latest changes follow.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Feb 6 09:55:30 2021grayOpen/ClosedOpen=>Closed
    Wed Apr 11 08:22:49 2012grayStatusNone=>Wont Fix
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup+gray