-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
Wlr 0.17 #4752
Wlr 0.17 #4752
Conversation
b1b8dbb
to
1f0fb4e
Compare
3803719
to
92d8b99
Compare
@tych0 @ramnes Tagging you both here to say @jwijenbergh is hoping to have this ready to merge by the weekend. Arch are looking to package |
Sure, I will have some time to do a release this weekend if we land it by then. |
edaead7
to
4182f89
Compare
If you think it's the same failure as before and you're otherwise happy with the branch, I'd say go ahead and merge it and let's do a release. |
It seems like it's working now after bumping |
Should be ready now, bit difficult to test everything but I have been daily driving this for a while without any real issues. There are some small TODOs for upcoming releases though, will make issues for those Note: I have not tested the release workflow changes, but those are the same on pywlroots where they did work. Maybe the release workflow now doesn't work because of pypy? |
caused by:
|
This is the thing where you need to run ffibuild, right? But also, I have not tested the release scripts either. I guess this is from the test pypi upload job? |
It's this step https://github.com/jwijenbergh/qtile/blob/141da0adcab6dfe6328e908f18198fbcb4b57ad9/.github/workflows/release.yml#L202, haven't changed anything there |
That almost looks to me like the ffi build for xkbcommon isn't getting run as part of the wheel build... I have never really understood how all that fits together, and a brief look didn't reveal anything. I'll take a look later. How are you actually running this? it looks like on a successful run, it will really publish the stuff to pypi given that it's not the test job that's failing, but the real one. |
The issue seems to be the 1.0 release of xkbcommon. I changed the release workflow to this and it worked:
I think the |
I am running this by creating a release in my fork. So I expect the upload to fail but not the build |
Ok. The problem is that the manylinux containers do not have a recent enough xkbcommon: https://almalinux.pkgs.org/8/almalinux-powertools-x86_64/libxkbcommon-x11-devel-0.9.1-1.el8.x86_64.rpm.html (needs 1.0) |
Almalinux 8 (quay.io/pypa/manylinux_2_28_x86_64 container) only comes with xkbcommon 0.9 it seems. Now that python-xkbcommon 1.0 is released (which needs xkbcommon >= 1.0), let's build xkbcommon from source such that a xkbcommon._ffi import still works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work in getting this done!
python-version: [pypy-3.10, '3.10', '3.11', '3.12'] | ||
# TODO: Add back pypy here and in release.yml once: | ||
# https://github.com/pypy/pypy/issues/4956 is resolved | ||
python-version: ['3.10', '3.11', '3.12'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we all agreed that we're now dropping pypy 3.10 (as opposed to just allowing it to fail)?
No objections from me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thought process was that for releases it would be nice that CI doesn't fail. After the release we can re-enable it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with me, though can you rebase and drop the continue-on-error I just added as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we do get some movement on that issue, we can always drop the note from the CHANGELOG and re-add pypy to CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, derp. You had it!
OK - this breaks a fair bit of stuff on qtile-extras. I'll need to work through changes to get it working! Edit: nowhere near as bad as I feared. All sorted! |
heh, did qtile migrate help you out? :) |
This patch adds wlroots 0.17 support