Your message dated Thu, 26 May 2016 11:35:41 +0000 (UTC)
with message-id <[email protected]>
and subject line Re: Bug#811455: RFS: qhttpengine/0.1.0+dfsg1-1 [ITP]
has caused the Debian Bug report #811455,
regarding RFS: qhttpengine/0.1.0+dfsg1-1 [ITP]
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 [email protected]
immediately.)
--
811455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811455
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "qhttpengine"
* Package name : qhttpengine
Version : 0.1.0+dfsg1-1
Upstream Author :Nathan Osman <[email protected]>
* URL :https://github.com/nitroshare/qhttpengine
* License : MIT
Section : libs
It builds those binary packages:
libqhttpengine-dbg - HTTP server for Qt applications - debug info
libqhttpengine-dev - HTTP server for Qt applications - development files
libqhttpengine-doc - HTTP server for Qt applications - documentation
libqhttpengine-examples - HTTP server for Qt applications - examples
libqhttpengine0 - HTTP server for Qt applications
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/qhttpengine
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/q/qhttpengine/qhttpengine_0.1.0+dfsg1-1.dsc
More information about qhttpengine can be obtained
fromhttps://github.com/nitroshare/qhttpengine.
Regards,
Nathan Osman
--- End Message ---
--- Begin Message ---
Hi
>First of all, I apologize for the mix-up. I wasn't paying very close
>attention to who was sending the emails. I think I've got it all
>straightened out now :)
not a problem at all :)
>As described below, I've made the changes you requested and made the
>adjustment for observing TMPDIR as Mattia suggested. Please let me know
>if you have any further questions or if there are any other changes I
>need to make.
I'm going to upload right now, as soon as the connection allows me to do it.
For a future upload please consider enabling hardening flags.
https://wiki.debian.org/HardeningWalkthrough
thanks,
Gianfraco
On 2016-05-24 01:28 AM, Mattia Rizzolo wrote:
> On Mon, May 23, 2016 at 08:37:46PM -0700, Nathan Osman wrote:
>> I apologize for not getting back to you sooner. I completely forgot to reply
>> to your last email.
> Well, it was not mine, it was from Gianfranco.
>
>> I removed the debug package, bumped the standards version, and removed the
>> Lintian override. As for the test suite, I was able to reproduce the failure
>> and found the cause of the problem: the test suite expects the $HOME
>> environment variable to be set to a valid directory. I worked around this
>> problem by manually setting $HOME to /tmp in debian/rules. Please let me
>> know if there is anything wrong with this.
> I'll let Gianfranco check it again, but anyway, for the bit of setting
> HOME to /tmp, please also respect TMPDIR¹. So, if TMPDIR is set, you
> should do HOME=${TMPDIR:-/tmp} (bash syntax).
>
> ¹ https://en.wikipedia.org/wiki/TMPDIR
--- End Message ---
