Your message dated Tue, 17 Feb 2009 21:03:44 +0000
with message-id <e1lzx6w-0000is...@ries.debian.org>
and subject line Bug#509961: fixed in lmemory 0.6c-4
has caused the Debian Bug report #509961,
regarding lmemory: build with gtk+-2.0
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 ow...@bugs.debian.org
immediately.)
--
509961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lmemory
Version: 0.6c-3
Porting this to gtk+2 seems pretty trivial:
Index: lmemory-0.6c/configure.in
===================================================================
--- lmemory-0.6c.orig/configure.in 2008-12-27 19:35:58.000000000 -0500
+++ lmemory-0.6c/configure.in 2008-12-27 19:36:51.000000000 -0500
@@ -22,8 +22,8 @@
AC_STDC_HEADERS
AC_ARG_PROGRAM
-AM_PATH_GTK(1.2.0,,
- AC_MSG_ERROR(Cannot find correct version of GTK - is gtk-config in path?))
+AM_PATH_GTK_2_0(,,
+ AC_MSG_ERROR(Cannot find correct version of GTK))
dnl Checks for header files.
AC_HEADER_STDC
--- End Message ---
--- Begin Message ---
Source: lmemory
Source-Version: 0.6c-4
We believe that the bug you reported is fixed in the latest version of
lmemory, which is due to be installed in the Debian FTP archive:
lmemory_0.6c-4.diff.gz
to pool/main/l/lmemory/lmemory_0.6c-4.diff.gz
lmemory_0.6c-4.dsc
to pool/main/l/lmemory/lmemory_0.6c-4.dsc
lmemory_0.6c-4_i386.deb
to pool/main/l/lmemory/lmemory_0.6c-4_i386.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 509...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gonéri Le Bouder <gon...@rulezlan.org> (supplier of updated lmemory 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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 17 Feb 2009 00:26:15 +0100
Source: lmemory
Binary: lmemory
Architecture: source i386
Version: 0.6c-4
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team <pkg-games-de...@lists.alioth.debian.org>
Changed-By: Gonéri Le Bouder <gon...@rulezlan.org>
Description:
lmemory - A children's game based on the "memory" card game
Closes: 509961 509962
Changes:
lmemory (0.6c-4) unstable; urgency=low
.
[ Peter De Wachter ]
* Added watch file.
.
[ Gonéri Le Bouder ]
* Build with gtk+-2.0, Closes: #509961
* Fix the build system, Closes: #509962
- call autoreconf, and then add a builddeps on autoconf, automale,
libtool
- add ac_local_program.diff to avoid a warning
* Add a .desktop file
* use dh_install to install the pixmaps
* Add myself in Uploaders:
Checksums-Sha1:
4abe6a7e540e644477ce574ff2d52f67b8d16699 1272 lmemory_0.6c-4.dsc
acd151770846c5b2604defc0b10b5eaa29045add 153170 lmemory_0.6c-4.diff.gz
d079294d77b3603f70a1f7ffb32183a786e2e7db 166092 lmemory_0.6c-4_i386.deb
Checksums-Sha256:
ccf73df305bda146f8271b9d65cce21e20a13ec74e8ab50548489d4637796f4d 1272
lmemory_0.6c-4.dsc
41dde0c4ec475583416057c71f931c027ce40a11af68f6c8631dd55b1569265f 153170
lmemory_0.6c-4.diff.gz
bdc6bee4402dc9250607af223689ded4da01bf66238507646e2729db5fe406a8 166092
lmemory_0.6c-4_i386.deb
Files:
83d9387804a535684171ec9aeec71310 1272 games optional lmemory_0.6c-4.dsc
8735b7c15583a3b069eb98ceb62fbbc2 153170 games optional lmemory_0.6c-4.diff.gz
eea034c14d21dae34c255e40bd5c3013 166092 games optional lmemory_0.6c-4_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmbIx0ACgkQsKTFpDfZQSxNhQCfU/kxZeDdQ8Lx1H/+mlQfetco
a1kAn2pXVeY/lCiYlHmV5STpWseLNo+u
=UKtU
-----END PGP SIGNATURE-----
--- End Message ---
