since that copies something to /tmp to

since that copies something to /tmp to run

15 Replies

Starting a thread since I didn't want to continue to disrupt the other meaningful conversation. So there was a typo more or less, that should be resolved. Could you possibly kick off a new build with the revised changes? @Kyle Gospo sorry for the poke, to be honest I have no idea if it pings folks when you make a thread like this. That said, I resolved that obvious issue in the akmods.

Kyle GospoOP•8mo ago

all good, ty yep, kicking off now

Waffleophagus•8mo ago

👍🏻 the ones that are failing are failing in build prep, I'll take a look

error: No matches for 'kernel' in repo 'copr:copr.fedorainfracloud.org:sentry:kernel-fsync'

error: No matches for 'kernel' in repo 'copr:copr.fedorainfracloud.org:sentry:kernel-fsync'

That uh, doesn't feel like my stuff at all?

Kyle GospoOP•8mo ago

it's not, you can ignore should only apply to fsync builds did any common build?

Waffleophagus•8mo ago

/bin/sh: line 1: /tmp/build-kmod-framework-laptop-tests.sh: Permission denied

/bin/sh: line 1: /tmp/build-kmod-framework-laptop-tests.sh: Permission denied

😅

Kyle GospoOP•8mo ago

oop

Waffleophagus•8mo ago

git doesn't track ownership like that right? Like, if I chmod it locally, that doesn't change the file as far as git sees right? I'm guessing its not quite that?

Kyle GospoOP•8mo ago

it does, give it ashot

Waffleophagus•8mo ago

