<r​ecanman:agoradesk.com> I can contribute 10kh/s. Do you still need someone to mine on testnet?

<r​ecanman:agoradesk.com> I can contribute ~10kh/s. Do you still need someone to mine on testnet?

<j​ohn_r365:monero.social> selsta & sech1 - I see you're both doing your best to try and progress the Trezor PR, but we're running into brick walls so far.

<j​ohn_r365:monero.social> I don't want to spam the Github PR, so will ask on here.

<j​ohn_r365:monero.social> Is a there a viable workaround if the build documentation is updated to specifically instruct users to install these dependencies?

<j​ohn_r365:monero.social> Or to ask more directly, selsta - are there any workarounds you'd accept, short of waiting for some verdict on #8922 and C++ 17?

<j​ohn_r365:monero.social> No worries if not, but just trying to better understand what's possible.

Is anyone else getting this on their node? paste.debian.net/hidden/1f1afafb "Exception at [portable_storage::load_from_binary], what=duplicate key: support_flags"

Does anybody happen to know whether I can directly merge from one branch into another interactively on GitHub?

First looks did not turn up. Maybe anyway no good idea because what would happen if there were conflicts?

<b​oog900:monero.social> Someone in offtopic asked about that yesterday

rbrunner You can just replace branch names in the URL github.com/monero-project/monero/compare/master...release-v0.18

There is a "create pull request" button

Thanks, will try

sech1: someone is running a broken modified node and is sending invalid p2p packets

john_r365: we also need C++17 for the GUI, Qt 5.15 is EOL and doesn't receive security updates anymore and Qt 6 requires C++17

that would be the cleanest solution, otherwise the changed dependencies have to be documented well and I already know we will get lots of issues asking why compilation is suddenly broken

I wonder if that broken/modified node is related to this nevocoin thing. maybe somebody forgot to clean the node list.

possible, but I've seen this message often on my node before this fork launched

<j​ohn_r365:monero.social> selsta - thanks for the reply. Ok, well, that does sound like a good reason to push forward with C++ 17.

<j​ohn_r365:monero.social> I'll revisit that thread and look at what the various complaints relate to regarding the upgrade.

<j​ohn_r365:monero.social> What would it take to move things forward in that regard?

<j​ohn_r365:monero.social> have left a comment for vtnerd and jtgrassie to get their thoughts on C++ 17, and see if the issue with Qt 6 / GUI / C++ 17 changes their point of view. As previously they were against moving to v17 simply to satisfy the Trezor PR.

<v​tnerd:monero.social> I'm primarily only against c++ version upgrades because it requires newer compilers, etc. I think someone pointed out that the last Ubuntu LTS has c++17 support, so maybe this isn't a big deal