dustymabe changed the topic of #fedora-coreos to: Fedora CoreOS :: Find out more at https://getfedora.org/coreos/ :: Logs at https://libera.irclog.whitequark.org/fedora-coreos
vgoyal has quit [Quit: Leaving]
ccha1 has quit [Ping timeout: 264 seconds]
ccha1 has joined #fedora-coreos
gursewak has quit [Ping timeout: 250 seconds]
gursewak has joined #fedora-coreos
jlebon has quit [Quit: leaving]
plundra has quit [Remote host closed the connection]
plundra has joined #fedora-coreos
gursewak has quit [Ping timeout: 250 seconds]
plarsen has quit [Quit: NullPointerException!]
paragan has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 276 seconds]
daMaestro has quit [Quit: Leaving]
samuelbernardo has quit [Ping timeout: 255 seconds]
samuelbernardo has joined #fedora-coreos
saschagrunert has joined #fedora-coreos
jcajka has joined #fedora-coreos
Betal has quit [Quit: WeeChat 3.8]
klaas has quit [Read error: Connection reset by peer]
klaas has joined #fedora-coreos
sayan has quit [Ping timeout: 246 seconds]
sayan has joined #fedora-coreos
jpn has joined #fedora-coreos
apiaseck has joined #fedora-coreos
Turnikov has joined #fedora-coreos
vgoyal has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 264 seconds]
ravanelli has joined #fedora-coreos
gursewak has joined #fedora-coreos
jlebon has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
nalind has joined #fedora-coreos
ravanelli has joined #fedora-coreos
Turnikov has quit [Ping timeout: 250 seconds]
inflatador_ has quit [Changing host]
inflatador_ has joined #fedora-coreos
Turnikov has joined #fedora-coreos
mheon has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
plarsen has joined #fedora-coreos
inflatador_ is now known as inflatador
Turnikov has quit [Ping timeout: 250 seconds]
<dustymabe> jlebon: ravanelli: travier[m]: bgilbert: jmarrero: anyone want to run the community meeting today?
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 276 seconds]
<jlebon> dustymabe: i might be afk in the afternoon, so better not me. i think ravanelli would do great though :)
jpn has joined #fedora-coreos
<ravanelli> I can try to ;)
<jlebon> ravanelli++
<zodbot> jlebon: Karma for ravanelli changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any
<dustymabe> ravanelli: reminder the meeting time is set in UTC
<dustymabe> which means for some people it will be at a different local time this week than it was last week
<dustymabe> 16:30 UTC
<ravanelli> dustymabe: 👍
<ravanelli> dustymabe: It will happen in around 1 hour
<travier[m]> yes
jcajka has quit [Quit: Leaving]
jcajka has joined #fedora-coreos
gursewak has quit [Ping timeout: 248 seconds]
<ravanelli> aaradhak anthr76 apiaseck davdunc dustymabe gursewak jaimelm jbrooks jcajka jdoss jlebon jmarrero lorbus miabbott nasirhm ravanelli saqali skunkerk walters
<ravanelli> FCOS community meeting in #fedora-meeting-1
<ravanelli> If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt
<dustymabe> travier[m]: maybe the maintainer is waiting for some statement that this has been tested on silverblue at least: https://src.fedoraproject.org/rpms/openssh/pull-request/45
<travier[m]> dustymabe: haven't had the time to do it yet :/
paragan has quit [Quit: Leaving]
gursewak has joined #fedora-coreos
saschagrunert has quit [Remote host closed the connection]
jcajka has quit [Quit: Leaving]
gursewak has quit [Ping timeout: 246 seconds]
gursewak has joined #fedora-coreos
mnguyen has joined #fedora-coreos
apiaseck has quit [Quit: Leaving]
bgilbert has joined #fedora-coreos
apiaseck has joined #fedora-coreos
gursewak has quit [Quit: Leaving]
apiaseck has quit [Quit: Leaving]
gursewak has joined #fedora-coreos
gursewak has quit [Ping timeout: 276 seconds]
Betal has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
<dustymabe> hey walters - when bootupctl reports that "No components are adoptable." - what does it mean?
<walters> It doesn't recognize your system
<walters> see https://github.com/coreos/bootupd/blob/eba79f3409aaeb9e9d590586fc695d4cb702417b/src/efi.rs#L113 - I'm guessing you're running a system before we were writing the coreos aleph
<dustymabe> see fpaste ^^
<dustymabe> the aleph is there
<walters> Oh yes, that's normal
<walters> Perhaps we should stop printing it without --verbose
<dustymabe> i was trying to peruse docs to understand what the different between --adopt-and-update and --update is
<dustymabe> seems like the point was "to support systems that weren't installed in the first place using bootupd"
<dustymabe> and
jpn has joined #fedora-coreos
<walters> right
<dustymabe> i think the part that went missing on me is whether adoption was needed for my system or not
<dustymabe> so when it said that adoption wasn't possible, i had the question of if my system was able to be udpated or not
<dustymabe> probably some clarity that could be added there
<walters> yep seems issue worthy
<dustymabe> +1
<walters> btw I plan at some point to fold this into bootc as bootc bootloader so e.g. typing bootc upgrade would also show you availability of bootloader updates
<walters> fragmented confusing array of tools in different git repos -> bootc 😄
<dustymabe> might as well have systemd-bootc and be done with it :)
jpn has quit [Ping timeout: 255 seconds]
<walters> bootc is aligned to containers/ - there's no systemd-podman, so there's no systemd-bootc
gursewak has joined #fedora-coreos
vgoyal has quit [Quit: Leaving]
<dustymabe> jlebon: finally filed this issue https://github.com/coreos/fedora-coreos-tracker/issues/1441 - we should probably cancel the rollout that's scheduled for tomorrow morning while we try to figure out what to do
<jlebon> dustymabe: yeah, let's do that :(
<jlebon> dustymabe: want to make a PR or should I?
<jlebon> staged in https://github.com/coreos/fedora-coreos-streams/pull/666 but maybe let's chat first
<dustymabe> jlebon: i'm trying to do a test now to see if the f37 kernel in bodhi testing has the same problem so we can give it some negative karma
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]
bgilbert has quit [Ping timeout: 276 seconds]
jpn has joined #fedora-coreos
jdieter has quit [Remote host closed the connection]
jdieter has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
<dustymabe> jlebon: should we reply to the status email with an update on the rollouts (since it gave dates).
<jlebon> dustymabe: we should, but ideally with dates of the new rollout once we figure that out
piwu1 has joined #fedora-coreos
<dustymabe> jlebon: 6.1.18-200.fc37 kernel works fine
piwu has quit [Ping timeout: 276 seconds]
piwu1 is now known as piwu
<jlebon> dustymabe: on top of f38 next?
<dustymabe> yeah
<dustymabe> the 6.2 kernel in f37 is similarly broken
<jlebon> ack ok, that's good info. so this is in fact independent of f38. so do we want to pin in both testing-devel and next-devel and respin the next release?
<dustymabe> I'm OK with that
<dustymabe> one thing we need to do is reach out to at leat IoT to discuss how this affects them
<dustymabe> least*
<dustymabe> I guess we also need to try to find out what's the earliest starting poing that still boots
vgoyal has joined #fedora-coreos
jpn has joined #fedora-coreos
travisghansen has quit [Read error: Connection reset by peer]
jpn has quit [Ping timeout: 276 seconds]
travisghansen has joined #fedora-coreos
nalind has quit [Quit: bye for now]
piwu has quit [Quit: Ping timeout (120 seconds)]
piwu has joined #fedora-coreos
mheon has quit [Ping timeout: 276 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]
vgoyal has quit [Quit: Leaving]
gursewak has quit [Ping timeout: 250 seconds]
wkawka has quit [Quit: Client closed]
Betal has quit [Ping timeout: 256 seconds]
Betal has joined #fedora-coreos