Sysprof cannot run, looking for wrong libbfd

Happened again in edgy. This time sysprof 1.0.3-1 is looking for libbfd-2.16.91 but system has libbfd-2.17 (from binutils 2.17-1ubuntu1).

Apparently sysprof's binutils dependency must be tightly versioned (currently it isn't versioned at all)

And again in gutsy:

sysprof: error while loading shared libraries: libbfd-2.17.50.20070426.so: cannot open shared object file: No such file or directory

To quote the description of binutils-dev (from which the libbfd in question comes):

"Note that building Debian packages which depend on the shared libbfd is Not Allowed."

So it looks like sysprof is doing something naughty here.

sysprof needs to be rebuild everytime a new version of binutils gets uploaded.

sysprof is currently in sync with binutils in gutsy.

Aaand it's broken again.

sysprof (1.0.8-3build1) gutsy; urgency=low

  * Rebuild for recent libbfd (from binutils) (LP: #46224).

 -- Michael Bienia <email address hidden> Wed, 29 Aug 2007 17:48:55 +0200

Broken again in Hardy.

The proposed patch fixes this once and for all by linking statically against libbfd.
I have not tested, if this causes other failures once the versions of libbfd are different on the system from the version sysprof has been linked against!
The patch is taken from the Debian bug.

The debdiff also addresses bug 30160.

I've contacted upstream (Soeren Sandmann) about this and he definitely recommends statically linking against libbfd and says additionally:
"""I think bfd using apps in general should do that. On Fedora,
"-lbfd" does that by default, so I'd suggest doing the same on
Ubuntu/Debian.

Since this is not a problem with sysprof trunk, which doesn't depend
on libbfd at all, and not a problem on Fedora, I think it makes more
sense to just let Ubuntu/Debian patch this issue.

I am not really opposed to taking a patch to make it link libbfd
statically on Ubuntu, but I don't have any more stable releases
planned for the 1.0 series, unless it gets broken by a kernel update."""

Please don't upload/sponsor the debdiff:
It's been fixed in Debian now, too. See the sync request at bug 186158.

This is fixed in debian an will be fixed with next sync (see bug #186158)

Synced.