Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#10 - package installation order
Attached to Project:
Pacman
Opened by Sean Middleditch (elanthis) - Friday, 04 October 2002, 23:39 GMT
Last edited by Sean Middleditch (elanthis) - Wednesday, 26 February 2003, 01:37 GMT
Opened by Sean Middleditch (elanthis) - Friday, 04 October 2002, 23:39 GMT
Last edited by Sean Middleditch (elanthis) - Wednesday, 26 February 2003, 01:37 GMT
|
DetailsInstalling packages with -A/-U, or doing a system upgrade, does not take dependencies into account. This causes install scripts to sometimes fail, as they require binaries or libraries from packages not being installed until later down the line.
Alternatively, pre/post scripts could be made to run before any package is modified/installed and after all packages are modified/installed, respectively. GNOME is not cleanly installable because of this issue. (gconf requires orbit2 and xfree86, and some libgnome needs a working gconf on install; most other gnome packages will end up needing it working on install as well). |
This task depends upon
Closed by Anonymous Submitter
Reason for closing: Not a bug
Reason for closing: Not a bug
I've fixed this in the current tree by making the install scriptlets call ldconfig before creating the .modules file.
A quick fix for users with the 0.4 iso is to simply reinstall pango and gtk: 'pacman -Sy pango gtk2'
As another test case, as I'm testing the GNOME2.2 packages, when I install gtk2 and pango, the gtk2 install script fails, as it can't load the pango libraries - and the gtk2 init script explicitly calls ldconfig.