--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "hexchat"
Package name : hexchat
Version : 2.9.6.1-1
Upstream Author : Berke Viktor
URL : http://hexchat.github.io
License : GPL-2 with OpenSSL exception
Section : net
It builds these binary packages:
hexchat - IRC client for X based on X-Chat 2
hexchat-common - Common files for HexChat
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/hexchat
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/h/hexchat/hexchat_2.9.6.1-1.dsc
More information about HexChat can be obtained from http://hexchat.github.io/
and http://hexchat.readthedocs.org/.
Please let me know if you need any more information.
Regards,
Jesse Rhodes (sney)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Tue, Feb 18, 2014 at 6:46 PM, Jesse Rhodes <drubo@drubo.net> wrote:
> Hi Vincent,
>
> Here's the rest:
>
> 1) Recommends line moved back to where it should be
>
> 2) There is no doxygen-built documentation distributed with this
> package; I discussed it with #debian-mentors and they seemed to think
> that the Doxyfile in the upstream tarball is only there for
> development purposes and its output wouldn't be necessary in a binary
> distribution. (The plugin interface is documented separately, and
> already included in hexchat-common.)
>
> 3) I turned on verbose building and -D_FORTIFY_SOURCE=2 is indeed
> being used when python.so is being compiled, so that would make this
> an upstream issue, correct? Anything in particular I should mention
> when I report it to them?
>
> 4) The weird debian/rules targets were because I referred to the xchat
> package for examples, and its debian/rules may have been written
> originally before dh overrides were available/widely known. What I did
> worked, so I accepted it and moved on. I have switched the format to
> override_dh_* targets now.
>
> 5) debian/watch updated.
>
> Let me know your thoughts on the license exception, as well as point 2
> in this email, and then I'll re-upload with the final decision.
For those following along on #738683, the remaining issues were solved
on #debian-mentors.
Anyways, built, signed, and uploaded; thanks for your contribution to Debian!
Regards,
Vincent
--- End Message ---