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#15484 - shaman does not run 'ldconfig' after installing package

Attached to Project: Community Packages
Opened by Wim Herremans (herremaw) - Saturday, 11 July 2009, 19:27 GMT
Last edited by Allan McRae (Allan) - Sunday, 12 July 2009, 01:46 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

shaman does not seem to run 'ldconfig' after installing a package.

Additional info:
* package version(s) shaman 1.0.9-1
* config and/or log files etc.

Steps to reproduce:

1. Install scribus using shaman.

Result: qt3 and scribus are installed and /etc/ld.so.conf gets an entry for /opt/qt/lib.

But scribus does not start and reports: error while loading shared libraries:
libqt-mt.so.3: cannot open shared object file: No such file or directory

After running 'ldconfig', scribus starts alright.

2. pacman --remove --cascade qt3

On my system, this removes qt3 and scribus, and /etc/ld.so.conf becomes empty.

3. run 'ldconfig'

4. pacman --sync --refresh scribus

Result: scribus and qt are installed and /etc/ld.so.conf gets an entry for /opt/qt/lib.

But in this case scribus runs without problem, without having to run 'ldconfig'.

Conclusion: 'pacman' automatically calls 'ldconfig' after installing qt3,
but 'shaman' does not.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 12 July 2009, 01:46 GMT
Reason for closing:  Upstream
Comment by Allan McRae (Allan) - Sunday, 12 July 2009, 01:46 GMT
Please file this with the shaman devs.

Loading...