libsigc++-2.0: FTBFS amd64: configure scripts too old

Bug #7637 reported by Debian Bug Importer
16
Affects Status Importance Assigned to Milestone
libsigc++-2.0 (Debian)
Fix Released
Unknown
libsigc++-2.0 (Ubuntu)
Invalid
Medium
Tollef Fog Heen

Bug Description

Automatically imported from Debian bug report #251989 http://bugs.debian.org/251989

Revision history for this message
In , Goswin von Brederlow (brederlo) wrote : FTBFS i386: configure script to old and --host missing for configure
Download full text (12.6 KiB)

dpkg-buildpackage: source package is libsigc++-2.0
dpkg-buildpackage: source version is 2.0.3-1
dpkg-buildpackage: source maintainer is Daniel Burrows <email address hidden>
dpkg-buildpackage: host architecture is i386
 fakeroot debian/rules clean
dh_testdir
dh_testroot
if [ -f debian/soname-specific-files ]; then rm -f `cat debian/soname-specific-files`; rm debian/soname-specific-files; fi
dh_testdir
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
dh_clean build-stamp config-stamp install-stamp debian/shlibs.local
 debian/rules build
dh_testdir
#for x in debian/*.patch; do patch --dry-run -fp1 < $x > /dev/null && \
  patch -fp1 < $x; done
test -d builddir || mkdir builddir
cd builddir && ../configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gm4... no
checking for m4... m4
checking for perl... /usr/bin/perl
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for some Win32 platform... no
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90......

Revision history for this message
In , Daniel Burrows (dburrows) wrote : Re: Bug#251989: FTBFS i386: configure script to old and --host missing for configure

  libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
just tested it on my own system and pbuilder) Maybe something is wrong
with your build environment.

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| Almost Winter, Winter, Still Winter, and Construction. |
\---- Be like the kid in the movie! Play chess! -- http://www.uschess.org ---/

Revision history for this message
In , Goswin von Brederlow (brederlo) wrote :

Daniel Burrows <email address hidden> writes:

> libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
> just tested it on my own system and pbuilder) Maybe something is wrong
> with your build environment.
>
> Daniel

Do you have an amd64 (x86_64) cpu running a 64bit kernel?

MfG
        Goswin

Revision history for this message
In , Daniel Burrows (dburrows) wrote :

On Mon, Aug 16, 2004 at 07:35:01PM +0200, Goswin von Brederlow <email address hidden> was heard to say:
> Daniel Burrows <email address hidden> writes:
>
> > libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
> > just tested it on my own system and pbuilder) Maybe something is wrong
> > with your build environment.
> >
> > Daniel
>
> Do you have an amd64 (x86_64) cpu running a 64bit kernel?

 No, nor does Debian.

 Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| "A game which, from the viewpoint of the other players (ie, everyone) might |
| be compared to playing poker with blank cards, for infinite stakes, with a |
| Dealer who won't tell you the rules and who /smiles all the time/." |
| -- Terry Pratchett, _Good Omens_ |
\------------- Got APT? -- Debian GNU/Linux http://www.debian.org ------------/

Revision history for this message
In , Daniel Burrows (dburrows) wrote :

  I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
there isn't a problem with uploading a new version. However, I'd rather
not stress the autobuilders unnecessarily. I think that upstream is
slowly working towards another release, and I was planning to just roll
this into that release; does that work for you? (note that 2.0.4 might
not make sarge in that case, depending on how long they take)

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| Human beings were created by water to transport it uphill. |
\-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/

Revision history for this message
In , Goswin von Brederlow (brederlo) wrote :

Daniel Burrows <email address hidden> writes:

> I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
> there isn't a problem with uploading a new version. However, I'd rather
> not stress the autobuilders unnecessarily. I think that upstream is
> slowly working towards another release, and I was planning to just roll
> this into that release; does that work for you? (note that 2.0.4 might
> not make sarge in that case, depending on how long they take)
>
> Daniel

