jaeger changed the topic of #crux to: CRUX 3.7 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
tilman has joined #crux
<r0ni> there appears to be a circular dep in 'gcr3' and i'm having trouble figuring out which one it is, but prt-get does NOT like it
<r0ni> prt-get deptree that is
<r0ni> but maybe i'm causing that, no clue yet. still testing
<r0ni> nope, yep my fault
<r0ni> adding gcr3 to pinentry deps appears to make the OS shit the bed, so I'll just have to leave it alone.. odd but ok
XXX1232 has quit [Ping timeout: 248 seconds]
XXX1232 has joined #crux
groovy2shoes has joined #crux
braewoods_ has joined #crux
braewoods has quit [Ping timeout: 248 seconds]
joe9 has quit [Quit: leaving]
remiliascarlet has quit [Read error: Connection reset by peer]
remiliascarlet has joined #crux
<cruxbot> [contrib.git/3.7]: hwloc: 2.9.2 -> 2.9.3
brian_ has quit [Read error: Connection reset by peer]
lavaball has joined #crux
lavaball has quit [Quit: lavaball]
lavaball has joined #crux
dbrooke has quit [Server closed connection]
dbrooke has joined #crux
<farkuhar> r0ni: `finddeps pinentry` does reveal eager linking of gcr3 into the pinentry package, so I can understand why you might have wanted to add gcr3 among the pinentry deps. This insertion wouldn't cause a dependency cycle if there were no such link gnupg => pinentry.
<farkuhar> According to finddeps, gnupg has no dynamic linking with pinentry, it's just a runtime dependency. You could delete pinentry from the gnupg deps, but you'd need to warn the user about the loss of functionality from doing only the minimal depinst.
sajcho has joined #crux
<farkuhar> r0ni's modified pinentry would have to live outside the opt repo, though, lest it violate the rules encoded in sepen's repoverify tool: https://lists.crux.nu/pipermail/crux-devel/2008-July/003697.html
<sajcho> solution: add --disable-pinentry-{fltk,gnome3,gtk2,qt,qt5,tqt} - and it's done
sajcho has quit [Quit: Client closed]
exark has quit [Quit: quit]
exark has joined #crux
<cruxbot> [contrib.git/3.7]: libsodium: 1.0.18 -> 1.0.19
<cruxbot> [contrib.git/3.7]: ncpamixer: 1.3.3.5 -> 1.3.7
<cruxbot> [contrib.git/3.7]: unicode-character-database: 15.0.0 -> 15.1.0
<cruxbot> [core.git/3.7]: curl: 8.2.1 -> 8.3.0
lavaball has quit [Quit: lavaball]
<cruxbot> [compat-32.git/3.7]: libglvnd-32: 1.6.0 -> 1.7.0
<cruxbot> [compat-32.git/3.7]: curl-32: 8.2.1 -> 8.3.0
lavaball has joined #crux
<cruxbot> [contrib.git/3.7]: python3-rapidfuzz: 3.2.0 -> 3.3.0
<cruxbot> [contrib.git/3.7]: httpbin: fixed url, source and footprint
remiliascarlet has quit [Ping timeout: 252 seconds]
remiliascarlet has joined #crux
<r0ni> farkuhar i originally had it named 'pinentry-gtk' but recently changed it when i noticed it fails to install since it overwrites the existing /usr/bin/pinentry, since that file is actually gimped in the distro with a wrong filename, so i decided it best to "append" any existing install of pinentry with the gnome3 binary as well. but to ensure it built properly i added gcr3 to deps, only to find this issue, but now I see the cycle where I
<r0ni> hadn't noticed prior
serpente has joined #crux
lavaball has quit [Remote host closed the connection]
<r0ni> ff/thunderbird zero day effecting everything below 117.0.1 / ESR 115.2.1/102.15.1 - thunderbird prior to 102.15.1 / 115.2.2 afaik the vuln is being exploited
<cruxbot> [opt.git/3.7]: [notify] thunderbird-bin: updated to version 115.2.2
<farkuhar> r0ni: Heh, I guess if you want the gnome3 binary then sajcho's solution --disable-pinentry-{fltk,gnome3,gtk2,qt,qt5,tqt} would not work for you.
tilman has quit [Ping timeout: 252 seconds]
tilman has joined #crux
<farkuhar> r0ni: the portdb has pinentry-gnome3 in the nullspoon repo, and pinentry-allenable in sajcho's repo. Maybe take a look at those ports to get some ideas.