Yes 2> is stderr correct?

try
pacman [blah] >> file 2>&1

this one’s in the AUE

AUR

@Night_H4nter aue

no luck

osuzhdayu

i have no clue why it’s not just going into the file

i’ve tried 2>

i’ve tried everything

Nope, that machine was so fucked up he just reinstalled.

I’m confused why >> isn’t making the output for grep warnings

go into a file

is there a way to do that

truth

with sufficient skill and time, anything is fixable
of course, that doesn’t mean it’s worth it, and you’re not better off with redoing from scratch

I’m kinda invested in this

so i’m gonna keep at it

I think that scenario was fixable with pacman’s –root flag

because warnings go to stderr, not stdout

yes 2> is stderr correct?

2> is redirecting the stderr

fd 2 is stderr, yes

anyway, do the chown with 0:0 and follow-symlinks

–dereference

oh rn i’m trying to get the output of my pacman error log

but using 2> out.txt isn’t working

At some point you spend more time trying to fix it than just reinstalling it. 😆

exactly

I’m doing a similar thing with an android phone currently

I fucked up the baseband

and the time I spent trying to fix it is starting to top the cost of just buying another one

reinstalling would be faster for me

Nope, it had mismatched versions of hundreds of libs and packages. Because of the partial upgrade, that isn’t a viable solution.

pacman -Qkk | grep warnings 2> out.txt