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
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture All
Severity High
Priority Normal
Reported Version 0.6 Widget
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Installing 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
Comment by Judd Vinet (judd) - Friday, 20 December 2002, 03:06 GMT
Turns out the issue wasn't an improper package order, but the fact that ld.so.cache doesn't get updated until after ALL packages are installed. So when xfree86 and pango (or gtk2) are installed in the same batch, pango will spit out a 'cannot find libXft.so.1' error.

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'
Comment by Judd Vinet (judd) - Friday, 20 December 2002, 03:08 GMT
Note the first part of this bug is still valid, but will be moved to a fresh bug id. Pacman does not sort out dependencies if used with -A or -U. It uses the exact installation order that is given to it on the command line.
Comment by Sean Middleditch (elanthis) - Wednesday, 26 February 2003, 01:37 GMT
  • Task details edited
This bug appears to still be very much here - indeed, it wasn't library existance in the ld cache, the errors regarding gconf were caused by gconftool not being available yet (as it is a binary provided a package that wasn't installed yet).

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.

Loading...