Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

On 2017-01-13 13:17+0100, Adam Borowski wrote:
> On Fri, Jan 13, 2017 at 01:14:20PM +0100, Félix Sipma wrote:
>> Upstream updated the license to Expat, and I updated the license of debian/ 
>> to
>> GPL-3+
>> 
>> Please find the updated package there:
>> 
>>dget -x 
>> https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.1-1.dsc
> 
> I'm afraid that URL is 404-compliant.
> I can't find it on mentors.debian.net either.
> 
> Meow!

It's seems to work now. Maybe mentors took time to synchronize?


signature.asc
Description: PGP signature

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Adam Borowski]

On Fri, Jan 13, 2017 at 01:14:20PM +0100, Félix Sipma wrote:
> Upstream updated the license to Expat, and I updated the license of debian/ to
> GPL-3+
> 
> Please find the updated package there:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.1-1.dsc

I'm afraid that URL is 404-compliant.
I can't find it on mentors.debian.net either.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

Control: tag -1 -moreinfo

Upstream updated the license to Expat, and I updated the license of debian/ to
GPL-3+

Please find the updated package there:

dget -x 
https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.1-1.dsc


On 2017-01-11 11:27+0100, Adam Borowski wrote:
> Control: tag -1 +moreinfo
> 
> On Tue, Jan 10, 2017 at 02:38:00PM +0100, Félix Sipma wrote:
>> I am looking for a sponsor for my package "inkscape-open-symbols".
>>  inkscape-open-symbols - Open source SVG symbol sets that can be used as 
>> Inkscape symbols
>> 
>> Package: inkscape-open-symbols
>> Version: 1.0-1
>> Upstream Author: Xaviju 
>> Homepage: http://github.com/Xaviju/inkscape-open-symbols
>> License: GPL-2
>> Section: graphics
> 
>>dget -x 
>> https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.0-1.dsc
> 
> While from technical point of view it looks good, I'm afraid there's a
> license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
> problem between symbol sets -- there's mere aggregation without derivation
> or linking, but this can't be said for packaging.
> 
> Meow!


signature.asc
Description: PGP signature

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

On 2017-01-11 18:59+0100, Adam Borowski wrote:
> On Wed, Jan 11, 2017 at 06:32:59PM +0100, Félix Sipma wrote:
>> On 2017-01-11 11:27+0100, Adam Borowski wrote:
>>> While from technical point of view it looks good, I'm afraid there's a
>>> license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
>>> problem between symbol sets -- there's mere aggregation without derivation
>>> or linking, but this can't be said for packaging.
>> 
>> There's a discussion about the licensing there:
>> https://github.com/Xaviju/inkscape-open-symbols/issues/61
>> 
>> I'm not sure about how inkscape-open-symbols could be licensed (for now it's
>> GPL-2, so it's problematic, isn't it?)... Sure, it is a collection, but then,
>> what would be the difference with the Debian package?
> 
> The Debian packaging consists of nothing but a makefile (debian/rules) and a
> few assorted bits of metadata.  Hardly copyrightable, but above the commonly
> quoted threshold of copyrightability (~10 lines).
> 
> I might be wrong about the ftpmasters' point of view -- might be good to
> hear a clarification -- but I for one don't see a difference between
> aggregating two unrelated packages with conflicting licenses in one iso
> image, vs aggregating two unrelated symbol sets with conflicting licenses in
> one package, as long as they're clearly not derived from one another nor
> linked/etc.
> 
> So the only issue I see is license compatibility between the packaging
> and every of included symbol sets separately.  And here, any license
> compatible with both GPL-2 and GPL-3+ will do.

So, for you, if the inkscape-open-symbols is licensed under MIT (upstream
intends to do that), is there a problem or not?


signature.asc
Description: PGP signature

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Adam Borowski]

On Wed, Jan 11, 2017 at 06:32:59PM +0100, Félix Sipma wrote:
> On 2017-01-11 11:27+0100, Adam Borowski wrote:
> > While from technical point of view it looks good, I'm afraid there's a
> > license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
> > problem between symbol sets -- there's mere aggregation without derivation
> > or linking, but this can't be said for packaging.
> 
> There's a discussion about the licensing there:
> https://github.com/Xaviju/inkscape-open-symbols/issues/61
> 
> I'm not sure about how inkscape-open-symbols could be licensed (for now it's
> GPL-2, so it's problematic, isn't it?)... Sure, it is a collection, but then,
> what would be the difference with the Debian package?

