Bug#872571: marked as done (RFS: injeqt/1.1.0-1.1 [RC])
Your message dated Wed, 23 Aug 2017 15:56:51 +0200
with message-id <20170823135651.2evsebn3gyxqwkh3@angband.pl>
and subject line Re: Bug#872571: RFS: injeqt/1.1.0-1.1 [RC]
has caused the Debian Bug report #872571,
regarding RFS: injeqt/1.1.0-1.1 [RC]
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
immediately.)
--
872571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872571
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "injeqt"
* Package name : injeqt
Version : 1.1.0-1.1
Upstream Author : Rafał Malinowski
<rafal.przemyslaw.malinowski@gmail.com>
* URL : https://github.com/vogel/injeqt
* License : LGPL-2.1
Section : libs
It builds those binary packages:
libinjeqt-dev - Dependency injection framework for Qt
libinjeqt1 - Dependency injection framework for Qt
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/injeqt
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/i/injeqt/injeqt_1.1.0-1.1.dsc
Changes since the last upload:
* Non-maintainer upload.
* Add patch to fix ftbfs with GCC-7. (Closes: #853452)
Regards,
Mateusz Łukasik
--- End Message ---
--- Begin Message ---
On Fri, Aug 18, 2017 at 08:25:59PM +0200, Mateusz Łukasik wrote:
> * Package name : injeqt
> Version : 1.1.0-1.1
> Changes since the last upload:
>
> * Non-maintainer upload.
> * Add patch to fix ftbfs with GCC-7. (Closes: #853452)
The NMU procedure requires posting the proposed debdiff to the bug before
making the upload. I've just done so, but in the future it'd be nice if you
(plural "you") could send the debdiff when requesting sponsoring; this would
give the maintainer a chance to react if there's something bad with the
upload, especially something the sponsor may miss or not know about.
Uploaded.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀
--- End Message ---
Reply to: