banshee should depend on libtaglib2.0-cil

[Tim Fuchs]

Binary package hint: banshee

bansheee will crash with the following error:

** (Banshee:10252): WARNING **: The following assembly referenced from /usr/lib/banshee/Banshee.Base.dll could not be loaded:
     Assembly: taglib-sharp (assemblyref_index=15)
     Version: 2.0.2.0
     Public Key: db62eba44689b5b0
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/banshee).

** (Banshee:10252): WARNING **: Could not load file or assembly 'taglib-sharp, Version=2.0.2.0, Culture=neutral, PublicKeyToken=db62eba44689b5b0' or one of its dependencies.
Stacktrace:

When I install taglib-sharp manually, everything works fine, so it's just a missing dependency of the package.

[Tim Fuchs (tim-fuchs)]

This is on hardy, I didn't know where to add that information.

[Andrew Starr-Bochicchio (andrewsomething)]

I can confirm this on Hardy. Here is the error output:

** (Banshee:9541): WARNING **: Could not load file or assembly 'taglib-sharp, Version=2.0.2.0, Culture=neutral, PublicKeyToken=db62eba44689b5b0' or one of its dependencies.

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'taglib-sharp, Version=2.0.2.0, Culture=neutral, PublicKeyToken=db62eba44689b5b0' or one of its dependencies.
File name: 'taglib-sharp, Version=2.0.2.0, Culture=neutral, PublicKeyToken=db62eba44689b5b0'
  at Banshee.Base.ImportManager.ProcessQueue () [0x00000]
  at Banshee.Base.ImportManager+<>c__CompilerGenerated64.<QueueSource>c__197 () [0x00000]
  at (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
Importing timer stopped: 00:00:00.0096150

Right now Banshee build-depends on libtaglib2.0-cil (>= 2.0.0) according to its debian/control file. I don't know if this just needs to be bumped up on the build deps and rebuilt or if the package needs to depend on libtaglib2.0-cil

[Andrew Starr-Bochicchio (andrewsomething)]

Actually, I see that this bug is already reported so I'm marking it a duplicate of Bug #186420 Further conversation should take place there.