Your message dated Fri, 31 Mar 2006 08:47:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#360210: fixed in gnome-keyring-sharp 0.0.1-8
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: gnome-keyring-sharp
Version: 0.0.1-7
Severity: serious

From my pbuilder build log:

...
checking GTK_SHARP_CFLAGS... 
-I:/usr/lib/pkgconfig/../../share/gapi-2.0/pango-api.xml 
-I:/usr/lib/pkgconfig/../../share/gapi-2.0/atk-api.xml 
-I:/usr/lib/pkgconfig/../../share/gapi-2.0/gdk-api.xml 
-I:/usr/lib/pkgconfig/../../share/gapi-2.0/gtk-api.xml
checking GTK_SHARP_LIBS... 
-r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll
checking for gapi-2.0 >= 1.9.0... Package gapi-2.0 was not found in the 
pkg-config search path. Perhaps you should add the directory containing 
`gapi-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gapi-2.0' 
found
configure: error: Library requirements (gapi-2.0 >= 1.9.0) not met; consider 
adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a 
nonstandard prefix so pkg-config can find them.
make: *** [configure-stamp] Error 1
-- 
Daniel Schepler


--- End Message ---
--- Begin Message ---
Source: gnome-keyring-sharp
Source-Version: 0.0.1-8

We believe that the bug you reported is fixed in the latest version of
gnome-keyring-sharp, which is due to be installed in the Debian FTP archive:

gnome-keyring-sharp_0.0.1-8.diff.gz
  to pool/main/g/gnome-keyring-sharp/gnome-keyring-sharp_0.0.1-8.diff.gz
gnome-keyring-sharp_0.0.1-8.dsc
  to pool/main/g/gnome-keyring-sharp/gnome-keyring-sharp_0.0.1-8.dsc
libgnome-keyring-cil_0.0.1-8_all.deb
  to pool/main/g/gnome-keyring-sharp/libgnome-keyring-cil_0.0.1-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Trotter <[EMAIL PROTECTED]> (supplier of updated gnome-keyring-sharp 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 31 Mar 2006 16:34:19 +0000
Source: gnome-keyring-sharp
Binary: libgnome-keyring-cil
Architecture: source all
Version: 0.0.1-8
Distribution: unstable
Urgency: low
Maintainer: Guido Trotter <[EMAIL PROTECTED]>
Changed-By: Guido Trotter <[EMAIL PROTECTED]>
Description: 
 libgnome-keyring-cil - C# bindings for the GNOME Keyring API
Closes: 360210 360239
Changes: 
 gnome-keyring-sharp (0.0.1-8) unstable; urgency=low
 .
   * Add build dependency on gtk-sharp2-gapi (closes: #360239, #360210)
Files: 
 7a467e81f88ce0a7fc1a88d6d1446338 803 libs optional 
gnome-keyring-sharp_0.0.1-8.dsc
 d0b509dabc3258265cf74d991362535f 5138 libs optional 
gnome-keyring-sharp_0.0.1-8.diff.gz
 8de11a6c82147afe4cf04816eaf1e657 7666 libs optional 
libgnome-keyring-cil_0.0.1-8_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFELVpshImxTYgHUpsRAjYCAJ48o9dNRymvAdbWMfNEVeRIJsXwEwCfbPGX
7eMvY69saP1IJk/kOoYmHZY=
=+NR0
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to