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#1397 - option to stop upgrading on first conflict
Attached to Project:
Pacman
Opened by Mircea Bardac (IceRAM) - Tuesday, 07 September 2004, 21:07 GMT
Opened by Mircea Bardac (IceRAM) - Tuesday, 07 September 2004, 21:07 GMT
|
DetailsWhen big packages are upgraded/installed and many conflicts appear (from different reasons), pacman seems to stall because it lacks any progress bar while checking for file conflicts.
There should be some kind of option in /etc/pacman.conf to make pacman stop on first conflict. Q: Why stop on first conflict? A: Because it won't work anyway afterwards. Q: Why a new option and not something enabled by default? A: To preserve the current functionality. Of course, because it's only ONE conflicting file, pacman could show the package owning it (or 'no owner package', if possible). I leave it to your choice wether to make it turned on by default or not. Of course, you can make it a built-in function (no option in pacman.conf), but might not be very fortunate for the users who do unattended upgrading and rely on watching /var/pacman.log and fixing all conflicts at a time. |
This task depends upon
Closed by Judd Vinet (judd)
Wednesday, 08 September 2004, 20:06 GMT
Reason for closing: Won't implement
Wednesday, 08 September 2004, 20:06 GMT
Reason for closing: Won't implement
As most conflicts are usually isolated within one package, it won't take that much longer to build a full list of conflicts than it will to display one and exit.