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#30755 - Add means to show informative text when using -f/--force and to have an extra confirmation
Attached to Project:
Pacman
Opened by Erik Ridderby (Paddlaren) - Thursday, 19 July 2012, 11:27 GMT
Last edited by Dan McGee (toofishes) - Friday, 20 July 2012, 16:38 GMT
Opened by Erik Ridderby (Paddlaren) - Thursday, 19 July 2012, 11:27 GMT
Last edited by Dan McGee (toofishes) - Friday, 20 July 2012, 16:38 GMT
|
DetailsSummary and Info: Add means to show informative text when using -f/--force and to have an extra confirmation that the user is aware of the concequences
Given the recent problems with the move of /lib to /usr/lib where many users inadvisedly has been using -f with unexpected results it is possible that many broken systems could have been prevented if the package maintainer could provide a package specific message strongly advice not to use -f. I guess that there are other situations where -f is the last resort and that some helpful last minute information could make sense. The suggestion is that it shall be possible to provide information in the package that is displayed along with a confirmation that the intention really is to use the -f flag. Some references: http://jasonwryan.com/blog/2012/07/19/breakage/ http://allanmcrae.com/2012/07/the-arch-linux-testing-repo-is-for-testing/ E.g: #pacman -S glibc **** You are using the -f/--force flag when upgrading the glibc **** Please consider the following: Never use --force during this update as this is likely to break your system. If either of this steps does not work (e.g. due to dependency version issues, file conflicts in /lib), refer to this guide for more detailed instructions on performing this upgrade. Please refer to http://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ for further information. Continue with -f enabled [y/N]? |
This task depends upon
Closed by Dan McGee (toofishes)
Friday, 20 July 2012, 16:38 GMT
Reason for closing: Won't fix
Additional comments about closing: We removed -f, but we're not going to do any more hand holding than that, nor make the process more interactive than strictly necessary.
Friday, 20 July 2012, 16:38 GMT
Reason for closing: Won't fix
Additional comments about closing: We removed -f, but we're not going to do any more hand holding than that, nor make the process more interactive than strictly necessary.
I suggest that when the user need to take extra care during an update the user shall be informed one way or another, preferably in the same context as where the update is being made.
One way is to add the message as I suggested, another way is to look at how Gentoo portage does; portage has a news system where emerge will tell you to read the information before an update is performed. My experience is that this worked just fine and that the information was mostly relevant as with the Arch Linux Official News Channel on the home page.
The question is rather "In this particular case we suggest that -f/--force will break you system. Do you want to break your system?" can actually be welcomed of some users.
I don't really see how the general change from -f to --force makes the user aware of that this particular time --force will break your system. The only reason I know that -f was/will be removed with a particular intention is because I read about it, I would not guessed on my own.