19:06 <dustymabe> marmijo[m]: any luck figuring out how to pin the kernel just for ppc64le ?

19:06 <dustymabe> might be good to iron that out and get testing on the new kernel (for the other arches) before our next week releases

19:07 <marmijo[m]> I dont think we support pinning packages for only one arch. I couldnt get it to work locally.

19:07 <marmijo[m]> https://github.com/coreos/fedora-coreos-tracker/issues/1489#issuecomment-1664017086

19:08 <dustymabe> marmijo[m]: hmm. somehow I missed that notification

19:15 <dustymabe> marmijo[m]: responded

19:15 <marmijo[m]> dustymabe: thanks!

20:11 <dustymabe> marmijo[m]: thanks for working on https://github.com/coreos/fedora-coreos-config/pull/2537

20:12 <marmijo[m]> dustymabe: of course, thank you for reviewing it!

20:12 <dustymabe> one thing I don't know is if there are pieces later in the process that might hiccup because of this (think the actual pipeline builds, or bump-lockfile, or the release job, etc), but I know there is only one way to find out.

20:12 <dustymabe> :)

20:12 <dustymabe> marmijo[m]: if the openstack tests have been succeeding recently then maybe we can drop the pipeline hack to snooze it

20:14 <marmijo[m]> Sounds good, we'll just deal with it as it happens :)

20:14 <marmijo[m]> re: openstack. They have been working, I'll drop the snooze because it's expired anyway. I'm also trying to look into https://github.com/coreos/coreos-assembler/issues/3550 as well

20:15 <dustymabe> for ^^ I would focus less on why it's happening (I think it's part of issues with vexxhost) and more on having GC just take care of it

20:17 <marmijo[m]> dustymabe: Indeed. I've spent some time trying to understand ore so I can work on the GC