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#22958 - Interactive Handling of Updated Config Files
Attached to Project:
Pacman
Opened by Phillip Smith (fukawi2) - Saturday, 19 February 2011, 10:25 GMT
Last edited by Dan McGee (toofishes) - Monday, 21 February 2011, 13:55 GMT
Opened by Phillip Smith (fukawi2) - Saturday, 19 February 2011, 10:25 GMT
Last edited by Dan McGee (toofishes) - Monday, 21 February 2011, 13:55 GMT
|
DetailsAt the moment pacman has the well-known behavior of creating either .pacnew and/or .pacsave files during upgrades of configuration files that need to be manually reviewed after an upgrade.
It would be nice to have a configurable option in pacman.conf to enable interactive management of these files during upgrade. Debian/apt handle this with the following output: Configuration file `/etc/apache2/mods-available/php5.conf' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** php5.conf (Y/I/N/O/D/Z) [default=N] ? |
This task depends upon
Closed by Dan McGee (toofishes)
Monday, 21 February 2011, 13:55 GMT
Reason for closing: Won't implement
Additional comments about closing: Use pacdiff; if it does not provide all the functionality you are looking for then patches are always welcome to enhance it.
Monday, 21 February 2011, 13:55 GMT
Reason for closing: Won't implement
Additional comments about closing: Use pacdiff; if it does not provide all the functionality you are looking for then patches are always welcome to enhance it.
Comment by Xavier (shining) -
Saturday, 19 February 2011, 10:47 GMT
Just run pacdiff after a pacman upgrade for the same result.