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

Re: RFS: gvb



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Jun 22, 2008 at 12:27:28PM +0200, Holger Levsen wrote:
>On Sunday 22 June 2008 11:36, Jonas Smedegaard wrote:
>> >(And then debian/copyrights refers to 
>> >/usr/share/common-licences/GPL, which is the GPL3, so that's another 
>> >(normal) bug.)
>> Why is that (the last part) a bug?  GPL2+ _includes_ GPL3, so 
>> pointing to that newer version of the license should be ok, no?
>
>The GPL3+ licence doesnt include GPL2 so by pointing to the GPL3+ only 
>you are leaving some information out. I consider this buggy. (But as 
>said, normal severity, maybe even minor.)
>
>It's like depending on python2.5 when the software runs just as fine 
>with python2.4.
>
>I discussed this issue over yesterday (with my Debian Edu ftpmaster 
>hat), first with Petter (who uploaded a package with such a copyright), 
>then with Jörg Jaspert (as Debian ftpmaster). At first I consided this 
>bug to be RC, but now I agree that, while not perfectly correct, this 
>is not serious at all.

This could give the impression that Jörg and Petter agrees with you on 
this, but really you only say that discussing with them made you relax 
your standpoint from RC to normal.

I still fail to understand why it is a bug to refer to GPLv3 when the 
copyright holder permits to redistribute under...

>either version 2 of the License, or (at your option) any later version.


Was those discussions with Petter and Jörg made in public somewhere?  
Then perhaps simply referring to them will enlighten me, to avoid the 
need for repeating your arguments here ;-)


  - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  - Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkheMWkACgkQn7DbMsAkQLizhACdFFKIlfphqvi2Ln9UZXqO6J3o
lFIAnilHbMGYWaJ5iJts1vUvnKnZmecN
=VKNe
-----END PGP SIGNATURE-----


Reply to: