29 Replies
I think you are right
akmod-xone-0.0.git.44.36f58c71-1.fc39.x86_64 looks like it's pulling dev deps@Kyle Gospo does this revert and the corresponding rebuild in COPR fix xone pulling all that extra stuff?
https://github.com/ublue-os/packages/commit/36f58c717eb0d094ef891a51e97771a4ceda7265
GitHub
Revert "chore: Update xone akmod repo" · ublue-os/packages@36f58c7
This reverts commit 19cde99bae93af2b7f57fa4c07a87537f6e1f0df.
It did not, testing why it's no longer building
when I only pulled a single line fix
can look at that separately
the scheduled akmods builds from this morning were fine... it was later in the day we had extra deps pulled in
hhmm... i think
change was the removal of a single line in a C file
doubt that touched deps
something's funky lol
well, the problem i'm talking about is not actually the
akmod-xone ... or kmod package... it's the xone-kmod-common version change
https://pastebin.com/xiSUzepX - @bketelsen 's update from earlier...
and this is mine after i just did a rebuild of my custom image... my scheduled build this morning was normal, i updated... and now I rebuild and see this...
https://gist.github.com/bsherman/b5b416d5451c23af3297a129d2650b9bLook at xone-kmod-common though, all I did was change the source
and if you look at the sources, they exactly match
i'm just glad the source has been found - if not yet fixed. I really didn't want to put all that stuff on my daily driver
i'll look closer here
i'm strugging to see why the version changed
0.0.git.37.0dc082d0-1.fc39 -> 0.0.git.44.36f58c71-1.fc39
oh, that's the ublue-os/packages git metaRight
So no change besides the version string
Unless I merge the commit I intended to this morning to remove one line
And now for some reason builds are failing regardless
yeah... i'm going to build this thing local to try to sort it out
Switched back to my fork, pulled in the tiny changes I needed, and pulled in the latest spec file from negativo
Should at least successfully build now
Which leaves the dependency change mystery
well, a test of latest akmods changes, built locally on main-base:39... and with xone-kmod-common 0.0.git.45.5441d09a-1 looks good
So weird
agree, i'm not sure what to think about that
that xonedo repo still excludes xpad stuff right?
i'm building my custom image to validate all this on the github side
It's xone modified to not do any controllers over USB
Leaving xpad to handle that
Gift from chimera
hmm... so,
usb dongle with xbox one devices work with
xone
bluetooth xbox one devices work with xpadneo
and ALL xbox usb devices fallback to xpadYep
well, my kids haven't complained 😄
they mostly use xpadneo... but one had to plug in via USB because of a bug in steam+game recently
That's a win, folks!
https://gist.github.com/bsherman/02ecdc0ad830b6593b873e1f2fce5cef
just need bluefin to update and this is good
Gist
fixed rpm-ostree update kmod-xone
fixed rpm-ostree update kmod-xone. GitHub Gist: instantly share code, notes, and snippets.
and hope @j0rge didn't build ISOs with that mess in it
I can rebuild
we have the techology... we can rebuild him.
what was the issue?
i don't know if your recent ISO builds have the flaw, but some weird issue with the xone-kmod-common package was pulling in a ton of dev packages
the thing Brian was asking about a few hours ago in bluefin/ublue-dev
@bouhaa FYI, xone needs an update for a sleep issue in newer kernels
My fork of your repo adds the new applicable commits
I was around when he found it
but was on dad mode for most of it
glad we found it!
Yay, thanks all for tracking it down.
Thanks, I thought I had a pull.yml. Something must be wrong then