Not realy.

The amd64 and intel em64t cpus will be very common in the near future
and if all goes well sarge will have a 64bit kernel image for
them (so people don't have to compile their own).

The package has a FTBFS bug on those cpus because you fail to pass
"--host" and the configure script is too old to work without.
libsig2.0 needs to be fixed for sarge or removed. Since you just need
to update the generated files and add a "--host=..." in rules to be
policy compliant I don't see a reason to make an exception.

MfG
        Goswin

Revision history for this message
In , Daniel Burrows (dburrows) wrote :

severity 251989 serious
severity 254174 serious
merge 251989 254174
thanks

  If that's the case, this should be "serious".

   Off to load up the autobuilders with a change that's pointless for
   99.99% of the user base,
  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| He had a terrible memory. He remembered everything. |
\------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/

Revision history for this message
In , Daniel Burrows (dburrows) wrote : Bug#251989: fixed in libsigc++-2.0 2.0.3-2

Source: libsigc++-2.0
Source-Version: 2.0.3-2

We believe that the bug you reported is fixed in the latest version of
libsigc++-2.0, which is due to be installed in the Debian FTP archive:

libsigc++-2.0-0_2.0.3-2_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-0_2.0.3-2_i386.deb
libsigc++-2.0-dev_2.0.3-2_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-dev_2.0.3-2_i386.deb
libsigc++-2.0-doc_2.0.3-2_all.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-doc_2.0.3-2_all.deb
libsigc++-2.0_2.0.3-2.diff.gz
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-2.diff.gz
libsigc++-2.0_2.0.3-2.dsc
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-2.dsc

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 <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Burrows <email address hidden> (supplier of updated libsigc++-2.0 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 <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 17 Aug 2004 10:39:46 -0400
Source: libsigc++-2.0
Binary: libsigc++-2.0-0 libsigc++-2.0-doc libsigc++-2.0-dev
Architecture: source all i386
Version: 2.0.3-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Burrows <email address hidden>
Changed-By: Daniel Burrows <email address hidden>
Description:
 libsigc++-2.0-0 - Type-safe Signal Framework for C++ - runtime
 libsigc++-2.0-dev - Type-safe Signal Framework for C++ - development files
 libsigc++-2.0-doc - Type-safe Signal Framework for C++ - reference documentation
Closes: 244229 251989 254174
Changes:
 libsigc++-2.0 (2.0.3-2) unstable; urgency=low
 .
   * The "Die autobuilders die die die!" release.
 .
   * Regenerate the configure script (Closes: #251989, #254174).
 .
   * Don't compress the doxygen tags file (Closes: #244229).
Files:
 4fe6528297c21f13cc2f92dd6c37533b 653 devel optional libsigc++-2.0_2.0.3-2.dsc
 760fffd1c6f6c4a978a0735a0a7a379d 73258 devel optional libsigc++-2.0_2.0.3-2.diff.gz
 c4642d90fb6d7cee21fb6d6b4bf5852a 15532 libs optional libsigc++-2.0-0_2.0.3-2_i386.deb
 e25b942bff9a89c8bcfea0a5fa78471c 119464 libdevel optional libsigc++-2.0-dev_2.0.3-2_i386.deb
 1bf5daa9db5e34e00664b8a09b309869 1346938 doc optional libsigc++-2.0-doc_2.0.3-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBIiJ/ch6xsM7kSXgRAs1QAKCdibsLR873mdFidoSEM+ZWBvm2LgCghdbI
lttO6YTgKJvG1Y4iFmSsoXY=
=mcHu
-----END PGP SIGNATURE-----

Revision history for this message
In , Daniel Burrows (dburrows) wrote : oops

reopen 251989
severity 268047 serious
merge 268047 251989
thanks

  Shoulda done this earlier.

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| If we do not change our direction |
| we are likely to end up where we are headed. |
\---- Be like the kid in the movie! Play chess! -- http://www.uschess.org ---/

Revision history for this message
In , Daniel Burrows (dburrows) wrote : Bug#251989: fixed in libsigc++-2.0 2.0.3-5

Source: libsigc++-2.0
Source-Version: 2.0.3-5

We believe that the bug you reported is fixed in the latest version of
libsigc++-2.0, which is due to be installed in the Debian FTP archive:

libsigc++-2.0-0_2.0.3-5_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-0_2.0.3-5_i386.deb
libsigc++-2.0-dev_2.0.3-5_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-dev_2.0.3-5_i386.deb
libsigc++-2.0-doc_2.0.3-5_all.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-doc_2.0.3-5_all.deb
libsigc++-2.0_2.0.3-5.diff.gz
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-5.diff.gz
libsigc++-2.0_2.0.3-5.dsc
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-5.dsc

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 <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Burrows <email address hidden> (supplier of updated libsigc++-2.0 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 <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 27 Aug 2004 12:59:56 -0400
Source: libsigc++-2.0
Binary: libsigc++-2.0-0 libsigc++-2.0-doc libsigc++-2.0-dev
Architecture: source all i386
Version: 2.0.3-5
Distribution: unstable
Urgency: high
Maintainer: Daniel Burrows <email address hidden>
Changed-By: Daniel Burrows <email address hidden>
Description:
 libsigc++-2.0-0 - Type-safe Signal Framework for C++ - runtime
 libsigc++-2.0-dev - Type-safe Signal Framework for C++ - development files
 libsigc++-2.0-doc - Type-safe Signal Framework for C++ - reference documentation
Closes: 251989 254174 268047
Changes:
 libsigc++-2.0 (2.0.3-5) unstable; urgency=high
 .
   * The "actually tested this time" upload.
 .
   * Try to rebuild the autotools/libtool stuff...again. The shared object
     file is actually shipped this time; I may have used the wrong automake
     version for -3. (Closes: #251989, #254174, #268047)
Files:
 cc19f9c27ab5e7296938caf7b577e54b 653 devel optional libsigc++-2.0_2.0.3-5.dsc
 b5b8bc8d551cff1c23b1e5774515f41d 79770 devel optional libsigc++-2.0_2.0.3-5.diff.gz
 67df018c28f550b79dc7030d627274ba 24470 libs optional libsigc++-2.0-0_2.0.3-5_i386.deb
 c7f514a5f45740aabdd3d1a12537c748 120550 libdevel optional libsigc++-2.0-dev_2.0.3-5_i386.deb
 4bf1eee2dea2e6da7be231c50ef92a76 1343990 doc optional libsigc++-2.0-doc_2.0.3-5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBL2uOch6xsM7kSXgRAm0GAKCAJEdSNNbY59azAjN3Wen8jXJycwCfeuEu
JrcU2/HGRQv9anDbBjZn8tg=
=8eo/
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #251989 http://bugs.debian.org/251989

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1BUx9e-0008P7-Mv@dual>
Date: Tue, 01 Jun 2004 00:29:17 +0000
From: Goswin von Brederlow <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: libsigc++-2.0: FTBFS amd64: configure scripts too old

Package: libsigc++-2.0
Version: 2.0.3
Severity: important
Justification: fails to build from source

Hi,

the configure script in libsigc++-2.0 does not know about amd64 (x86_64).
I tried to regenerate the script but that seems to screw things up
even for previously working archs.

Please update the configure script in your next upload.

MfG
 Goswin

-- System Information:
Debian Release: testing/unstable
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.5-amd64
Locale: LANG=C, LC_CTYPE=C

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (12.8 KiB)

Message-Id: <E1Bwem5-0005o2-39@dual>
Date: Mon, 16 Aug 2004 12:31:33 +0200
From: Goswin von Brederlow <email address hidden>
To: <email address hidden>
Subject: FTBFS i386: configure script to old and --host missing for configure

dpkg-buildpackage: source package is libsigc++-2.0
dpkg-buildpackage: source version is 2.0.3-1
dpkg-buildpackage: source maintainer is Daniel Burrows <email address hidden>
dpkg-buildpackage: host architecture is i386
 fakeroot debian/rules clean
dh_testdir
dh_testroot
if [ -f debian/soname-specific-files ]; then rm -f `cat debian/soname-specific-files`; rm debian/soname-specific-files; fi
dh_testdir
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
dh_clean build-stamp config-stamp install-stamp debian/shlibs.local
 debian/rules build
dh_testdir
#for x in debian/*.patch; do patch --dry-run -fp1 < $x > /dev/null && \
  patch -fp1 < $x; done
test -d builddir || mkdir builddir
cd builddir && ../configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gm4... no
checking for m4... m4
checking for perl... /usr/bin/perl
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for some Win32 platform... no
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040816153158.GA4246@torrent>
Date: Mon, 16 Aug 2004 11:31:58 -0400
From: Daniel Burrows <email address hidden>
To: Goswin von Brederlow <email address hidden>,
 <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host missing for configure

  libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
just tested it on my own system and pbuilder) Maybe something is wrong
with your build environment.

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| Almost Winter, Winter, Still Winter, and Construction. |
\---- Be like the kid in the movie! Play chess! -- http://www.uschess.org ---/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 16 Aug 2004 19:35:01 +0200
From: Goswin von Brederlow <email address hidden>
To: Daniel Burrows <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host
 missing for configure

Daniel Burrows <email address hidden> writes:

> libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
> just tested it on my own system and pbuilder) Maybe something is wrong
> with your build environment.
>
> Daniel

Do you have an amd64 (x86_64) cpu running a 64bit kernel?

MfG
        Goswin

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040816181404.GA4540@torrent>
Date: Mon, 16 Aug 2004 14:14:04 -0400
From: Daniel Burrows <email address hidden>
To: Goswin von Brederlow <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host missing for configure

On Mon, Aug 16, 2004 at 07:35:01PM +0200, Goswin von Brederlow <email address hidden> was heard to say:
> Daniel Burrows <email address hidden> writes:
>
> > libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
> > just tested it on my own system and pbuilder) Maybe something is wrong
> > with your build environment.
> >
> > Daniel
>
> Do you have an amd64 (x86_64) cpu running a 64bit kernel?

 No, nor does Debian.

 Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| "A game which, from the viewpoint of the other players (ie, everyone) might |
| be compared to playing poker with blank cards, for infinite stakes, with a |
| Dealer who won't tell you the rules and who /smiles all the time/." |
| -- Terry Pratchett, _Good Omens_ |
\------------- Got APT? -- Debian GNU/Linux http://www.debian.org ------------/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040816181708.GA4573@torrent>
Date: Mon, 16 Aug 2004 14:17:08 -0400
From: Daniel Burrows <email address hidden>
To: Goswin von Brederlow <email address hidden>,
 <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host missing for configure

  I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
there isn't a problem with uploading a new version. However, I'd rather
not stress the autobuilders unnecessarily. I think that upstream is
slowly working towards another release, and I was planning to just roll
this into that release; does that work for you? (note that 2.0.4 might
not make sarge in that case, depending on how long they take)

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| Human beings were created by water to transport it uphill. |
\-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 17 Aug 2004 06:19:05 +0200
From: Goswin von Brederlow <email address hidden>
To: Daniel Burrows <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host
 missing for configure

Daniel Burrows <email address hidden> writes:

> I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
> there isn't a problem with uploading a new version. However, I'd rather
> not stress the autobuilders unnecessarily. I think that upstream is
> slowly working towards another release, and I was planning to just roll
> this into that release; does that work for you? (note that 2.0.4 might
> not make sarge in that case, depending on how long they take)
>
> Daniel

Not realy.

The amd64 and intel em64t cpus will be very common in the near future
and if all goes well sarge will have a 64bit kernel image for
them (so people don't have to compile their own).

The package has a FTBFS bug on those cpus because you fail to pass
"--host" and the configure script is too old to work without.
libsig2.0 needs to be fixed for sarge or removed. Since you just need
to update the generated files and add a "--host=..." in rules to be
policy compliant I don't see a reason to make an exception.

MfG
        Goswin

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040817144103.GA4225@torrent>
Date: Tue, 17 Aug 2004 10:41:03 -0400
From: Daniel Burrows <email address hidden>
To: Goswin von Brederlow <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: Bug#251989: FTBFS i386: configure script to old and --host missing for configure

severity 251989 serious
severity 254174 serious
merge 251989 254174
thanks

  If that's the case, this should be "serious".

   Off to load up the autobuilders with a change that's pointless for
   99.99% of the user base,
  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| He had a terrible memory. He remembered everything. |
\------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 17 Aug 2004 11:47:09 -0400
From: Daniel Burrows <email address hidden>
To: <email address hidden>
Subject: Bug#251989: fixed in libsigc++-2.0 2.0.3-2

Source: libsigc++-2.0
Source-Version: 2.0.3-2

We believe that the bug you reported is fixed in the latest version of
libsigc++-2.0, which is due to be installed in the Debian FTP archive:

libsigc++-2.0-0_2.0.3-2_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-0_2.0.3-2_i386.deb
libsigc++-2.0-dev_2.0.3-2_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-dev_2.0.3-2_i386.deb
libsigc++-2.0-doc_2.0.3-2_all.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-doc_2.0.3-2_all.deb
libsigc++-2.0_2.0.3-2.diff.gz
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-2.diff.gz
libsigc++-2.0_2.0.3-2.dsc
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-2.dsc

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 <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Burrows <email address hidden> (supplier of updated libsigc++-2.0 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 <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 17 Aug 2004 10:39:46 -0400
Source: libsigc++-2.0
Binary: libsigc++-2.0-0 libsigc++-2.0-doc libsigc++-2.0-dev
Architecture: source all i386
Version: 2.0.3-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Burrows <email address hidden>
Changed-By: Daniel Burrows <email address hidden>
Description:
 libsigc++-2.0-0 - Type-safe Signal Framework for C++ - runtime
 libsigc++-2.0-dev - Type-safe Signal Framework for C++ - development files
 libsigc++-2.0-doc - Type-safe Signal Framework for C++ - reference documentation
Closes: 244229 251989 254174
Changes:
 libsigc++-2.0 (2.0.3-2) unstable; urgency=low
 .
   * The "Die autobuilders die die die!" release.
 .
   * Regenerate the configure script (Closes: #251989, #254174).
 .
   * Don't compress the doxygen tags file (Closes: #244229).
Files:
 4fe6528297c21f13cc2f92dd6c37533b 653 devel optional libsigc++-2.0_2.0.3-2.dsc
 760fffd1c6f6c4a978a0735a0a7a379d 73258 devel optional libsigc++-2.0_2.0.3-2.diff.gz
 c4642d90fb6d7cee21fb6d6b4bf5852a 15532 libs optional libsigc++-2.0-0_2.0.3-2_i386.deb
 e25b942bff9a89c8bcfea0a5fa78471c 119464 libdevel optional libsigc++-2.0-dev_2.0.3-2_i386.deb
 1bf5daa9db5e34e00664b8a09b309869 1346938 doc optional libsigc++-2.0-doc_2.0.3-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBIiJ/ch6xsM7kSXgRAs1QAKCdibsLR873mdFidoSEM+ZWBvm2LgCghdbI
lttO6YTgKJvG1Y4iFmSsoXY=
=mcHu
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040827160729.GA6357@torrent>
Date: Fri, 27 Aug 2004 12:07:29 -0400
From: Daniel Burrows <email address hidden>
To: <email address hidden>
Subject: oops

reopen 251989
severity 268047 serious
merge 268047 251989
thanks

  Shoulda done this earlier.

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| If we do not change our direction |
| we are likely to end up where we are headed. |
\---- Be like the kid in the movie! Play chess! -- http://www.uschess.org ---/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

*** Bug 7638 has been marked as a duplicate of this bug. ***

Revision history for this message
Debian Bug Importer (debzilla) wrote :

*** Bug 7639 has been marked as a duplicate of this bug. ***

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 27 Aug 2004 13:32:05 -0400
From: Daniel Burrows <email address hidden>
To: <email address hidden>
Subject: Bug#251989: fixed in libsigc++-2.0 2.0.3-5

Source: libsigc++-2.0
Source-Version: 2.0.3-5

We believe that the bug you reported is fixed in the latest version of
libsigc++-2.0, which is due to be installed in the Debian FTP archive:

libsigc++-2.0-0_2.0.3-5_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-0_2.0.3-5_i386.deb
libsigc++-2.0-dev_2.0.3-5_i386.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-dev_2.0.3-5_i386.deb
libsigc++-2.0-doc_2.0.3-5_all.deb
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0-doc_2.0.3-5_all.deb
libsigc++-2.0_2.0.3-5.diff.gz
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-5.diff.gz
libsigc++-2.0_2.0.3-5.dsc
  to pool/main/libs/libsigc++-2.0/libsigc++-2.0_2.0.3-5.dsc

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 <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Burrows <email address hidden> (supplier of updated libsigc++-2.0 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 <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 27 Aug 2004 12:59:56 -0400
Source: libsigc++-2.0
Binary: libsigc++-2.0-0 libsigc++-2.0-doc libsigc++-2.0-dev
Architecture: source all i386
Version: 2.0.3-5
Distribution: unstable
Urgency: high
Maintainer: Daniel Burrows <email address hidden>
Changed-By: Daniel Burrows <email address hidden>
Description:
 libsigc++-2.0-0 - Type-safe Signal Framework for C++ - runtime
 libsigc++-2.0-dev - Type-safe Signal Framework for C++ - development files
 libsigc++-2.0-doc - Type-safe Signal Framework for C++ - reference documentation
Closes: 251989 254174 268047
Changes:
 libsigc++-2.0 (2.0.3-5) unstable; urgency=high
 .
   * The "actually tested this time" upload.
 .
   * Try to rebuild the autotools/libtool stuff...again. The shared object
     file is actually shipped this time; I may have used the wrong automake
     version for -3. (Closes: #251989, #254174, #268047)
Files:
 cc19f9c27ab5e7296938caf7b577e54b 653 devel optional libsigc++-2.0_2.0.3-5.dsc
 b5b8bc8d551cff1c23b1e5774515f41d 79770 devel optional libsigc++-2.0_2.0.3-5.diff.gz
 67df018c28f550b79dc7030d627274ba 24470 libs optional libsigc++-2.0-0_2.0.3-5_i386.deb
 c7f514a5f45740aabdd3d1a12537c748 120550 libdevel optional libsigc++-2.0-dev_2.0.3-5_i386.deb
 4bf1eee2dea2e6da7be231c50ef92a76 1343990 doc optional libsigc++-2.0-doc_2.0.3-5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBL2uOch6xsM7kSXgRAm0GAKCAJEdSNNbY59azAjN3Wen8jXJycwCfeuEu
JrcU2/HGRQv9anDbBjZn8tg=
=8eo/
-----END PGP SIGNATURE-----

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

libsigc++-2.0 is in universe, not a release goal.

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

libsigc++-2.0 is not in main, just in universe, so this is not a warty bug;
closing.

Changed in libsigc++-2.0:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.