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#23340 - Group selection mechanism

Attached to Project: Pacman
Opened by Taylan Ulrich B. (taylanub) - Friday, 18 March 2011, 21:37 GMT
Last edited by Allan McRae (Allan) - Monday, 21 March 2011, 13:22 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version 3.5.0
Due in Version 3.5.1
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The group member listing and selection prompt seem to be printed out in inappropriate cases.

- Before pacman bails out due to missing dependencies anyway.
- Before the expected output comes when using 'pacman -Sp ...'.

In both those cases, the member listing and prompt are being displayed, but it doesn't wait for input, and just moves on.

The second case is especially annoying because:
* The whole thing goes to stdout and not stderr.

So when you have a script that tries to get specific package information via "pacman -Sp --print-format ... packages..." and the packages list contains a group name, the output will be cluttered with the group member selection text.
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 21 March 2011, 13:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit b0bb4f90
Comment by Allan McRae (Allan) - Saturday, 19 March 2011, 05:29 GMT
Can you post some actual output for this case:
> Before pacman bails out due to missing dependencies anyway.

I have no idea what you are trying to describe and thus no way to replicate.
Comment by Taylan Ulrich B. (taylanub) - Saturday, 19 March 2011, 18:36 GMT
To be honest, now i don't know either what exactly i meant with that part, and can't reproduce what i could possibly have meant. Sorry, no more bug reporting with a tired mind.
Comment by Dan McGee (toofishes) - Sunday, 20 March 2011, 17:05 GMT
Include a *simple test case* next time rather than only generalizing. Something as simple as `pacman -Sp pacman base` would have helped here.

It doesn't wait for input intentionally, whether this was expected or not. --print enables --noconfirm, which then tells pacman to print all questions to stdout for easier capture. This has been happening for some time.

We should probably figure out what we want to be doing in the case of --print/--noconfirm/showing questions. We have three different things that are a bit too munged together.
Comment by Allan McRae (Allan) - Monday, 21 March 2011, 11:54 GMT
Patch.

Loading...