Glen, I've not used backports (I run mostly sid) and so take this with a grain of salt, but I read it like this: On Mon, Jul 23, 2007 at 11:51:28PM -0700, Glen Pfeiffer wrote: > I have OOo 2.0.4 installed from the stable repository. I want to > install 2.2.1 from backports so I added backports to my sources. > > When I try to install with "aptitude -t etch-backports install > openoffice.org", aptitude proposes an interesting solution. From > what I see, I don't think I should accept it. And subsequent > solutions seem even worse. I have included the first solution > below. My system is 100% updated, so anything it says about Vim, > MySql, etc. is a result of trying to install OOo 2.2.1. my comments on the aptitude output are interspersed below. > > Should I purge OOo first? This is my first attempt to install > from backports, so I am not sure about this. I have searched, but > did not find anything helpful. If you want to see a cleaner output from aptitude, just for fun, then yes, remove OO.o first, but I think it looks clean and I would go ahead. > > > ---- Begin Aptitude Output ---- > The following packages are BROKEN: > openoffice.org-base openoffice.org-calc openoffice.org-common > openoffice.org-core openoffice.org-draw openoffice.org-evolution > openoffice.org-gnome openoffice.org-gtk openoffice.org-impress > openoffice.org-java-common openoffice.org-math openoffice.org-writer > python-uno aptitude likes to make you panic... > > The following packages are unused and will be REMOVED: > libcurl3 libxt-java I find this interesting. I would hold these packages for later investigation as to why they are being removed. > > The following NEW packages will be automatically installed: > libportaudio2 openoffice.org-filter-binfilter > openoffice.org-filter-mobiledev openoffice.org-style-andromeda fine... > > The following packages have been kept back: > kdelibs-data kdelibs4c2a kdemultimedia-kio-plugins ktuberling > libarts1-akode libfinance-quote-perl libkcddb1 libkdegames1 > libmysqlclient15off libpisock9 libpisync0 linux-image-2.6-486 > mysql-client-5.0 mysql-common mysql-server-5.0 openoffice.org-help-en-us > ttf-opensymbol tuxpaint tuxpaint-config tuxpaint-data vim-common vim-full > vim-gui-common vim-runtime vim-tiny kept back means that new versions exist, but you are not installing them. This is a side effect of having backports in your sources.list. There are newer versions of all these packages in backports, but you're not using them... which is probably what you want at this point. [...] > > The following packages have unmet dependencies: > openoffice.org-gnome: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-core: Conflicts: openoffice.org-calc (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-writer (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-impress (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-draw (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-base (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-gtk (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-gnome (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-evolution (< 2.2.1-1~bpo.1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > openoffice.org-writer: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-impress: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-draw: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-java-common: Conflicts: openoffice.org-base (<= 2.2.0-4) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-writer (<= 2.2.0-4) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > openoffice.org-gtk: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-evolution: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-math: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-common: Conflicts: openoffice.org-base (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-writer (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-calc (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-impress (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-draw (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > Conflicts: openoffice.org-math (< 2.2.0-1) but 2.0.4.dfsg.2-7etch1 is installed and it is kept back. > python-uno: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-base: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. > openoffice.org-calc: Depends: openoffice.org-core (= 2.0.4.dfsg.2-7etch1) but 2.2.1-1~bpo.1 is to be installed. this just shows you what all the conflicts are. > > Resolving dependencies... > The following actions will resolve these dependencies: > > Install the following packages: > openoffice.org-style-crystal [2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-style-hicontrast [2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-style-industrial [2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-style-tango [2.2.1-1~bpo.1 (etch-backports)] > > Upgrade the following packages: > openoffice.org-base [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-calc [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-draw [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-evolution [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-gnome [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-gtk [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-impress [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-math [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > openoffice.org-writer [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] > python-uno [2.0.4.dfsg.2-7etch1 (stable, now) -> 2.2.1-1~bpo.1 (etch-backports)] at the end, the solution looks very straightforward. It is only going to upgrade and install openoffice packages (python-uno is a OOo related). This looks like a very clean upgrade to me. A
Attachment:
signature.asc
Description: Digital signature