misuto has quit [Remote host closed the connection]
misuto has joined #fedora-coreos
misuto has quit [Ping timeout: 246 seconds]
BazilObolensky[m has joined #fedora-coreos
misuto has joined #fedora-coreos
<BazilObolensky[m>
Hi All! I asked like a month ago how to sign my coreos-like system with gpg. I think i finally managed to do it but now rpm-ostree status prints me "Can't check signature: public key not found". I suppose i need to add my public.key somewhere. Can you give me a tip where and how i should put it? Huge thanks in advance!
<travier[m]>
Bazil Obolensky: You specify it when you add the remote with ostree
jpn has quit [Ping timeout: 250 seconds]
jpn has joined #fedora-coreos
ccha has quit [Ping timeout: 265 seconds]
jpn has quit [Ping timeout: 240 seconds]
jpn has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
<nalind>
baude: one of the dependencies, specifically github.com/idubinskiy/schematyper's generator.go, imports a package named "gopkg.in/alecthomas/kingpin.v2", but the go.mod it gets when it downloads it says the module is actually named github.com/alecthomas/kingpin/v2
<baude>
i get that part, what i dont understand is why this is happening with make schema because i havent changed anything
<baude>
im on aarch64 linux ... wonder if that is a factor with something like buildtags or some such, /me keeps poking it with a stick
vgoyal has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
<nalind>
baude: fwiw, happens for me on amd64
<baude>
ok, so im not weird ... or at least, we are both weird
<dustymabe>
weirdclub++
<baude>
dustymabe: you see it too ?
<dustymabe>
baude: not yet. just signed on after dropping kids at school. I'll check here shortly
<baude>
when i run cmd-artifact-disk on apple silicon, i am seeing a failure when qemu-system-aarch64 is called, likely in how it is called ... where can anyone comment on where that command is being generated?
<dustymabe>
aaradhak[m]: if there is something in there that looks like it could be the problem you can mention it when you open the bug
<dustymabe>
alternatively you can just say that you looked through the commits and nothing stood out, but you aren't a systemd expert and could use some help
<baude>
is guestfish calling that?
<HristoMarinov[m]>
fifofonix: 👍️
<dustymabe>
baude: want to fpaste some log output ?
<aaradhak[m]>
dustymabe: ok, the keyword for the issue we see is TIMEOUT, trying to find from the console logs if there is any other specific keyword.
<dustymabe>
aaradhak[m]: that's just a kola error message - you won't find that anywhere in systemd
<dustymabe>
you have to look at the journal/console logs for the test to try to figure out what systemd is doing differently
<fifofonix[m]>
dustymabe: finally got to your slides because i missed that portion of the presentation! Countme numbers very interesting. Positively surprised at ~25% aarch64.
<aaradhak[m]>
dustymabe: alright, will browse the console/journal log for systemd related stuff
saschagrunert has quit [Remote host closed the connection]
<dustymabe>
aaradhak[m]: you might need to compare the console/journal with logs from previous successful runs to see if there are differences
<dustymabe>
but if you don't find anything that's OK
<dustymabe>
it could be enough to post a "good" run (with the old systemd) and a "bad" run's logs in the BZ when you open it
<aaradhak[m]>
dustymabe: ok sure, i will work on the comparison and get some details