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#9294 - unnecessary line wraps when piping pacman output

Attached to Project: Pacman
Opened by Jens Adam (byte) - Tuesday, 22 January 2008, 04:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 20:55 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:
pacman shouldn't contain any special terminal logic or whatever else it is that causes different stdout behaviour, whether the endpoint is an interactive terminal or a pipe.

Steps to Reproduce:
Compare 'pacman -Si (or -Qi) syslog-ng' to 'pacman -Si syslog-ng | grep Description'.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 20:55 GMT
Reason for closing:  Fixed
Comment by Dan McGee (toofishes) - Tuesday, 22 January 2008, 04:24 GMT
That doesn't make any sense. How would we scale progress bars otherwise? It has to contain some terminal logic otherwise interactive output is impossible.

The issue you really wanted to address appears to be line wrapping in --info output, which is a legitimate gripe. Note that normally we do some indented printing, so this is not as cut-and-dry as it may appear.
Comment by Aaron Griffin (phrakture) - Tuesday, 22 January 2008, 17:52 GMT
In previous versions, when there was no tty, we did not output the progress bar at all.
Comment by Allan McRae (Allan) - Sunday, 22 April 2012, 12:04 GMT
Is this an issue anymore? There is no example output so I can not compare, but "pacman -Si syslog-ng | grep Description" looks fine to me now...
Comment by Jens Adam (byte) - Sunday, 22 April 2012, 13:38 GMT
Oh, totally forgot about this one.
Seems like it's solved, I used foomatic-db-engine with its long description and glibc (Required by) for testing.

Loading...