The Debian packaging consists of nothing but a makefile (debian/rules) and a
few assorted bits of metadata.  Hardly copyrightable, but above the commonly
quoted threshold of copyrightability (~10 lines).

I might be wrong about the ftpmasters' point of view -- might be good to
hear a clarification -- but I for one don't see a difference between
aggregating two unrelated packages with conflicting licenses in one iso
image, vs aggregating two unrelated symbol sets with conflicting licenses in
one package, as long as they're clearly not derived from one another nor
linked/etc.

So the only issue I see is license compatibility between the packaging
and every of included symbol sets separately.  And here, any license
compatible with both GPL-2 and GPL-3+ will do.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

On 2017-01-11 11:27+0100, Adam Borowski wrote:
> While from technical point of view it looks good, I'm afraid there's a
> license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
> problem between symbol sets -- there's mere aggregation without derivation
> or linking, but this can't be said for packaging.

There's a discussion about the licensing there:
https://github.com/Xaviju/inkscape-open-symbols/issues/61

I'm not sure about how inkscape-open-symbols could be licensed (for now it's
GPL-2, so it's problematic, isn't it?)... Sure, it is a collection, but then,
what would be the difference with the Debian package?


signature.asc
Description: PGP signature

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

On 2017-01-11 11:27+0100, Adam Borowski wrote:
> Control: tag -1 +moreinfo
> 
> On Tue, Jan 10, 2017 at 02:38:00PM +0100, Félix Sipma wrote:
>> I am looking for a sponsor for my package "inkscape-open-symbols".
>> inkscape-open-symbols - Open source SVG symbol sets that can be used as 
>> Inkscape symbols
>> 
>> Package: inkscape-open-symbols
>> Version: 1.0-1
>> Upstream Author: Xaviju 
>> Homepage: http://github.com/Xaviju/inkscape-open-symbols
>> License: GPL-2
>> Section: graphics
> 
>>   dget -x 
>> https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.0-1.dsc
> 
> While from technical point of view it looks good, I'm afraid there's a
> license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
> problem between symbol sets -- there's mere aggregation without derivation
> or linking, but this can't be said for packaging.
> 
> Meow!

I've fixed some of the licenses (which where in fact GPL-2+). I'm trying to see
if upstream agrees to relicense inkscape-open-symbols to GPL-2+ and then I'll
do another package. Nice catch!


signature.asc
Description: PGP signature

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Adam Borowski]

Control: tag -1 +moreinfo

On Tue, Jan 10, 2017 at 02:38:00PM +0100, Félix Sipma wrote:
> I am looking for a sponsor for my package "inkscape-open-symbols".
>   inkscape-open-symbols - Open source SVG symbol sets that can be used as 
> Inkscape symbols
> 
> Package: inkscape-open-symbols
> Version: 1.0-1
> Upstream Author: Xaviju 
> Homepage: http://github.com/Xaviju/inkscape-open-symbols
> License: GPL-2
> Section: graphics

> dget -x 
> https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.0-1.dsc

While from technical point of view it looks good, I'm afraid there's a
license problem: you're mixing GPL-2 and GPL-3+.  I believe this is not a
problem between symbol sets -- there's mere aggregation without derivation
or linking, but this can't be said for packaging.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#850821: RFS: inkscape-open-symbols/1.0-1

[Félix Sipma]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inkscape-open-symbols".
  inkscape-open-symbols - Open source SVG symbol sets that can be used as 
Inkscape symbols

Package: inkscape-open-symbols
Version: 1.0-1
Upstream Author: Xaviju 
Homepage: http://github.com/Xaviju/inkscape-open-symbols
License: GPL-2
Section: graphics


Download with dget:

dget -x 
https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar https://git.gueux.org/inkscape-open-symbols.git
cd restic
gbp buildpackage


Thanks.


signature.asc
Description: PGP signature