BI think you are right
Bakmod-xone-0.0.git.44.36f58c71-1.fc39.x86_64 looks like it's pulling dev depsB@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
https://github.com/ublue-os/packages/commit/36f58c717eb0d094ef891a51e97771a4ceda7265
GitHub
This reverts commit 19cde99bae93af2b7f57fa4c07a87537f6e1f0df.
KIt did not, testing why it's no longer building
Kwhen I only pulled a single line fix
Kcan look at that separately
Bthe scheduled akmods builds from this morning were fine... it was later in the day we had extra deps pulled in
Bhhmm... i think
Kchange was the removal of a single line in a C file
Kdoubt that touched deps
Ksomething's funky lol
Bwell, the problem i'm talking about is not actually the
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/b5b416d5451c23af3297a129d2650b9b
akmod-xone ... or kmod package... it's the xone-kmod-common version changehttps://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/b5b416d5451c23af3297a129d2650b9b
KLook at xone-kmod-common though, all I did was change the source
Kand if you look at the sources, they exactly match
Bi'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
Bi'll look closer here
Bi'm strugging to see why the version changed
0.0.git.37.0dc082d0-1.fc39 -> 0.0.git.44.36f58c71-1.fc39Boh, that's the
ublue-os/packages git metaKRight
KSo no change besides the version string
KUnless I merge the commit I intended to this morning to remove one line
KAnd now for some reason builds are failing regardless
Byeah... i'm going to build this thing local to try to sort it out
KSwitched back to my fork, pulled in the tiny changes I needed, and pulled in the latest spec file from negativo
KShould at least successfully build now
KWhich leaves the dependency change mystery
Bwell, 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
KSo weird
Bagree, i'm not sure what to think about that
Bthat xonedo repo still excludes xpad stuff right?
Bi'm building my custom image to validate all this on the github side
KIt's xone modified to not do any controllers over USB
KLeaving xpad to handle that
KGift from chimera
Bhmm... so,
usb dongle with xbox one devices work with
bluetooth xbox one devices work with
and ALL xbox usb devices fallback to
usb dongle with xbox one devices work with
xonebluetooth xbox one devices work with
xpadneo and ALL xbox usb devices fallback to
xpadKYep
Bwell, my kids haven't complained 
Bthey mostly use xpadneo... but one had to plug in via USB because of a bug in steam+game recently
BThat's a win, folks!
https://gist.github.com/bsherman/02ecdc0ad830b6593b873e1f2fce5cef
just need bluefin to update and this is good
https://gist.github.com/bsherman/02ecdc0ad830b6593b873e1f2fce5cef
just need bluefin to update and this is good
Gist
fixed rpm-ostree update kmod-xone. GitHub Gist: instantly share code, notes, and snippets.
Band hope @j0rge didn't build ISOs with that mess in it
JI can rebuild
Bwe have the techology... we can rebuild him.
Jwhat was the issue?
Bi 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
Bthe thing Brian was asking about a few hours ago in bluefin/ublue-dev
K@bouhaa FYI, xone needs an update for a sleep issue in newer kernels
KMy fork of your repo adds the new applicable commits
JI was around when he found it
Jbut was on dad mode for most of it
Jglad we found it!
