Bug#609581: calibre: summary of upstreams

2011-01-21 Thread Hamish
Package: calibre
Followup-For: Bug #609581

fwiw, some background history and modern day reading..

- poppler is a fork of xpdf, which (apparently) at the time of forking
was GPL2 only. thus poppler became GPL2 only as well.
http://cgit.freedesktop.org/poppler/poppler/tree/README
http://cgit.freedesktop.org/poppler/poppler/tree/README-XPDF


- in the mean time, xpdf, under the same author/company, and in the advent of
GPL3, has now become GPL2+.
  author contact: Derek B. Noonburg derekn  foolabs com
but that little + was missing at the time of poppler forking.
http://packages.debian.org/changelogs/pool/main/x/xpdf/xpdf_3.02-12/xpdf.copyright


- poppler asks that all contributions be given as GPL2+. so they are thinking
about it.
http://cgit.freedesktop.org/poppler/poppler/tree/README.contributors
(contact info for poppler given on that page)


so we have all actors and code moved to GPL2+ in principal, only the pedantic
twists of copyright law to satisfy. I've seen worse.


two easy ways out:
- poppler sync to a newer GPL2+ release of xpdf (not suitable in squeeze 
timeframe)
- someone, preferably a poppler dev, approach Derek and ask for a 
re/dual-license
of his (c)2004 xpdf as GPL2+. Then poppler adjust their READMEs as needed, 
reissue
a no-other-change tarball, the package gets rebuilt, and we can all get on with
more productive pursuits.


- as noted, calibre upstream has synced to GPL2+ as well. again, rebuild as 
needed
against the 0-diff GPL2+ release of calibre, or just ask calibre upstream for
a relicense/reissue of the older code used in the .deb under the GPL2+.


I ack the problem, but it all seems a little academic.. I suppose the clearest
path is for calibre to pressure poppler to prepare+release a clean  clear GPL2+
cut so this problem doesn't come up again in future. but easiest solution seems
a few emails from the authors saying + is fine appented to the shipped COPYING
file(s).


regards,
Hamish



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#609581: calibre: summary of upstreams

2011-01-21 Thread Jakub Wilk

* Hamish hamis...@yahoo.com, 2011-01-22, 00:18:
- in the mean time, xpdf, under the same author/company, and in the 
advent of GPL3, has now become GPL2+.


Any references for this? As far as I can see, the last release of xpdf 
was 3.02 (in 2007), and its README doesn't say anything about later 
versions of GPL. There were a few security patches released since then, 
but they don't change licensing.



http://packages.debian.org/changelogs/pool/main/x/xpdf/xpdf_3.02-12/xpdf.copyright


This looks like a bug in debian/copyright.

--
Jakub Wilk



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#609581: calibre: summary of upstreams

2011-01-21 Thread Sune Vuorela
On Friday 21 January 2011 12:18:26 Hamish wrote:
 Package: calibre
 Followup-For: Bug #609581
 
 fwiw, some background history and modern day reading..
 
 - poppler is a fork of xpdf, which (apparently) at the time of forking
 was GPL2 only. thus poppler became GPL2 only as well.
 http://cgit.freedesktop.org/poppler/poppler/tree/README
 http://cgit.freedesktop.org/poppler/poppler/tree/README-XPDF

true.

 - in the mean time, xpdf, under the same author/company, and in the advent
 of GPL3, has now become GPL2+.
   author contact: Derek B. Noonburg derekn  foolabs com
 but that little + was missing at the time of poppler forking.
 http://packages.debian.org/changelogs/pool/main/x/xpdf/xpdf_3.02-12/xpdf.co
 pyright

Erm? do you have any authorative souces for that? upstream homepage is very 
clear that it is gplv2only.

I think that there is a bug in the xpdf copyright file. CC'ing xpdf

 I ack the problem, but it all seems a little academic.. 

If your facts is correct, then I would agree. But I cannot find any sources to 
back up that claim.

/Sune



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org