Your message dated Fri, 18 May 2007 22:56:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in upload of 1.0.0-1.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libgpgme-ruby
Version: 0.2-2
Severity: wishlist

A new upstream release (0.3) is available at[1]. Apparently, only a
minor change is required to build the new version: build-depend on
libgpgme11-dev instead of libgpgme-dev.

 1. http://deisui.org/~ueno/ruby/ruby-gpgme/ruby-gpgme-0.3.tar.gz

Thanks.


--- End Message ---
--- Begin Message ---
Hello,

A month ago an upload of libgpgme-ruby 1.0.0-1 has occurred:

libgpgme-ruby (1.0.0-1) unstable; urgency=low

  [ Rudi Cilibrasi ]
  * I am taking stewardship of the package for now as maintainer.
  * New upstream version.
  * Changed Build-Deps to specify libgpgme11-dev.
  * Updated Standards to 3.7.2.

  [ Paul van Tilburg ]
  * Updated homepage URL in debian/control and debian/watch,
    since the project moved to RubyForge.
  * Added myself to the Uploaders, currently acting as sponsor.
  * Adapted debian/rules, and removed debian/control.in to drop
    the Uploaders rule.

 -- Paul van Tilburg <[EMAIL PROTECTED]>  Wed, 18 Apr 2007 22:30:24 +0200


This bugreport can therefore be considered closed.

Paul

-- 
Student @ Eindhoven                         | email: [EMAIL PROTECTED]
University of Technology, The Netherlands   | JID: [EMAIL PROTECTED]
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181

--- End Message ---

Reply via email to