<civodul>artyom-poptsov1: when connecting with guile-ssh, i get this on some machines: no match for method kex algos: server [email@example.com,diffie-hellman-group-exchange-sha256], client [diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]
<civodul>it seems that guile-ssh uses sha1 as its default key exchange algorithms, which is going to cause more and more problems
<mbakke>Not sure, there are probably patches floating around for newer Boost versions.
<mbakke>Or maybe we should switch to MariaDB as the canonical mysql package.
<rekado>mbakke: qtbase and qt are big packages using mysql. Someone should try building those with mariadb.
<thomassgn>how does privelege separation/setuid work with e.g. wireshark? I can't see a group as recommended by the wireshark docs...
<thomassgn>I see in the package definition there is no mention of setuid or similar. I'll look for examples of setuid and similar and see if I can get it working with privelege separation as the wireshark docs intend. :)
<rekado>thomassgn: setuid binaries must be whitelisted in GuixSD
<catonano>guix pull: error: Git error: could not open '/home/catonano/.cache/guix/pull/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq/.git/logs/refs/remotes/origin/rhel6' for writing: Permesso negato
<dijong>hi, my guix installation seems to work ok but when trying to link any c++ programs with g++ -lstdc++, i get this error "test.cpp:(.text+0x7648): undefined reference to `operator delete(void*, unsigned long)'" at the end. i do have libstdc++:out installed, so what else could be the issue?
***loonquawl__ is now known as loonquawl
<dijong>i was able to get it to work by re-installing gcc:lib -- i just did "guix package -i gcc:lib" and it said "gcc:lib 7.3.0 → 7.3.0" and installed, then it worked.
<dijong>speaking of which, what's the best way to check if i've installed a package? doing guix package --show doesn't show that info, currently i just try guix package -i and it says e.g. "7.3.0 → 7.3.0" then i know it's already installed and hit ctrl+C
<mbakke>I haven't been able to reproduce the glibc 2.27 build failure when testing with a (package (inherit (@@ (gnu packages commencement) glibc-final-with-bootstrap-bash)). Nor with the actual "glibc/linux". Very peculiar.
<civodul>these should be the same things, but do they lead to different derivations?