Your message dated Fri, 24 Feb 2006 09:38:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in libsigc++-2.0, not libsigc++-1.2
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: libsigc++-2.0
Version: 2.0.16-2
Severity: serious
Tags: patch

From my pbuilder build log:

...
if [ -d builddir ]; then rm -rf builddir; fi
#-for x in debian/*.patch; do patch --dry-run -fRp1 < $x > /dev/null&&\
          patch -fRp1 < $x ; done
/bin/sh: -c: line 1: syntax error near unexpected token `done'
/bin/sh: -c: line 1: `  patch -fRp1 < $x ; done'
make: *** [clean] Error 2

I've attached a patch which fixes the build for me.
-- 
Daniel Schepler
diff -urN libsigc++-2.0-2.0.16.old/debian/rules libsigc++-2.0-2.0.16/debian/rules
--- libsigc++-2.0-2.0.16.old/debian/rules	2006-01-26 16:00:49.000000000 +0000
+++ libsigc++-2.0-2.0.16/debian/rules	2006-01-26 16:02:46.000000000 +0000
@@ -56,14 +56,14 @@
 	dh_testroot
 	if [ -d builddir ]; then rm -rf builddir; fi
 	#-for x in debian/*.patch; do patch --dry-run -fRp1 < $$x > /dev/null&&\
-	  patch -fRp1 < $$x ; done
+	#  patch -fRp1 < $$x ; done
 	dh_clean build-stamp config-stamp install-stamp debian/shlibs.local
 
 config: config-stamp
 config-stamp:
 	dh_testdir
 	#for x in debian/*.patch; do patch --dry-run -fp1 < $$x > /dev/null && \
-	  patch -fp1 < $$x; done
+	#  patch -fp1 < $$x; done
 	test -d builddir || mkdir builddir
 	cd builddir && ../configure --prefix=/usr
 	touch config-stamp

--- End Message ---
--- Begin Message ---
reopen 350697
thanks

The upload of libsigc++-2.0_2.0.16-3 closed the wrong bug, so I'm reopening 
the bug against libsigc++-1.2 and closing the bug against libsigc++-2.0.
-- 
Daniel Schepler

--- End Message ---

Reply via email to