(when you've used a tool for over a decade and had no idea how that kinda stuff worked) one chmod a+x and we're pushed again. Wait... can I just run the action in my own forked repo to not poke you every time I fix a tiny thing? yes... yes I can. Good news is we got a lot farther! Bad news is, at least on my build, its failing and its no longer clear to me why. https://github.com/Waffleophagus/akmods/actions/runs/8543889511/job/23408689155

 2024/04/03 18:45:01 akmodsbuild: + '[' -e /etc/pki/akmods/certs/public_key.der ']'
2024/04/03 18:45:01 akmodsbuild: + /usr/lib/rpm/brp-kmodsign /etc/pki/akmods/private/private_key.priv /etc/pki/akmods/certs/public_key.der /tmp/akmodsbuild.4Iqzwny7//BUILDROOT/evdi-kmod-1.14.2-1.fc39.x86_64/lib/modules/6.7.11-200.fc39.x86_64/extra/evdi/ /usr/src/kernels/6.7.11-200.fc39.x86_64
2024/04/03 18:45:01 akmodsbuild: At main.c:170:
2024/04/03 18:45:01 akmodsbuild: - SSL error:1E08010C:DECODER routines::unsupported: crypto/encode_decode/decoder_lib.c:102
2024/04/03 18:45:01 akmodsbuild: sign-file: /etc/pki/akmods/private/private_key.priv
2024/04/03 18:45:01 akmodsbuild: /usr/lib/rpm/brp-kmodsign: line 40: warning: command substitution: ignored null byte in input
2024/04/03 18:45:01 akmodsbuild: brp-kmodsign: modules are unsigned!
2024/04/03 18:45:01 akmodsbuild: error: Bad exit status from /var/tmp/rpm-tmp.ifMChb (%install)
2024/04/03 18:45:01 akmodsbuild: 
2024/04/03 18:45:01 akmodsbuild: RPM build errors:
2024/04/03 18:45:01 akmodsbuild:     Bad exit status from /var/tmp/rpm-tmp.ifMChb (%install)
2024/04/03 18:45:01 akmodsbuild: 
2024/04/03 18:45:01 akmods: Building rpms failed; see /var/cache/akmods/evdi/1.14.2-1-for-6.7.11-200.fc39.x86_64.failed.log for details

 2024/04/03 18:45:01 akmodsbuild: + '[' -e /etc/pki/akmods/certs/public_key.der ']'
2024/04/03 18:45:01 akmodsbuild: + /usr/lib/rpm/brp-kmodsign /etc/pki/akmods/private/private_key.priv /etc/pki/akmods/certs/public_key.der /tmp/akmodsbuild.4Iqzwny7//BUILDROOT/evdi-kmod-1.14.2-1.fc39.x86_64/lib/modules/6.7.11-200.fc39.x86_64/extra/evdi/ /usr/src/kernels/6.7.11-200.fc39.x86_64
2024/04/03 18:45:01 akmodsbuild: At main.c:170:
2024/04/03 18:45:01 akmodsbuild: - SSL error:1E08010C:DECODER routines::unsupported: crypto/encode_decode/decoder_lib.c:102
2024/04/03 18:45:01 akmodsbuild: sign-file: /etc/pki/akmods/private/private_key.priv
2024/04/03 18:45:01 akmodsbuild: /usr/lib/rpm/brp-kmodsign: line 40: warning: command substitution: ignored null byte in input
2024/04/03 18:45:01 akmodsbuild: brp-kmodsign: modules are unsigned!
2024/04/03 18:45:01 akmodsbuild: error: Bad exit status from /var/tmp/rpm-tmp.ifMChb (%install)
2024/04/03 18:45:01 akmodsbuild: 
2024/04/03 18:45:01 akmodsbuild: RPM build errors:
2024/04/03 18:45:01 akmodsbuild:     Bad exit status from /var/tmp/rpm-tmp.ifMChb (%install)
2024/04/03 18:45:01 akmodsbuild: 
2024/04/03 18:45:01 akmods: Building rpms failed; see /var/cache/akmods/evdi/1.14.2-1-for-6.7.11-200.fc39.x86_64.failed.log for details

wait, since I'm running it on my fork... my key needs to be different right?

Kyle GospoOP•8mo ago

correct best to continue in your PR

Waffleophagus•8mo ago

right, I just can't kick off the builds there, was trying to remove from having to poke you every time I made a change. THAT SAID I'm starting to actually get hopeful That said, whenever you get a minute, I think we... might be good? 🤞🏻 oh uh... I don't think I enabled 38 images on the copr?

error: Packages not found: framework_laptop-*.fc38.x86_64

error: Packages not found: framework_laptop-*.fc38.x86_64

Kyle GospoOP•8mo ago

did any 39s build?

Waffleophagus•8mo ago

error: Packages not found: framework_laptop-*.fc39.x86_64

error: Packages not found: framework_laptop-*.fc39.x86_64

ok, well that's just odd Oh uh, ok, I think I see what happened here. I think I targeted the wrong platform in my COPR... Targeted the right ones (and included 38 while I was at it) ok, so I saw two issues, the first was the fact that I wasn't building to x86_64, the other is framework_laptop isn't a thing, but framework-laptop is, so I thinnkkk I solved that by trying to find all instances of the former and making them the latter? The slightly revised version of the COPR is building now. ok, COPR built Just to learn a bit, Warning: figure out the default kernel [WARNING] that's normal right?

Kyle GospoOP•8mo ago

yep you're good

Waffleophagus•8mo ago

error: Packages not found: framework_laptop-*.fc39.x86_64 grrrr.... I don't know what is causing it to be an underscore. It should be a dash now the file is definitively a dash ok, question, the package its looking for, where is that defined in your akmod setup? Cause I realized that the actual kmod written is named framework_laptop.c and it refers to itself as underscore in a few places. I'm wondering if I should actually default to the underscore. That said I did find 1 spot and it should be good to go, but figure I'd anticipate the issue again @Kyle Gospo just lemme know when you get a chance to run it. Or do you think it'd make sense for me to change the signing key to something of my own, iterate on it, and then change it back for the PR so I don't poke you? Also, ideas on the above question? Again, trying to make it to where I just... give you a PR that's ready and not hassle you with every change 😅 Ugh, its still giving

error: Packages not found: framework_laptop-*.fc39.x86_64

error: Packages not found: framework_laptop-*.fc39.x86_64

and I don't know why

Gaming

Programming

since that copies something to /tmp to