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#36260 - [pacman] makepkg -i installs packages without checking for file conflicts
Attached to Project:
Pacman
Opened by Alister Hood (Alister) - Wednesday, 24 July 2013, 05:08 GMT
Last edited by Allan McRae (Allan) - Wednesday, 24 July 2013, 07:07 GMT
Opened by Alister Hood (Alister) - Wednesday, 24 July 2013, 05:08 GMT
Last edited by Allan McRae (Allan) - Wednesday, 24 July 2013, 07:07 GMT
|
DetailsDescription:
When I build and install a package with `makepkg -i`, it doesn't check for file conflicts, it just overwrites any existing files. If I build the package with makepkg and then install it with `pacman -U $pkg` then it checks for file conflicts and refuses to install if there are any. Additional info: pacman 4.1.2-1 There don't seem to be any options to makepkg which relate to this, but please let me know if there is a relevant log or something somewhere. |
This task depends upon
Comment by Allan McRae (Allan) -
Wednesday, 24 July 2013, 05:36 GMT
Um... no. "makepkg -i" just calls "pacman -U". You are going to need to provide detailed instructions on how to replicate.
Comment by Allan McRae (Allan) -
Wednesday, 24 July 2013, 05:37 GMT
In fact, firstly provide output of a "makepkg -i" invocation showing a file being overwritten.
Comment by Alister Hood (Alister) -
Wednesday, 24 July 2013, 07:03 GMT
Oh, I see now. Sorry, I was tricked by some subtly faulty PKGBUILDS.
makepkg.conf