Pacman

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.
Tasklist

FS#39976 - [pacman] 'Proceed with installation?' confirmation threats ' n' as YES

Attached to Project: Pacman
Opened by ... (spider007) - Sunday, 20 April 2014, 14:05 GMT
Last edited by Allan McRae (Allan) - Friday, 23 May 2014, 11:16 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Somehow pacman incorrectly interprets ' n' as YES when asking for confirmation:

# pacman -S pacman
warning: pacman-4.1.2-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Packages (1): pacman-4.1.2-5

Total Installed Size: 3.70 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n] n
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
(1/1) reinstalling pacman [######################] 100%

This is unexpected and unwanted behavior. Responses such as ' asdf' is correctly interpreted as NO
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 23 May 2014, 11:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in git commit 5293d578
Comment by Allan McRae (Allan) - Sunday, 20 April 2014, 14:30 GMT
Please supply output using --debug.
Comment by Allan McRae (Allan) - Sunday, 20 April 2014, 15:12 GMT
Ignore that - bug found and patched.
Comment by ... (spider007) - Sunday, 20 April 2014, 15:37 GMT
I know the bug is in strtrim, which incorrectly thinks ' x' consists of whitespace only; I doubt that a debug-log will help?

edit: ah, nvm. Nice!

Loading...