Your message dated Sun, 29 Apr 2012 08:48:30 +0000
with message-id <e1sopny-0001pg...@franck.debian.org>
and subject line Bug#666232: fixed in gitg 0.2.4-1.1
has caused the Debian Bug report #666232,
regarding gitg: FTBFS with gtk 3.4
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.)
--
666232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitg
Version: 0.2.4-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-3.4-ftbfs
Hi,
gtk 3.4 will be part of the upcoming GNOME 3.4 release.
A 3.4.0 release of gtk is available in experimental.
During a test-rebuild gitg failed to build with the new gtk 3.4
You can find the full build log at [1].
In most cases, this is due to the usage of deprecated API [2] and
gitg using -Werror.
Please update gitg at your earliest convenience, so once we move
gtk 3.4 from experimental to unstable, your package will remain
buildable. We plan on uploading gtk-3.4 in a few days.
Thanks!
Michael,
on behalf of the Debian GNOME team.
[1] http://people.debian.org/~biebl/gtk-3.4/gitg_0.2.4-1.log
[2] http://developer.gnome.org/gtk3/3.4/api-index-deprecated.html
--- End Message ---
--- Begin Message ---
Source: gitg
Source-Version: 0.2.4-1.1
We believe that the bug you reported is fixed in the latest version of
gitg, which is due to be installed in the Debian FTP archive:
gitg_0.2.4-1.1.debian.tar.gz
to main/g/gitg/gitg_0.2.4-1.1.debian.tar.gz
gitg_0.2.4-1.1.dsc
to main/g/gitg/gitg_0.2.4-1.1.dsc
gitg_0.2.4-1.1_amd64.deb
to main/g/gitg/gitg_0.2.4-1.1_amd64.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 666...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
wujiang <masterwuji...@gmail.com> (supplier of updated gitg 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: RIPEMD160
Format: 1.8
Date: Sun, 29 Apr 2012 13:57:01 +0800
Source: gitg
Binary: gitg
Architecture: source amd64
Version: 0.2.4-1.1
Distribution: unstable
Urgency: low
Maintainer: Jonny Lamb <jo...@debian.org>
Changed-By: wujiang <masterwuji...@gmail.com>
Description:
gitg - git repository viewer for gtk+/GNOME
Closes: 666232
Changes:
gitg (0.2.4-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Replaced deprecated gdk_window_get_pointer API. (Closes: #666232)
+ debian/patches/ftbfs: Added.
Checksums-Sha1:
850dcf4f27516af8d6f4d8dbea5996f305baad23 1336 gitg_0.2.4-1.1.dsc
a62b46a4105c609d68c7f5075e63d906c032deea 5909 gitg_0.2.4-1.1.debian.tar.gz
d4d694dab81894cca9a8e3a480a8e8be92094dff 293724 gitg_0.2.4-1.1_amd64.deb
Checksums-Sha256:
d6db724f4a6398c19b1ffaceb0759c8a3c3ba397a34f692061f36ca62673cbd8 1336
gitg_0.2.4-1.1.dsc
b1cc68c3397774c1551c6d113b2b4bbc83f50117abc38c6785d55259cb6fd845 5909
gitg_0.2.4-1.1.debian.tar.gz
35ea757f624c32a04d2e2aef81a147949a810e79c9916a24d6ac9b1c1d08e7fd 293724
gitg_0.2.4-1.1_amd64.deb
Files:
81680e9f0a46642611f8a77ace4d0d90 1336 vcs optional gitg_0.2.4-1.1.dsc
a0802f94b88dd909d62f3825d2a292b2 5909 vcs optional gitg_0.2.4-1.1.debian.tar.gz
3a8e379c4bfe7136303d025d9a7a7d84 293724 vcs optional gitg_0.2.4-1.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEAREDAAYFAk+c8acACgkQl4M9yZjvmkklkACePRbHgNP8OsJ3NsemZEe7x7ds
T1EAoJBaJgefLexDVcdKLwGNXLIHh6cQ
=fYZu
-----END PGP SIGNATURE-----
--- End Message ---
