From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Calibre
Date: Tue, 17 Feb 2015 16:35:44 -0500 [thread overview]
Message-ID: <878ufw8bm7.fsf@netris.org> (raw)
In-Reply-To: <20150217203056.GB30365@debian> (Andreas Enge's message of "Tue, 17 Feb 2015 21:30:56 +0100")
Andreas Enge <andreas@enge.fr> writes:
> On Tue, Feb 17, 2015 at 12:02:00AM -0500, Mark H Weaver wrote:
>> The calibre source tarball contains non-free software. Debian
>> distributes their own excerpted source tarball instead, with the
>> src/unrar, src/calibre/ebooks/markdown, and resources/viewer/mathjax
>> directories removed, as well as src/odf/thumbnail.py.
>
> Amazing, thanks for looking into it. How do you find out which files
> debian drops?
I downloaded Debian's 'dfsg' source tarball, and the upstream source
tarball, and used 'diff' to find the diferences.
> I suppose that a "dfsg" in the package name is a warning
> sign?
Yes, although in many cases it is because the GNU Free Documentation
License doesn't comply with Debian's DFSG when invariant sections are
used.
> This is even more surprising as there is the file COPYRIGHT
> in the distribution, which diligently lists the licenses of lots of
> packages, except apparently for the non-free ones...
Debian's copyright file only lists the licenses of what they included in
their source package, so anything they removed is not included.
>> (2) src/calibre/ebooks/markdown/serializers.py license includes the text:
>>
>> --8<---------------cut here---------------start------------->8---
>> # By obtaining, using, and/or copying this software and/or its
>> # associated documentation, you agree that you have read, understood,
>> # and will comply with the following terms and conditions:
>> #
>> # Permission to use, copy, modify, and distribute this software and
>> # its associated documentation for any purpose and without fee is
>> # hereby granted, provided that the above copyright notice appears in
>> # all copies, and that both that copyright notice and this permission
>> # notice appear in supporting documentation, and that the name of
>> # Secret Labs AB or the author not be used in advertising or publicity
>> # pertaining to distribution of the software without specific, written
>> # prior permission.
>> --8<---------------cut here---------------end--------------->8---
>>
>> I'm not as confident that this one is a problem, partly because I
>> guess it is probably unenforceable, but the first paragraph is
>> attempting to put a restriction on use. They are saying that you're
>> not even allowed to use this software unless you have "read,
>> understood, and will comply with ...".
>
> I suppose that the first sentence merely states "the following license
> is valid", so I do not think it is a real problem. One always needs to
> comply with the license, no?
No. Normally one only has to comply with the license if you do
something that would violate copyright law, e.g. redistribution.
Mark
next prev parent reply other threads:[~2015-02-17 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 10:20 Calibre Andreas Enge
2015-02-17 4:23 ` Calibre Mark H Weaver
2015-02-17 20:21 ` Calibre Andreas Enge
2015-02-17 5:02 ` Calibre Mark H Weaver
2015-02-17 20:30 ` Calibre Andreas Enge
2015-02-17 21:35 ` Mark H Weaver [this message]
2015-02-17 21:50 ` Calibre Andreas Enge
2015-02-17 22:09 ` Calibre Mark H Weaver
2015-02-17 22:17 ` Calibre Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ufw8bm7.fsf@netris.org \
--to=mhw@netris.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.