Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GR] bump version #7371

Merged
merged 2 commits into from Sep 21, 2023
Merged

[GR] bump version #7371

merged 2 commits into from Sep 21, 2023

Conversation

jheinen
Copy link
Contributor

@jheinen jheinen commented Sep 19, 2023

bump GR version to 0.72.10

bump GR version to 0.72.10
@jheinen
Copy link
Contributor Author

jheinen commented Sep 19, 2023

No idea how to fix this. Or should I stay with the old Qt 6.4.2 version?

BTW: We use 6.5.2 in our "local" CI system and it passes all tests ...

@barche
Copy link
Contributor

barche commented Sep 19, 2023

I set GCC to version 10, this should fix the error.

@barche
Copy link
Contributor

barche commented Sep 19, 2023

Not sure if I did something wrong on my end, but a quick test with the downloaded artifact from the build here fails, so don't merge this just yet.

@barche
Copy link
Contributor

barche commented Sep 19, 2023

Joy oh joy, the new Qt6.5 package is missing the XCB platform and can't work on Linux X11. I missed that because I did all this on my other machine, which is on Wayland.

@barche barche marked this pull request as draft September 19, 2023 12:56
@jheinen
Copy link
Contributor Author

jheinen commented Sep 21, 2023

@barche : Do you think the draft status can be removed now with the successful build of Qt6 (including XCB extensions)?

@barche
Copy link
Contributor

barche commented Sep 21, 2023

Testing now with the new Qt6Base binaries and the compiled artifact from this PR plotting with GR gives the following error. I have no immediate ideas on how to solve this:

.julia/dev/GR_jll/override/bin/gksqt: /usr/bin/../lib/julia/libcurl.so.4: version `CURL_OPENSSL_4' not found (required by /usr/lib/libproxy/libpxbackend-1.0.so)
connect: Connection refused
GKS: can't connect to GKS socket application

@giordano
Copy link
Member

giordano commented Sep 21, 2023

You're using a system library (/usr/lib/libproxy/libpxbackend-1.0.so), that's the problem.

@barche barche marked this pull request as ready for review September 21, 2023 10:32
@barche
Copy link
Contributor

barche commented Sep 21, 2023

Correct, I was accidentally using the Julia from arch linux. Works fine with the official binary for me now.

@giordano
Copy link
Member

How did that happened though?

@barche
Copy link
Contributor

barche commented Sep 21, 2023

Still investigating, because I thought I was using julia-bin from AUR. Trying with a vanilla 1.9.3 download now, on 1.8.5 it worked.

@barche
Copy link
Contributor

barche commented Sep 21, 2023

Also the downloaded julia 1.9.3 official binary works fine with the artifacts from this PR, so whatever it is, it is something in my installation getting mixed up. I think it's safe to merge this PR.

@jheinen
Copy link
Contributor Author

jheinen commented Sep 21, 2023

@giordano : LGTM - I will bump GR.jl as soon as #7371 is merged.

@giordano giordano merged commit c5aa67f into JuliaPackaging:master Sep 21, 2023
20 checks passed
@jheinen
Copy link
Contributor Author

jheinen commented Sep 21, 2023

Thanks!

@charperflow
Copy link

@barche Did you ever figure out how your system libraries were getting pulled in? I am currently running into the same issue and only have julia-bin installed from the AUR!

@barche
Copy link
Contributor

barche commented Jan 10, 2024

No, I never figured it out, I switch to a manually downloaded Julia whenever this comes up here.

@charperflow
Copy link

Well the AUR now has two supported versions, julia-bin and juliaup. I found that switching to juliaup provided a work around, but I also couldn't figure out the source of the problem :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants