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#371 - Pacman or Documentation bug
Attached to Project:
Pacman
Opened by Chris Hane (chane) - Sunday, 11 January 2004, 17:46 GMT
Last edited by Judd Vinet (judd) - Sunday, 11 January 2004, 20:34 GMT
Opened by Chris Hane (chane) - Sunday, 11 January 2004, 17:46 GMT
Last edited by Judd Vinet (judd) - Sunday, 11 January 2004, 20:34 GMT
|
DetailsSection 3.1.6 of the user documentation has system configuraiton setup information being put into the etc/modules.conf (specificaly network device alias); however this file is upgrade by pacman and overwrites this file with a new version.
Found this issue upgrading a remote computer and lost network contectivity after an upgrade/reboot cycle. Very difficult to correct as I needed to then have physical access to the server. I have put this file into my local copy of etc/pacman.conf as a NoUpgrade, just thought the main distribution should also or other users could run into this issue. |
This task depends upon
Comment by Judd Vinet (judd) -
Sunday, 11 January 2004, 20:33 GMT
True, /etc/modules.conf should never be touched by pacman. I'll add it to the NoUpgrade list in the default pacman.conf.