libsigc++-2.0: Update configure scripts.

Bug #7639 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
libsigc++-2.0 (Debian)
Fix Released
Unknown
libsigc++-2.0 (Ubuntu)
Invalid
High
Unassigned

Bug Description

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

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

Message-ID: <email address hidden>
Date: Wed, 25 Aug 2004 21:03:59 +0200
From: Kurt Roeckx <email address hidden>
To: <email address hidden>
Subject: libsigc++-2.0: Update configure scripts.

Package: libsigc++-2.0
Version: 2.0.3-4
Severity: important

Hi,

It seems you already tried to fix this before and then reverted
all configure changes.

On amd64 it's currently failing to build because of the old
libtool version being used. Could you please update the
configure script by running the "./autogen.sh" script.

You should make sure you have automake newer than 1.6 as the
default since 1.4 is failing. I suggest you use 1.7 as that's
what it's currently build with.

Kurt

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

Message-ID: <20040825194823.GA32264@torrent>
Date: Wed, 25 Aug 2004 15:48:23 -0400
From: Daniel Burrows <email address hidden>
To: Kurt Roeckx <email address hidden>, <email address hidden>
Subject: Re: Bug#268047: libsigc++-2.0: Update configure scripts.

On Wed, Aug 25, 2004 at 09:03:59PM +0200, Kurt Roeckx <email address hidden> was heard to say:
> It seems you already tried to fix this before and then reverted
> all configure changes.
>
> On amd64 it's currently failing to build because of the old
> libtool version being used. Could you please update the
> configure script by running the "./autogen.sh" script.
>
> You should make sure you have automake newer than 1.6 as the
> default since 1.4 is failing. I suggest you use 1.7 as that's
> what it's currently build with.

  That's exactly what I did before, with the result that libsigc++
stopped installing its libraries. I'll look at it again now that I'm
back in town, though.

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| "...drums...drums in the deep!" |
| J. R. R. Tolkien |
\-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: Thu, 26 Aug 2004 20:08:00 +0200
From: Kurt Roeckx <email address hidden>
To: Daniel Burrows <email address hidden>, <email address hidden>
Subject: Re: Bug#268047: libsigc++-2.0: Update configure scripts.

On Wed, Aug 25, 2004 at 03:48:23PM -0400, Daniel Burrows wrote:
>
> That's exactly what I did before, with the result that libsigc++
> stopped installing its libraries. I'll look at it again now that I'm
> back in town, though.

I first tried to just update the libtool as explained in:
http://people.debian.org/~keybuk/libtool-updating.html

But that gave weird results trying to build the package.
You might want to take a look at that too.

Kurt

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 :

Marking as duplicate based on debbugs merge (251989,268047)

This bug has been marked as a duplicate of bug 7637.

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
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#268047: 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-----

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.

Other bug subscribers

Remote bug watches

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