Hi,
> > >I did all that was doable in a reasonable time. As said before, for what need >more >time and/or help from upstream, I've kept track of it in README.source ok >done, thanks ok >Yes, we'll try to do something with upstream, but I couldn't do that in >a trivial way. As explained tests create VMs. >This is tracked in README.source though. that might be an issue :) >Actually I based the licensing of that file on that same file : >http://sources.debian.net/src/spice-html5/0.1.4-1/debian/copyright/?hl=13#L13 >I can ask the maintainer there if he knows more. if other packages have the same license might be fine then, but please double check :) >I guess upstream didn't update the files. I'll sent a mail to them to ask. thanks >./m4/*.m4:dnl Copyright (C) 1996-2003, 2009-2010 Free Software Foundation, >./po/Makefile.in.in:# Copyright (C) 1995-1997, 2000-2007, 2009-2010 by Ulrich >Drepper <drep...@gnu.ai.mit.edu> >./plugins/sample/po/Makefile.in.in:# Copyright (C) 1995-1997, 2000-2007, >2009-2010 by Ulrich Drepper <drep...@gnu.ai.mit.edu> >./config.rpath:# Copyright 1996-2010 Free Software Foundation, Inc. >./INSTALL:Copyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software >Foundation, >./INSTALL:are permitted in any medium without royalty provided the copyright >./build-aux/config.rpath:# Copyright 1996-2010 Free Software Foundation, Inc. >./build-aux/pkg-version:# Copyright 2008-2012 Red Hat, Inc. > >not sure how to deal with those : they specify a copyright but no license >except things like "unlimited permission to copy and/or distribute it, with or >without modifications, as long as this notice is preserved." >So, does this means that they will fall under the license of the project >(LGPL-3) or are those small notices considered as a license by itself? yes, fine for them :) >COPYING specifies LGPL-3 ; do you mean people generally use LGPL-3+ and that >upstream may have done a typo ? I'll ask. yes please, I usually see LGPL-3+, and it is a little bit more permissive (not right now, but it might become in a future version) >will do thanks >Indeed! good suggestion given the number of python deps pulled and it seems to >change quite often. >I will ask for this too. thanks, unfortunately you still need to have them in build-dependencies, but not in runtime-dependencies (please check the DEBIAN/control in the binary package if everything went good) and please tell somewhere the package name, because I forgot it (and I'm too lazy to check) cheers, G.
