jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
braewoods_ has quit [Read error: Connection reset by peer]
braewoods__ has joined #crux-devel
ukky has quit [Ping timeout: 245 seconds]
aardo has quit [Ping timeout: 255 seconds]
ardo has joined #crux-devel
sajcho has joined #crux-devel
sajcho has quit [Quit: Client closed]
r0ni has joined #crux-devel
<r0ni> beerman: could we get a possibly change in the 'pinentry' port? the script calls to 'pinentry-gtk2' when it builds 'pinentry-gnome3' for some years now. As-is the script will fail to launch the proper dialog for gtk. I bypassed the port for my uses in the xfce repo, but it prob should be fixed properly for others whom may use the gtk dialog entry
ukky has joined #crux-devel
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
SiFuh has quit [Quit: leaving]
<beerman> r0ni i'll take a look later
<r0ni> thx, also i sent a email... if you do happen to get it, let me know... i think my mail server may be broken lol
<beerman> yeah i got it
<r0ni> awesome woohoo!
ukky has quit [Quit: Rebooting...]
ukky has joined #crux-devel
<beerman> r0ni you are not exactly right, it does build both, pinentry-gtk-2 and pinentry-gnome3, but you are correct in reporting it. I always used gnupg config to set it explicitly.
<beerman> anyway, this is what i came up with, would that work for you? https://dpaste.com/62JVLAKMV
<beerman> line 36 was forgotten, this shouldn't matter with the wrapper we place in PATH
<r0ni> as long as we can get a call to a 'pinentry-gnome3' in there, i'm golden
<r0ni> also that link won't load for me, but as i'm about to step out for work, I trust you'll do it well enough sir
<beerman> thats possible in any way, i only inherited that port, i didn't exactly invent this wrapper myself
<r0ni> ahh it's already there, nice
<beerman> yeah i tested the change and every pinentry works for me, i took the liberty to include the tty frontend as well by default because both that and curses are perfectly valid, so why not have it
<beerman> adjusted the wrapper which still prefers qt because i don't know, it has been up top before and ignoring this wrapper via gnupg configs is a perfect solution as well
<beerman> let me know if you run into anything with that, other than that, I would consider that done. thanks for the report