Christian Schoenebeck wrote:
> Am Donnerstag, 6. März 2008 18:55:55 schrieb schoappied:
>
>> It's dutch. If you need more info or translations I can give it to you...
>>
>
> Oh yeah, English next time please ("export LANG=C"), my internal dutch
> decoder
> works but is a bit slow.
>
> A minor explanation about the libgig .deb package issue in general: our
> Debian
> libgig package (including the one your building yourself) is simply
> called "libgig", whereas the ones coming from Debian-related distributions
> are (mostly) called libgig6 ATM, because the Debian folks have the policy to
> postfix the library's package name with the current .so major version (e.g.
> also "libqt3", "libqt4", ... instead of just "libqt"). And the current major
> version of the libgig DLL is 6 (don't confuse that with the release version
> of libgig). They're doing that package name postfixing, so you could install
> and use different versions of the same library on your machine at the same
> time and thus allowing to install and use applications at the same time,
> which depend on different versions of the the same library. Unfortunately
> libgig's current directory layout doesn't support that, because consequently
> you would have to install them in separate directories as well,
> e.g. /usr/lib/libgig6/ like it's done with Qt. So the best overall solution
> would be to fix the directory layout, but this would introduce new problems.
>
> So looking at your output, it seems you still had the libgig version from
> your
> distribution installed, which creates a conflict with the one you're building
> by yourself, because the Debian packaging system interprets "libgig6"
> and "libgig" as being two separate individual packages, not related to each
> other. Which usually is fine, but the problem however in libgig's current
> case is that both share a couple of same files, so when you try to install /
> upgrade one of the two, dpkg will detect that one would overwrite a file from
> the other package and abort the installation process.
>
> So to fix it on your machine, remove the libgig6 package (which most probably
> will remove other pacakges as well) and it should work fine then:
>
> apt-get remove libgig6
>
> CU
> Christian
>
>
Thanks, but it isn't working:
The following packages have unmet dependencies:
gigtools: Depends: libgig6 but it is not installable
libgig-dev: Depends: libgig6 (= 3.2.1-1) but it is not installable
Resolving dependencies...
The following actions will resolve these dependencies:
Install the following packages:
libgig6 [3.2.1-1 (testing, testing, unstable, unstable, now)]
Score is 41
Accept this solution? [Y/n/q/?]
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
