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#11143 - case sensitive configuration files
Attached to Project:
Pacman
Opened by Pierre Chapuis (catwell) - Thursday, 07 August 2008, 17:24 GMT
Last edited by Xavier (shining) - Thursday, 07 August 2008, 18:22 GMT
Opened by Pierre Chapuis (catwell) - Thursday, 07 August 2008, 17:24 GMT
Last edited by Xavier (shining) - Thursday, 07 August 2008, 18:22 GMT
|
DetailsSummary and Info:
I don't know if this behavior is wanted but my config files broke with 3.2.0 because they are no longer case insensitive. Steps to Reproduce: Put a line like: server = ftp://mir2.archlinuxfr.org/archlinux/$repo/os/x86_64 instead of: Server = ftp://mir2.archlinuxfr.org/archlinux/$repo/os/x86_64 in /etc/pacman.d/mirrorlist and you should get: bash-3.2# pacman -Syu error: config file /etc/pacman.d/mirrorlist, line 6: directive 'server' not recognized. error: config file /etc/pacman.d/mirrorlist, line 6: directive 'server' not recognized. error: config file /etc/pacman.d/mirrorlist, line 6: directive 'server' not recognized. :: Synchronizing package databases... error: failed to update core (unexpected error) error: failed to update extra (unexpected error) error: failed to update community (unexpected error) error: failed to synchronize any databases |
This task depends upon
NOTE: Each directive must be in CamelCase. If the case isn't respected, the directive won't be recognized. For example. noupgrade or NOUPGRADE will not work.
Edit: and filing this under the right version number might make this report valid, as this was new in 3.2.0...
http://projects.archlinux.org/?p=pacman.git;a=blob_plain;f=NEWS;hb=HEAD
- config options are now case sensitive