Dear maintainer, I've prepared an NMU for gloox (versioned as 0.9.9.5-1.3) and uploaded it to DELAYED/2, according to DevRef §5.11.1. The NMU is including the patch already attached to this bugreport. Please feel free to tell me if I should delay it longer.
Regards. diff -u gloox-0.9.9.5/debian/changelog gloox-0.9.9.5/debian/changelog --- gloox-0.9.9.5/debian/changelog +++ gloox-0.9.9.5/debian/changelog @@ -1,3 +1,11 @@ +gloox (0.9.9.5-1.3) unstable; urgency=low + + * Non-maintainer upload. + * debian/patches/fix-gcc4.4.dpatch added, fixes FTBFS with GCC 4.4, + thanks to Martin Michlmayr (Closes: #505333) + + -- David Paleino <[email protected]> Mon, 21 Dec 2009 13:18:50 +0100 + gloox (0.9.9.5-1.2) unstable; urgency=low * Fix incorrect changelog entry (e-mail address) diff -u gloox-0.9.9.5/debian/patches/00list gloox-0.9.9.5/debian/patches/00list --- gloox-0.9.9.5/debian/patches/00list +++ gloox-0.9.9.5/debian/patches/00list @@ -5 +5,2 @@ -autoreconf.dpatch \ No newline at end of file +autoreconf.dpatch +fix-gcc4.4.dpatch only in patch2: unchanged: --- gloox-0.9.9.5.orig/debian/patches/fix-gcc4.4.dpatch +++ gloox-0.9.9.5/debian/patches/fix-gcc4.4.dpatch @@ -0,0 +1,30 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## fix-gcc4.4.dpatch by Martin Michlmayr <[email protected]> +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Fix FTBFS with GCC 4.4 + +...@dpatch@ +diff -urNad gloox-0.9.9.5~/src/md5.cpp gloox-0.9.9.5/src/md5.cpp +--- gloox-0.9.9.5~/src/md5.cpp 2008-04-26 13:47:24.000000000 +0200 ++++ gloox-0.9.9.5/src/md5.cpp 2009-12-21 13:17:48.000000000 +0100 +@@ -71,6 +71,7 @@ + + #include "md5.h" + ++#include <cstdio> + #include <string.h> + + namespace gloox +diff -urNad gloox-0.9.9.5~/src/sha.cpp gloox-0.9.9.5/src/sha.cpp +--- gloox-0.9.9.5~/src/sha.cpp 2008-04-26 13:47:24.000000000 +0200 ++++ gloox-0.9.9.5/src/sha.cpp 2009-12-21 13:17:58.000000000 +0100 +@@ -12,6 +12,8 @@ + + #include "sha.h" + ++#include <cstdio> ++ + namespace gloox + { + -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
