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#25099 - Some error are displayed on stdout

Attached to Project: Pacman
Opened by Sébastien Luttringer (seblu) - Sunday, 10 July 2011, 22:12 GMT
Last edited by Dan McGee (toofishes) - Monday, 22 August 2011, 16:39 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.5.3
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

When desc files are missing in /var/lib/pacman/local/*/ pacman print error on stdout in place of stderr.

archipel ~ 1 # pacman -Qs toto 2>/dev/null
error: could not open file /var/lib/pacman/local/xterm-270-1/desc: No such file or directory
...

This impact some capacities of pacman. By example when was filesystem is corrupted and you want to reinstall all your system, doing something like wiki suggest it is impossible:

pacman -S $(comm -23 <(pacman -Qeq) <(pacman -Qmq))

Another impact is when you call makepkg, you can see output in attachment.

I looked into the code and i don't find an easy way to fix. I will look more closely later.

Steps to Reproduce:
Remove a file like /var/lib/pacman/local/xterm*/desc
   BUG (2.2 KiB)
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 22 August 2011, 16:39 GMT
Reason for closing:  Implemented
Additional comments about closing:  Commit b6914d16cc
Comment by Allan McRae (Allan) - Wednesday, 13 July 2011, 14:06 GMT
I am not 100% confident that this is the right thing to do... but it "fixes" this issue.
Comment by Dan McGee (toofishes) - Saturday, 16 July 2011, 15:28 GMT Comment by Dan McGee (toofishes) - Friday, 19 August 2011, 23:58 GMT
I think I'm OK with this, but do WARNING level messages belong there too?

Loading...