[arch-general] Dependency: pyalpm: requires pacman<3.6 (workaround install pyalpm?)
Guys: There is a strange dependency with pyalpm that prevented upgrade to pacman 4 which I solved by -- installing pyalpm?? Installing pyalpm pulled in pacman as a dependency which successfully completed the upgrade, but pacman would not -Syu and upgrade on its own. That doesn't make sense. The -Syu error was: :: The following packages should be upgraded first : pacman :: Do you want to cancel the current operation :: and upgrade these packages now? [Y/n] y resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: pyalpm: requires pacman<3.6 So I tried the following and answered NO to the pacman upgrade. Evidently pyalpm pulled it in as a dep anyway: 15:18 providence:~/dt/icons/coolicons/openOffice> sudo pacman -Sy --needed pyalpm :: Synchronizing package databases... core is up to date extra is up to date community is up to date archlinuxfr is up to date xyne-any is up to date downloading kdemod3.db... phoenix is up to date :: The following packages should be upgraded first : pacman :: Do you want to cancel the current operation :: and upgrade these packages now? [Y/n] n resolving dependencies... looking for inter-conflicts... Targets (3): libarchive-3.0.3-2 pacman-4.0.1-4 pyalpm-0.5.3-1 Total Download Size: 2.20 MB Total Installed Size: 6.20 MB Proceed with installation? [Y/n] :: Retrieving packages from core... libarchive-3.0.3-2-i686 1215.4K 720.0K/s 00:00:02 [#######################################] 100% pacman-4.0.1-4-i686 1005.0K 693.3K/s 00:00:01 [#######################################] 100% :: Retrieving packages from extra... pyalpm-0.5.3-1-i686 36.8K 194.3K/s 00:00:00 [#######################################] 100% (3/3) checking package integrity [#######################################] 100% (3/3) checking for file conflicts [#######################################] 100% (1/3) upgrading libarchive [#######################################] 100% (2/3) upgrading pacman [#######################################] 100% warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew
Run `pacman-key --init` to set up your pacman keyring. (3/3) upgrading pyalpm [#######################################] 100%
Not sure if this is an issues that will catch others trying to upgrade, but it definitely was a screwy way to work-around pacman not upgrading on its own... -- David C. Rankin, J.D.,P.E.
On Tue, Jan 17, 2012 at 10:26 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
David C. Rankin, J.D.,P.E.
This mail didn't make much sense to me untill the very last line ... You can solve it in a number of ways e.g. remove pyalpm, update pacman, update pyalpm if available: https://bbs.archlinux.org/viewtopic.php?pid=1042280#p1042280
Am 17.01.2012 21:32, schrieb Karol Blazewicz:
On Tue, Jan 17, 2012 at 10:26 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
David C. Rankin, J.D.,P.E.
This mail didn't make much sense to me untill the very last line ...
You can solve it in a number of ways e.g. remove pyalpm, update pacman, update pyalpm if available: https://bbs.archlinux.org/viewtopic.php?pid=1042280#p1042280
The best way is to add pyalpm to SyncFirst in pacman.conf and just run -Syu. -- Pierre Schmitz, http://pierre-schmitz.com
On Tue, Jan 17, 2012 at 23:20, Pierre Schmitz <pierre@archlinux.de> wrote:
Am 17.01.2012 21:32, schrieb Karol Blazewicz:
On Tue, Jan 17, 2012 at 10:26 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
David C. Rankin, J.D.,P.E.
This mail didn't make much sense to me untill the very last line ...
You can solve it in a number of ways e.g. remove pyalpm, update pacman, update pyalpm if available: https://bbs.archlinux.org/viewtopic.php?pid=1042280#p1042280
The best way is to add pyalpm to SyncFirst in pacman.conf and just run -Syu.
Wouldn't the best way be for pacman to not only consider updating the packages listed in SyncFirst, but also all packages that prevent it through it's dependencies? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Am 17.01.2012 23:20, schrieb Pierre Schmitz:
Am 17.01.2012 21:32, schrieb Karol Blazewicz:
On Tue, Jan 17, 2012 at 10:26 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
David C. Rankin, J.D.,P.E.
This mail didn't make much sense to me untill the very last line ...
You can solve it in a number of ways e.g. remove pyalpm, update pacman, update pyalpm if available: https://bbs.archlinux.org/viewtopic.php?pid=1042280#p1042280
It's a pacman 3.5 bug, no idea if it is solved in pacman 4.
The best way is to add pyalpm to SyncFirst in pacman.conf and just run -Syu.
If I run into SyncFirst bugs, I always run pacman -S pacman Everything works fine then.
On Wed, Jan 18, 2012 at 15:46, Thomas Bächler <thomas@archlinux.org> wrote:
Am 17.01.2012 23:20, schrieb Pierre Schmitz:
The best way is to add pyalpm to SyncFirst in pacman.conf and just run -Syu.
If I run into SyncFirst bugs, I always run pacman -S pacman Everything works fine then.
Except of course that it didn't work in this case ;) You'd need to tell pacman to install pacman and ignore any dependencies of other packages that would prevent an upgrade of pacman! /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Am 18.01.2012 15:54, schrieb Magnus Therning:
On Wed, Jan 18, 2012 at 15:46, Thomas Bächler <thomas@archlinux.org> wrote:
Am 17.01.2012 23:20, schrieb Pierre Schmitz:
The best way is to add pyalpm to SyncFirst in pacman.conf and just run -Syu.
If I run into SyncFirst bugs, I always run pacman -S pacman Everything works fine then.
Except of course that it didn't work in this case ;) You'd need to tell pacman to install pacman and ignore any dependencies of other packages that would prevent an upgrade of pacman!
In that case pacman -S pacman pyalpm helps.
participants (5)
-
David C. Rankin
-
Karol Blazewicz
-
Magnus Therning
-
Pierre Schmitz
-
Thomas Bächler