xiphon: selsta: someone pointed out that the seed offset is not available in the gui. Unless it's deemed to esoteric, maybe it could be added.

moneromooo: yeah, will have a look

It shouldn’t confuse those unfamiliar with seed offset I guess.

Thanks

Snipa: selsta: inspected qt sources, the warning shouldn't have been triggered

^ if -fontconfig configuration option is set

and it will trigger the warning if -fontconfig is missing

maybe is the qt build configuration cache problem?

I've nuked it a few times I thought, I'll hceck again though.

Luigi1111: please remove release 0.15.0.3 from GitHub. We can just have the tag. Linking to binaries that don't exist from an "official" repository is just confusing.

don’t remove the release just remove the links / hashes

I would remove the whole release. I mean, why is it there if we don;t give the binaries?

binaries are just one way to distribute the release

to tease rabid moneristas everywhere

I think some repos have GUI v0.15.0.3

people can self compile

but I agree that links that 404 can be confusing

selsta: yes, but it was never done before. I'm not sayingit doesn't make sense to do it. Just that would be a new thing

We always only tagged if there were no binaries out, but if we want to have a release without binaries we should specify it in the descrition imo

well this release is not normal

we had the binaries ready

so that’s why we pushed it already

but I don’t see the harm it will only confuse those who already use v0.15.0.3

hope we don’t have this situation in the future :D

Alright. Fair enough( i think the vast majority of the GUI users don't build by themselves tho)

right

heyo! Snipa, any news on builds of the .0.3?

there is one bug left

Linux is throwing some fontconfig errors that aren't resolving with the QT rebuilds. I've done some make clean work, but it's still throwing weird errors. Doesn't help that building QT takes forever.

Windows is done and appears to be fine, mac I'll be building on the build server. QT just appears to hate my freetype and refuses to include it, though it looks like it might be something where the configuration test is legitimately wrong, and if I can get around the config test, all will be good.

Or just load the freetype lib into my normal include paths versus it's custom freetype2 build paths.

Even setting up custom linker overrides is being ignored during the test, which is sort of annoying.

growing pains of builds, yeah? hopefully, once resolved, shouldn't extend to further builds