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#38874 - --force option in makepkg -si is not passed to underlaying pacman -U command
Attached to Project:
Pacman
Opened by boris pezzatti (pezzacolori) - Tuesday, 11 February 2014, 16:08 GMT
Last edited by Allan McRae (Allan) - Tuesday, 11 February 2014, 21:13 GMT
Opened by boris pezzatti (pezzacolori) - Tuesday, 11 February 2014, 16:08 GMT
Last edited by Allan McRae (Allan) - Tuesday, 11 February 2014, 21:13 GMT
|
DetailsSummary and Info:
The --force option in pacman can refer to both the -S or the -U command. However using makepkg -si --force, this option is only passed to the build process, but not to the underlaying pacman -U command. Since some aur-package installers (like pacaur) rely on makepkg -si , it is impossible to use them with the --force option for the installation step. Steps to Reproduce: For a package installation that fails due to conflicting files, using pacman -U --force pkgxxx can solve the problem (I'm aware that it is not a good habit, but should be used only with caution). For aur packages, using makepkg -si --force do not achieve the goal, since only forces the rebuild of the package, but not its re-installation. |
This task depends upon
Comment by Dave Reisner (falconindy) -
Tuesday, 11 February 2014, 16:16 GMT
The --force option in makepkg has a very different meaning from the --force option in pacman. You should not conflate these two things.