Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15842 - shaman seems to fail with updated pacman

Attached to Project: Community Packages
Opened by Stuart Citrin (SABCD) - Friday, 07 August 2009, 01:36 GMT
Last edited by Allan McRae (Allan) - Friday, 07 August 2009, 01:43 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Run "shaman":
shaman: error while loading shared libraries: libalpm.so.3: cannot open shared object file: No such file or directory
Run "slocate libalpm"(partial response):
/usr/lib/libalpm.a
/usr/lib/libalpm.so
/usr/lib/libalpm.so.3
/usr/lib/libalpm.so.3.1.1
Run "pacman -S shaman" or "yaourt -S shaman":
resolving dependencies...
warning: cannot resolve "pacman<3.3", a dependency of "shaman"
:: the following package(s) cannot be upgraded due to unresolvable dependencies:
shaman
Run "yaourt -S shaman --aur":
Downloading shaman PKGBUILD from AUR...
Error: shaman not found in AUR.
Run "which shaman":
/usr/bin/shaman

Additional info:
* package version(s)
core/pacman3.3.0-2
shaman 1.0.9-1 per aur
* config and/or log files etc.


Steps to reproduce:
see above
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 07 August 2009, 01:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  Will be fixed when upstream makes a release.
Comment by Allan McRae (Allan) - Friday, 07 August 2009, 01:43 GMT
Yes... an updated shaman version has not been released upstream.

And, pacman-3.3 does not contain libalpm.so.3 so your locate results are wrong... And it appears you are either using the KDEmod shaman or updated pacman using -d. Both are not supported.

Loading...