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#17173 - [makepkg] all messages are printed to stderr

Attached to Project: Pacman
Opened by Sven-Hendrik Haase (Svenstaro) - Tuesday, 17 November 2009, 08:36 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 11 October 2019, 19:31 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To Eli Schwartz (eschwartz)
Architecture All
Severity Low
Priority Normal
Reported Version git
Due in Version 5.2.0
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

It appears as though all messages wrong makepkg are written to stderr instead of just the errors. Looking at the makepkg.sh.in source files reveals that this is indeed the case. I believe this is wrong behavior as normal messages should be written to stdout instead. I did not find any clues as to why the current behavior is used.
Can this be considered a bug or am I missing something?
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 11 October 2019, 19:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  https://git.archlinux.org/pacman.git/com mit/?id=882e707e40bbade0111cf3bdedbdac4d 4b70453b
Comment by Allan McRae (Allan) - Tuesday, 17 November 2009, 10:54 GMT
This would break usage like:
"makepkg -g >> PKGBUILD"
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 17 November 2009, 11:11 GMT
So how about a -q flag to enable makepkg -qp >> PKGBUILD usage?
Comment by Dan McGee (toofishes) - Tuesday, 17 November 2009, 13:29 GMT
Because that would change the way us old-school folk have to think about it. :)

That makepkg -g statement is probably muscle memory for most heavy makepkg users out there when they do actual packaging (as opposed to building from ABS). Looking at the issue from another angle, what is the problem with everything going to stderr other than it being unexpected at first?
Comment by Xavier (shining) - Tuesday, 17 November 2009, 17:03 GMT
What about documenting this ? Sven is not the first to ask.

I am just thinking about one line before all printing functions of makepkg. So that if someone looks at makepkg code to find out how stuff are printed, he would find this comment.
Comment by Dan McGee (toofishes) - Tuesday, 17 November 2009, 17:15 GMT
I agree that it should be documented, so patches welcome. :) I'd even go so far to day as this should be noted in both the makepkg code and somewhere in the manpage (not sure where off the top of my head but somewhere appropriate).
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 18 November 2009, 03:59 GMT
So no "correct" behavior for the time being?
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 25 November 2009, 17:16 GMT
Here you greedy man, have your smelly patch. It worked for me ;).
   makepkg.patch (3.6 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 01 December 2009, 20:03 GMT
So is my patch alright and can this bug be closed after merging it?
Comment by Eli Schwartz (eschwartz) - Thursday, 28 June 2018, 17:20 GMT
https://lists.archlinux.org/pipermail/pacman-dev/2018-June/022680.html

Loading...