On Fri, Oct 14, 2011 at 5:33 PM, Denis A. Altoé Falqueto <denisfalqueto@gmail.com> wrote:
On Fri, Oct 14, 2011 at 10:42 AM, Karol Blazewicz <karol.blazewicz@gmail.com> wrote:
On Fri, Oct 14, 2011 at 2:52 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
I see my text was probably hard to read, but it was not about some packages not being updated for pacman 4.0 yet but a possible bug (or two) in pacman itself.
-- Pierre Schmitz, https://users.archlinux.de/~pierre
Same thing happened when I installed yaourt:
[2011-10-14 14:36] Running 'pacman -S yaourt' [2011-10-14 14:36] warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew [2011-10-14 14:36] warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew [2011-10-14 14:36] upgraded pacman (4.0.0-2 -> 3.5.4-4) [2011-10-14 14:36] installed package-query (0.9-1) [2011-10-14 14:36] installed yaourt (0.10.2-1)
Now when I want to upgrade to pacman 4 it behaves as expected:
resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: package-query: requires pacman<3.6
You'll have to wait until package-query is updated to pacman 4 or just uninstall it. I had that problem too and decided to uninstall yaourt.
-- A: Because it obfuscates the reading. Q: Why is top posting so bad?
------------------------------------------- Denis A. Altoe Falqueto Linux user #524555 -------------------------------------------
My question is why pacman decided to downgrade itself to satisfy package-query's dependency? I think it should fail due to unresolvable dependencies: warning: cannot resolve "pacman<3.6", a dependency of "package-query" :: The following package cannot be upgraded due to unresolvable dependencies: yaourt