00:49:34 <gingeropolous> when did message type get shrunk to a single letter?
01:30:05 -xmr-pr- iamamyth opened pull request #9809: logging: Fix easylogging++ init with blank config
01:30:05 -xmr-pr- > https://github.com/monero-project/monero/pull/9809
04:19:26 <m-relay> <j​effro256:monero.social> what do you mean "message type"?
11:09:15 <gingeropolous> i mean the info messages in the console. its nothing, nevermind.
11:09:29 <gingeropolous> im seeing these in my logs again: start_outer_call failed . I remember them from a while back
17:37:52 <m-relay> <s​yntheticbird:monero.social> Regarding Rust dependency in monero: https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html
17:39:12 <m-relay> <k​ayabanerve:matrix.org> SyntheticBird: What's the claimed relevance? Not every Rust update will be relevant. While this is major, I don't see it as relevant.
17:43:18 <m-relay> <s​yntheticbird:monero.social> I was just going to say: I don't know how Rust update are going to work with monero codebase, but it could update requirement to 1.85 and Rust edition 2024.
17:56:03 <m-relay> <t​obtoht:monero.social> SyntheticBird: For release builds, we will use whichever version is available to us in Guix (which is currently 1.82). See also: https://github.com/monero-project/monero/pull/9801
18:47:23 <m-relay> <p​reland:monero.social> Speaking of builds….when is the miniupnp issue going to be fixed
18:48:06 <m-relay> <s​yntheticbird:monero.social> I pray everyday for miniupnp to be removed
18:48:12 <m-relay> <s​yntheticbird:monero.social> no one use it
18:48:39 <sech1> what issue
18:49:05 <m-relay> <p​reland:monero.social> Build fails because of gcc changes
18:49:40 <sech1> fails because of miniupnp? I use it in P2Pool and it doesn't give me any issues with a wide range of compilers
18:49:53 <m-relay> <p​reland:monero.social> Using env vars to change the compiler used to fix it, but it stopped working for some reason last night
18:50:05 <m-relay> <p​reland:monero.social> It only threw the error after clean building it
18:50:50 <m-relay> <p​reland:monero.social> I was able to fix it by doing the manual su module cmake thingy and forwarding miniupnp to a newer version…..sorta
18:50:57 <m-relay> <p​reland:monero.social> Still throws some cryptic errors
18:52:24 <m-relay> <o​frnxmr:xmr.mx> sounds like user error ?
18:53:50 <m-relay> <p​reland:monero.social> Could be
18:54:27 <m-relay> <p​reland:monero.social> I can check it again today and see if it magically gets fixed (as these things tend to work out)
18:54:29 <m-relay> <s​yntheticbird:monero.social> bro literally dropped a "sjill issue"
18:54:33 <m-relay> <s​yntheticbird:monero.social> "skill issue"*
18:55:41 <m-relay> <o​frnxmr:xmr.mx> What os/distro are you using to build, and what steps are you taking
18:58:14 <m-relay> <m​onero.arbo:matrix.org> I just built master today with guix fwiw
18:58:30 <m-relay> <m​onero.arbo:matrix.org> very sexy very working
20:16:32 <m-relay> <k​ayabanerve:matrix.org> The Monero Rust libs wouldn't benefit from the 2024 edition AFAIK.
20:16:53 <m-relay> <k​ayabanerve:matrix.org> I'm not saying some niche features from it couldn't be used, but it's not like we have async code or anything with crazy borrow rules.
20:17:17 <m-relay> <k​ayabanerve:matrix.org> So there isn't reason to update to that requirement due to how much work it'd be.
23:36:44 <m-relay> <a​remor:matrix.org> I’ve seen this when attempting to cross compile. That’s your use case?