You are not logged in.
Trying to install "swift" via pacaur:
/bin/pacman: unrecognized option '--color never'
I've seen that this error existed in pacman recently and has been fixed already.
I've updated my system just now.
But why does the error occur in pacAUR? And taking into account the fact that I've run "sudo pacman -Suy"?
Last edited by Maruba (2018-06-21 05:13:27)
Offline
Pacman doesn't update AUR packages. Rebuild pacaur.
Offline
I've seen that this error existed in pacman recently and has been fixed already.
Fixed, yes. Released? No.
Offline
It's not even fixed, actually. There's a *proposed* fix, which is entirely different: https://bugs.archlinux.org/task/58820
But Allan has not yet merged any new patches for the new 6.0 release cycle. Once he does, this would be fixed in pacman-git.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Odd, it works for me still:
$ sudo pacman --color never -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do
All of that was without color or bold ...
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Did you look at the bugreport I linked?
It's even in the OP's explanation:
/bin/pacman: unrecognized option '--color never'
I could duplicate this quite trivially, because it's not a bug in pacman, it's a bug in makepkg.
$ sudo pacman '--color never' -Syu
pacman: unrecognized option '--color never'
I think it's obvious why this doesn't work, and why makepkg should not be doing that.
EDIT: Migod, I just looked at the pacaur codebase and my eyes started bleeding. Now I remember why I stopped looking last time.
See this gem: https://github.com/rmarquis/pacaur/blob … caur#L2155
pacopts+=("--color $color")
But it doesn't matter, because later it just uses
${pacopts[@]}
No quotes.
EDIT2: The more you look, the more you notice some really eye-watering code which tries grepping pacman.conf to determine whether to pass explicit --color options to pacman... and also --nocolor to makepkg. It's the makepkg --nocolor bit that breaks, because when makepkg gets arrays wrong it actually matters as they get properly quoted when used.
And people claim pacaur is "better" than yaourt. How many have actually read the code???
Last edited by eschwartz (2018-06-11 16:40:51)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Ah, sorry. I didn't expect it to be something that silly. I thought the suggestion was that flag stopped working, not that makepkg or other tools were giving ridiculous flags to pacman.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I found that uncommenting the the line:
#Color
in my /etc/pacman.conf served as a temporary workaround.
Offline