On Wednesday 24,March,2010 10:13 PM, Michael Martin-Smucker wrote: > I'm not exactly sure why you have two installations of Banshee, but I > know that Karmic called the Banshee package 'banshee' instead of > 'banshee-1' for some reason. Not sure if it's also installed in a > different directory than it would be if you install from a PPA or build > from source, though. If so, that could lead to two installations of > Banshee. Try running: > > banshee --version > > and > > banshee-1 --version The banshee-1 package existed only in the PPA in the 1.0 beta days. 0.9X.Y or something. It has since been completely replaced by the banshee package, and /usr/bin/banshee made a symlink to /usr/bin/banshee-1, as done in Debian. Considering pre-1.0 Banshee is now deprecated, I wonder why we even have this banshee/banshee-1 distinction any more. It seems pointless to me. The Ubuntu packages install files in /usr/bin and /usr/lib/banshee-1. There is absolutely no Ubuntu package that installs things into /usr/local/ since the very scripts which build the packages have safety precautions against that and will bail out, causing the building process of the package to abort if anything was really put into /usr/local. It is most likely that you have had compiled Banshee in the past, and installed things into /usr/local/bin and /usr/local/lib/banshee-1. To remove this, you probably need to ./configure it again and run sudo make uninstall. This should get rid of the /usr/local installation and let you use the /usr/ installation just fine. > 3. If you don't want to mess around with uninstalling things or > manually changing launchers, you could automate your current copy/paste > method by creating a symbolic link between the two Banshee directories. > If the installation in /usr/lib is updating, and the one in > /usr/local/lib isn't, delete the banshee folder in /usr/local/lib: > > sudo rm -rf /usr/local/lib/banshee-1 > > and create a symbolic link in its place, that points at the Banshee > directory that updates: > > sudo ln -s /usr/lib/banshee-1 /usr/local/lib/banshee-1 > > That's it! Just make sure you rm -rf the directory that isn't updating, > and when you ln -s, first list the directory that you're linking to (the > working one), then the directory you're creating (which should match the > one you just deleted). I would rather you do NOT follow this approach. This is a workaround that will likely lead to a very cluttered system. > On Fri, Mar 19, 2010 at 11:35 PM, precipitous <precipitous media cox net > <mailto:precipitous media cox net>> wrote: > > > There are two installations of version 1.5.5 (daily) on my Ubuntu Karmic > machine. One is at /usr/lib/banshee-1, and the other is at > /usr/local/lib/banshee-1. Whenever updates are installed, the copy at > /usr/local/lib automatically gets updated, yet no matter how I run the > application, the copy at /usr/local/lib is the one that starts up. I am > forced to let the updates install each day, then manually copy the > files to > /usr/local/lib/. What would be the best strategy for dealing with > this, so > that I end up with only one working copy that gets updated > automatically, > retains my settings, and runs from a simple command? Am I right in saying that you really meant that the /usr/lib/ copy gets updated, whereas the /usr/local/lib copy is the one which starts up? If this is the case, then the problem is most likely because /usr/local/bin/banshee-1 is favoured over /usr/bin/banshee-1 when looking for binaries within the PATH (this variable is configured with /usr/local/bin before /usr/bin by default on most distributions including Ubuntu), and /usr/local/bin/banshee-1 will look in /usr/local/lib/banshee-1 for files. -- Kind regards, Chow Loong Jin (GPG: 0x8F02A411) Ubuntu Developer
Attachment:
signature.asc
Description: OpenPGP digital signature