Bug#728360: RFS: open-axiom/1.5.0~svn3056-1
Hi,
>> Some files in the source tree are licensed under GPL-2+ and Expat licenses.
>>
>> But I have checked only [1] output. Please have in mind that it includes not
>> full info and all blocks with "Copyright: *No copyright*" and
>> "License: UNKNOWN" should be checked manually.
>>
>> [1] licensecheck --copyright -c . -r . | /usr/lib/cdbs/licensecheck2dep5 > ../copyright_
>
> BTW, how should I refer to these terms:
> # As a special exception to the GNU General Public License, if you
> # distribute this file as part of a program that contains a
> # configuration script generated by Autoconf, you may include it under
> # the same distribution terms that you use for the rest of that program.
> ?
You may write something like this:
Files: config/*
Copyright: 1992-2013, Free Software Foundation, Inc
License: GPL-2+ or BSD-3-clause
These files are free software; you can redistribute them and/or modify
them under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
02110-1301, USA.
.
As a special exception to the GNU General Public License, if you
distribute this file as part of a program that contains a
configuration script generated by Autoconf, you may include it under
the same distribution terms that you use for the rest of that program.
I have looked at your debian/copyright in git repo. It may be much simpler:
http://paste.debian.net/plain/67414
As you see, all blocks were sorted by license, instead of specific files or
copyright holders.
>> And how about maintaining this package under umbrella of Debian Science Team?
>
> I don't mind. What should I do?
Send the join request from [1]. Once admin add you to Alioth team, your name
will appear in the list of members [2]. Have in mind that you will not receive
an email about this, unfortunately.
[1] https://alioth.debian.org/projects/debian-science/
[2] https://alioth.debian.org/project/memberlist.php?group_id=100159
When you will have push access to Debian Science Team repos, we will move your
old git repo to new location and will make a symlink at old location to new
one.
And finally, you should update debian/control in according to Debian Science
Policy Manual [3]. See requirements about Maintainer, Uploaders and Vcs-*
fields.
[3] http://debian-science.alioth.debian.org/debian-science-policy.html
(Have in mind that some information is a bit outdated here.)
That is all, if I have not missed anything.
Best regards,
Boris
Reply to: