Pacman

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.
Tasklist

FS#52522 - [pacman] libalpm hooks should consider package dependency

Attached to Project: Pacman
Opened by Jiachen Yang (farseerfc) - Thursday, 12 January 2017, 23:57 GMT
Last edited by Andrew Gregory (andrewgregory) - Monday, 16 January 2017, 04:22 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
If we have 2 packages A and B triggered the same install hook, and package A depends on package B, we should trigger the hook for B first and then A.
Running hook for A first may have errors if B is not currently installed.

Steps to Reproduce:
Install spl-dkms-git and zfs-dkms-git.
Sometimes dkms hook for zfs is run before dkms hook for spl, and an error happened saying spl hasn't installed.
This task depends upon

Closed by  Andrew Gregory (andrewgregory)
Monday, 16 January 2017, 04:22 GMT
Reason for closing:  Not a bug
Comment by Andrew Gregory (andrewgregory) - Friday, 13 January 2017, 13:37 GMT
Hooks are only run once, not individually for each triggering package; that's the whole point. The targets that triggered the hook get passed to it in alphabetical order. How exactly would you sort targets by dependency taking into consideration that targets can be paths, as opposed to packages, and may be owned by multiple packages?
Comment by Jiachen Yang (farseerfc) - Monday, 16 January 2017, 03:57 GMT
Sorry, it should be a problem for dkms hook. Thanks for the explanation.

Loading...