Bug#935669: assaultcube-data (1.2.0.2.1-3) in enabled autobuilding
Hi Philipp, > Within the TEXTURES part of the "Other" license there are a few that do > not actually allow the textures to be shipped. Do we have a reasonable > assumption that it is actually the "Other" license's cover text that > applies to them? For instance I'm concerned about these (with no > expectation of covering them exhaustively): I understand that, in short, most of these licenses of each author of these textures were concerned with the commercialization of these textures and the non-disclosure of the authors. And many of these authors over the years have had their websites, blogs, and emails disabled. In the assaultcube-data package is disclosing all authors, contacts and their licenses. What I can do is research and contact these authors of these textures and let us know more about the license. If you find it necessary. Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Bug#935669: assaultcube-data (1.2.0.2.1-3) in enabled autobuilding
On 10/17/2019 1:53 AM, Carlos Donizete Froes wrote: > The assaultcube-data (1.2.0.2.1-3) package includes "XS-Autobuild: yes" in the > header portion of "debian/control"[1] and the disclaimer compliance with the > licenses contained in "debian/copyright"[2] where It's okay to create the > software automatically across multiple architectures and distribute it. > > [1] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/control > > [2] > https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/copyright > > If so, could you approve this package or do I need to target something else? Within the TEXTURES part of the "Other" license there are a few that do not actually allow the textures to be shipped. Do we have a reasonable assumption that it is actually the "Other" license's cover text that applies to them? For instance I'm concerned about these (with no expectation of covering them exhaustively): > All files and images may be used without restrictions in your projects. > It is prohibited to offer those files as part of other texture packs or sell > or > distribute them in any other way without prior permission from arcitool. > These textures are copyright (c) Ted Southard http://www.digitalflux.com > They are free to use for non commercial use. Re-packaging and selling as part > of a texture collection is strictly prohibited. > Where can I not use these textures? > Any webpage, program, or texture cd that has them available without > my permission is not permitted. You can however use them in a design scheme > for your site. > You are not allowed to spread them without giving the creators name, to > include > them in texture collections without a written permission and you strictly may > not offer them as textures for sale in any way. etc Kind regards Philipp Kern
Bug#935669: assaultcube-data (1.2.0.2.1-3) in enabled autobuilding
Hi, Am 17.10.19 um 01:53 schrieb Carlos Donizete Froes: > Hi, > > The assaultcube-data (1.2.0.2.1-3) package includes "XS-Autobuild: yes" in the > header portion of "debian/control"[1] and the disclaimer compliance with the > licenses contained in "debian/copyright"[2] where It's okay to create the > software automatically across multiple architectures and distribute it. > > [1] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/control > > [2] > https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/copyright > > If so, could you approve this package or do I need to target something else? > > Thanks! I believe the only thing that's missing is an email to nonf...@release.debian.org and ask them to accept assaultcube-data to be built on Debians buildd network in the future. https://www.debian.org/doc/manuals/developers-reference/ch05.html#non-free-buildd I hope they read this email and act accordingly. If you don't receive a response, we can still upload assaultcube-data but then we just need to remember to upload the binary packages as well because source-only uploads won't work. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#935669: assaultcube-data (1.2.0.2.1-3) in enabled autobuilding
Hi, The assaultcube-data (1.2.0.2.1-3) package includes "XS-Autobuild: yes" in the header portion of "debian/control"[1] and the disclaimer compliance with the licenses contained in "debian/copyright"[2] where It's okay to create the software automatically across multiple architectures and distribute it. [1] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/control [2] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/copyright If so, could you approve this package or do I need to target something else? Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
