[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980562: marked as done (RFS: shellingham/1.3.2-1 [ITP] -- Tool to Detect Surrounding Shell)

Your message dated Sat, 06 Feb 2021 19:58:04 -0500
with message-id <87mtwgk82r.fsf@paluero>
and subject line Re: Bug#980562: RFS: shellingham/1.3.2-1 [ITP] -- Tool to Detect Surrounding Shell
has caused the Debian Bug report #980562,
regarding RFS: shellingham/1.3.2-1 [ITP] -- Tool to Detect Surrounding Shell
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

980562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980562
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "shellingham":

 * Package name    : shellingham
   Version         : 1.3.2-1
   Upstream Author : Tzu-ping Chung <uranusjr@gmail.com>
 * URL             : https://github.com/sarugaku/shellingham
 * License         : ISC
 * Vcs             : https://salsa.debian.org/python-team/packages/shellingham
   Section         : python

It builds those binary packages:

  python3-shellingham - Tool to Detect Surrounding Shell

To access further information about this package, please visit the following URL:


Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/s/shellingham/shellingham_1.3.2-1.dsc

Changes for the initial release:

 shellingham (1.3.2-1) unstable; urgency=medium
   * Initial release (Closes: #980483)

  Emmanuel Arias

--- End Message ---
--- Begin Message ---
On Saturday, February 06 2021, Emmanuel Arias wrote:

> Hi,
> Thanks for the review. I've just push to salsa this fixes
> docs file.


>> 4) You're licensing the contents under debian/ as GPL-3+, which is a
>> different license than what upstream is using.  Is there any particular
>> reason that made you choose to do this?  Do you understand the
>> implications of choosing a different license than the one upstream is
>> using here?
> To be honest  no, I didn't have experience packaging an upstream package
> with ISC license, so, I felt more comfortable using a well know by me
> license. But, I will investigate the implications of choosing a different
> license, thanks for note me that.

So, it's always a good idea to license the contents of the debian/
directory with the same license as upstream's.  If the licenses are
different, you will likely have trouble submitting your changes to
upstream: the licenses may be incompatible, or upstream may not feel
comfortable accepting changes licensed differently.

Don't take me wrong: I personally license everything I do using GPL-3+,
but unfortunately when dealing with packages we have to adapt.

Thanks for the updates, uploaded.

GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply to: