Your message dated Sat, 19 May 2012 04:35:44 +0000
with message-id <[email protected]>
and subject line Re: your mail
has caused the Debian Bug report #673494,
regarding RFS: haskell-ncurses/0.2.1-1 [ITP] -- Haskell bindings to GNU ncurses
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.)
--
673494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673494
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-request
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "haskell-ncurses"
* Package name : haskell-ncurses
Version : 0.2.1-1
Version : 0.2.1-1
Upstream Author : John Millikin <[email protected]>
* URL : https://john-millikin.com/software/haskell-ncurses/
* License : GPL3+
Section : haskell
It builds those binary packages:
libghc-ncurses-dev - Haskell bindings to the GNU ncurses library
libghc-ncurses-doc - Haskell bindings to the GNU ncurses library;
documentation
libghc-ncurses-prof - Haskell bindings to the GNU ncurses library;
profiling libraries
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/haskell-ncurses
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/h/haskell-ncurses/haskell-ncurses_0.2.1-1.dsc
Changes since the last upload:
haskell-ncurses (0.2.1-1) unstable; urgency=low
* Initial release. (closes: #673212)
-- John Millikin <[email protected]> Thu, 17 May 2012 21:25:23 -0700
Regards,
John Millikin
--- End Message ---
--- Begin Message ---
On Fri, May 18, 2012 at 08:44:55PM -0700, John Millikin wrote:
> Sorry, I typo'd the component name when submitting this bug.
> Re-submitted with the correct component.
For future reference, you could have sent the following
to [email protected]:
reassign 673494 sponsorship-requests
quit
--- End Message ---
