Am Samstag, 8. März 2008 18:12:23 schrieb schoappied:
> The following packages have been kept back:
> gstreamer0.10-plugins-ugly r-base-dev sooperlooper
> The following NEW packages will be installed:
> libgig6{a}
> The following packages will be upgraded:
> gigtools libgig-dev
> 2 packages upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
> Need to get 0B/880kB of archives. After unpacking 360kB will be used.
> Do you want to continue? [Y/n/?]
>
>
> When I do yes, then I'm in trouble....
>
> So isn't it the best thing to hold the packages or something?
I guess that's due to the gigtools and libgig-dev packages having a higher
version number in your distribution's repository than the ones you're
compiling directly. So that's why APT is trying to update your compiled
gigtools and libgig-dev packages with the ones from the your distribution.
As a workaround you could modify the Debian version tag of the libgig debian
packages you build. You can do so by modifying the debian/changelog file in
the libgig sources. At the very top of that file you see (ATM):
libgig (3.2.1-1) unstable; urgency=low
simply change that version to e.g.:
libgig (3.2.1-9999) unstable; urgency=low
and rebuild and install the libgig debian packages, then APT shouldn't bother
your again to upgrade those... at least not until the next libgig release
comes.
CU
Christian
-------------------------------------------------------------------------
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
