Your message dated Fri, 24 Feb 2006 10:31:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in libsigc++-1.2_1.2.7-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++-1.2
Version: 1.2.5-5
Severity: serious
Tags: patch
From my pbuilder build log:
...
#-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++-1.2-1.2.5.old/debian/rules libsigc++-1.2-1.2.5/debian/rules
--- libsigc++-1.2-1.2.5.old/debian/rules 2006-01-29 12:27:04.000000000 +0000
+++ libsigc++-1.2-1.2.5/debian/rules 2006-01-29 12:28:51.000000000 +0000
@@ -57,7 +57,7 @@
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
# Sometimes shows up if the source directory was configured:
rm -f config.log
@@ -66,7 +66,7 @@
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 && CXXFLAGS="$(CXXFLAGS)" ../configure --prefix=/usr
touch config-stamp
--- End Message ---
--- Begin Message ---
After reopening this bug, I found that there was a new upload today of
libsigc++-1.2 which fixed it. So I'm reclosing it now.
--
Daniel Schepler
--- End Message ---