You are not logged in.
I haven't done a system update for a little while - now when I attempt pacman -Syu, I get a failure due to libreoffice conflicts:
[peter@desktop AURBuilds]$ sudo pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed retrieving file 'archVMrepo.db' from repo.ktz.me : Connection timed out after 10000 milliseconds
error: failed to update archVMrepo (download library error)
:: Starting full system upgrade...
:: Replace libreoffice-still-base with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-calc with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-common with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-draw with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-gnome with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-impress with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-kde4 with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-math with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-postgresql-connector with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-writer with extra/libreoffice-still? [Y/n]
resolving dependencies...
warning: dependency cycle detected:
warning: freetype2 will be installed before its harfbuzz dependency
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2 dependency
looking for inter-conflicts...
:: libreoffice-still-sdk and libreoffice-still-sdk-doc are in conflict. Remove libreoffice-still-sdk-doc? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libreoffice-still-sdk and libreoffice-still-sdk-doc are in conflict
[peter@desktop AURBuilds]$ How do I resolve this?
Last edited by PeterBell (2015-02-08 02:18:43)
Offline
Andes just told me that the easier way to deal with this is to remove everything libreoffice from the system and then install the new one ![]()
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Andes just told me that the easier way to deal with this is to remove everything libreoffice from the system and then install the new one
It would take a while longer, but it's bulletproof, yeah ![]()
Offline
It looks like pacman already made the suggestion to replace the needed package - but the default answer was no (don't know why) and it looks like the default was accepted. Just press 'y' at that prompt.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Extra/unoconv is broken now. Had to uninstall it to upgrade LibreOffice, and now it won't install:
# pacman -S unoconv
resolving dependencies...
warning: cannot resolve "libreoffice-common", a dependency of "unoconv"
:: The following package cannot be upgraded due to unresolvable dependencies:
unoconvLast edited by Morn (2015-02-07 13:11:45)
Offline
Offline
Had a similar problem:
:: Starting full system upgrade...
:: Replace libreoffice-still-calc with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-common with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-draw with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-extension-nlpsolver with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-extension-wiki-publisher with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-impress with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-math with extra/libreoffice-still? [Y/n] y
:: Replace libreoffice-still-writer with extra/libreoffice-still? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: libreoffice-extension-ct2n: requires libreoffice-common
:: libreoffice-extension-diagram: requires libreoffice-common
:: libreoffice-extension-hunart: requires libreoffice-common
:: libreoffice-extension-numbertext: requires libreoffice-common
:: libreoffice-extension-oooblogger: requires libreoffice-common
:: libreoffice-extension-typo: requires libreoffice-common
:: libreoffice-extension-watch-window: requires libreoffice-commonRemoving the packages that required libreoffice-common seems to have done the trick.
Offline
It looks like pacman already made the suggestion to replace the needed package - but the default answer was no (don't know why) and it looks like the default was accepted. Just press 'y' at that prompt.
I had already tried that - it made no difference .. it still failed,
Offline
I believe it still failed, but I don't believe that it didn't make a difference. It failed for a different reason like those that have been tacked on to this thread. These are all different errors, and there are at least two distinct solutions depending on which error is being faced.
The error in your initial post was simply due to a replacement of a group in the repos. Some of the other errors are errors in the packaging of a couple dependent packages.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Tried again this morning and some of the package lists have been updated. Now the libreoffice-still-sdk problem has gone away, but there is still a dependency conflict:
[peter@desktop Mint]$ sudo pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace libreoffice-still-base with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-calc with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-common with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-draw with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-gnome with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-impress with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-kde4 with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-math with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-postgresql-connector with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-writer with extra/libreoffice-still? [Y/n]
resolving dependencies...
warning: dependency cycle detected:
warning: freetype2 will be installed before its harfbuzz dependency
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2 dependency
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.2
[peter@desktop Mint]$ I think that it's telling me that harfbuzz and freetype2 are dependent on each other!
Also, it seems to be saying that there is a dependency on the version of pacman. I'm running pacman v4.1.2 which would be <4.2?
Last edited by PeterBell (2015-02-08 00:52:55)
Offline
I believe it still failed, but I don't believe that it didn't make a difference.
Okay, but the output I included in my OP was after I had already tried both options.
Offline
I stand corrected, the new error is neither of the two I was predicting - your new error has nothing at all to do with any of the errors discussed in this thread and nothing to do with libreoffice. You need to remove and/or update package-query, that is an AUR package - there were dozens of threads on that exact error several weeks ago.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Having removed wine and its dependencies etc, I now get into this state:
[peter@desktop Mint]$ sudo pacman -R lib32-freetype2
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-harfbuzz: requires lib32-freetype2
[peter@desktop Mint]$ sudo pacman -R lib32-harfbuzz
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-freetype2: requires lib32-harfbuzz
[peter@desktop Mint]$ HELP!
Offline
What are you doing? Wine was never a problem. I told you want needed to be done. If you ignore provided advice and instead do other random things (without actually specifying what you are doing) then no one can help you.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
What are you doing? Wine was never a problem.
I'm sorry - I was trying to help myself by following the errors, as reported. It seemed that my problem stemmed from lib32-harfbuzz and lib32-freetype2, so I was attempting to remove those. However, wine was dependent on them so had to be removed first.
I told you want needed to be done. If you ignore provided advice and instead do other random things (without actually specifying what you are doing) then no one can help you.
Indeed, your posting did point me in the right direction, but did not appear until after I had posted about my experiment with wine. Wine is no great loss, anyway - I've never managed to achieve anything useful with it!
As you indicated, my problems were resolved by updating package-query:
yaourt package-queryEdit: In my searching, I did come across advice to use pacaur instead of yaourt - I'm not sure whether this would have made any difference in my case.
My analysis, wrongly or rightly, is this:
1) AUR packages (some?) appear to list pacman version as a dependency. "pacman -Syu" was attempting to update itself to 4.2 which broke the dependency (<4.2), even though 4.1.x was running at the time - there's a recipe for confusion! This was resolved by rebuilding package-query before updating the rest of the system, because the latest version has updated the pacman dependency.
2) lib32-harfbuzz and lib32-freetype2 (both AUR packages?) were in conflict - they cannot (must not) be dependent on each other. This was resolved by pulling later versions during the rebuild of package-query.
3) The libreoffice problem was not an issue. My mistake was that I ignored a lifetime of experience working in IT - I concentrated on the last-reported error rather than the first! All I can say in my defence is that eight years of retirement must have addled my brain!
In short, two, unrelated, errors, conflated with another, relatively insignificant, error message, led me on a wild goose chase.
I thank you for your wise counsel!
Last edited by PeterBell (2015-02-08 02:21:24)
Offline
For what it's worth, something a little odd does seem to be going on. In a similar position to Peter Bell, I just tried a pacman -Syu ... got the same offers to replace the libreoffice components with the "extra/libreoffice-still" ones.
Now, just at the moment I am in the position of not wanting to rock the libreoffice boat at all, so I *explicitly declined* pacman's offer to make those replacements.
But the update was still aborted, *apparently* because "libreoffice-still and libreoffice-still-common are in conflict" -- despite my explicitly declining the installation of libreoffice-still. Am I missing something?
:: Synchronising package databases...
core 120.4 KiB 164K/s 00:01 [######################] 100%
extra 1795.1 KiB 428K/s 00:04 [######################] 100%
community 2.5 MiB 523K/s 00:05 [######################] 100%
:: Starting full system upgrade...
:: Replace libreoffice-still-base with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-calc with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-common with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-draw with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-gnome with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-impress with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-kde4 with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-math with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-postgresql-connector with extra/libreoffice-still? [Y/n] n
:: Replace libreoffice-still-writer with extra/libreoffice-still? [Y/n] n
resolving dependencies...
looking for conflicting packages...
:: libreoffice-still-sdk and libreoffice-still-sdk-doc are in conflict. Remove libreoffice-still-sdk-doc? [y/N] y
:: libreoffice-still and libreoffice-still-common are in conflict. Remove libreoffice-still-common? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libreoffice-still and libreoffice-still-common are in conflictOffline
Andes tells me there's going to be a package on your system which depends on libreoffice-still-common which isn't being pulled to be removed. And as I said earlier, the easy way to deal with it is to remove all the libreoffice packages and then install the new one.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Now, just at the moment I am in the position of not wanting to rock the libreoffice boat at all, so I *explicitly declined* pacman's offer to make those replacements.
Then don't update at all. Doing a partial update like you're trying to do will leave you with a non-functional libreoffice anyway, so pacman's actually saved you some headaches by refusing to update.
Offline