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#3009 - forcing install of a package does not work for packages with confilcts
|
Detailsassuming
* I have package A * I have package B, provides=A, conflicts=A I can't install them both using -f, because pacman prompts to uninstall the other one (depending on which on is already installed) and fails if I choose "n" for uninstall. I undestand that pacman is supposed to be error-prone, but is this behaviour the desired one when -f is used? I had the feeling -f should skip all this checking. Well, a warning might work. Maybe -ff (a new argument) could mean total silence when encountering problems. |
This task depends upon
Closed by arjan timmerman (blaasvis)
Wednesday, 22 March 2006, 23:25 GMT
Reason for closing: Not a bug
Wednesday, 22 March 2006, 23:25 GMT
Reason for closing: Not a bug
-d, --nodeps
Skips all dependency checks. Normally, pacman will always check a package's depen-
dency fields to ensure that all dependencies are installed and there are no package
conflicts in the system. This switch disables these checks.
-f, --force
Bypass file conflict checks, overwriting conflicting files. If the package that is
about to be installed contains files that are already installed, this option will
cause all those files to be overwritten. This option should be used with care,
ideally not at all.
Quote:
# pacman -Sf wine
:: wine conflicts with cedega-cvs. Remove cedega-cvs? [Y/n] n
error: package conflicts detected
# pacman -Sd wine
Targets: wine-20050628-1
Total Package Size: 11.7 MB
Proceed with upgrade? [Y/n]
---
I still think there's something fishy going on.
P.S. cedaga-cvs is taken from the wiki
# pacman -Sf wine
:: wine conflicts with cedega-cvs. Remove cedega-cvs? [Y/n] n
error: package ***conflicts*** detected
Quote: man pacman
-f, --force
Bypass file ***conflict*** checks, overwriting conflicting files.
-----------
I was reported a CONFLICT and I tried to bypass the CONFLICT with -f.
I don't know why it worked with -d, since -d skips all DEPENDENCY checks.
It does seem logical to me to find a conflict (and to use -f to bypass it), since cedaga-cvs' PKGBUILD has "conflicts=wine" in it. I am reported conflicts so, what does this have to do with dependencies?
That's what I think it's fishy. It might be a bug in the strings used by pacman to report errors. It might be a bug in the error checking code, returning only one type of error ("conflict") for more errors.
I don't know exactly, but pacman isn't speaking the right English to me (or I'm definitely missing something here).
# pacman -Sf wine
:: wine conflicts with cedega-cvs. Remove cedega-cvs? [Y/n] n
error: ***package conflicts*** detected
Quote: man pacman
-f, --force
Bypass ***file conflict*** checks, overwriting conflicting files.
It still confused me though...