FS#58821 - [pacman] unrecognized option

Attached to Project: Arch Linux
Opened by Daniel Wendler (BMRMorph) - Friday, 01 June 2018, 08:27 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 June 2018, 13:32 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrade to pacman 5.1 i've got strange results with the "-m" switch for makepkg.
This call results in "/usr/bin/pacman: unrecognized option '--color never'" if i call it on an PKGBUILD.
If i run the build without the "-m" it works as expected.
I can also run for example "pacman -S --color never git" without problems.
I've can reproduce this easily with the "base/devel" docker container.


Additional info:
* package version(s): Pacman v5.1.0 - libalpm v11.0.0


Steps to reproduce:
docker run --rm -it base/devel bash
pacman -Sy
useradd -m pkg
echo "pkg ALL = NOPASSWD: ALL" > /etc/sudoers.d/pkg && chmod 0440 /etc/sudoers.d/pkg
su - pkg
curl https://aur.archlinux.org/cgit/aur.git/snapshot/package-query.tar.gz --output package-query.tar.gz
tar -xf package-query.tar.gz
cd package-query
makepkg -ms --noconfirm
==> Making package: package-query 1.9-3 (Fri Jun 1 08:10:34 2018)
==> Checking runtime dependencies...
==> Installing missing dependencies...
/usr/bin/pacman: unrecognized option '--color never'
==> ERROR: 'pacman' failed to install missing dependencies.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 01 June 2018, 13:32 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#58820 

Loading...