17:00:06 #startmeeting FESCO (2022-11-15) 17:00:06 Meeting started Tue Nov 15 17:00:06 2022 UTC. 17:00:06 This meeting is logged and archived in a public location. 17:00:06 The chair is zbyszek. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:06 The meeting name has been set to 'fesco_(2022-11-15)' 17:00:06 #meetingname fesco 17:00:06 The meeting name has been set to 'fesco' 17:00:06 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, music, mhayden, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 17:00:06 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok music nirik sgallagh zbyszek 17:00:09 #topic init process 17:00:12 .hi 17:00:13 mhayden: mhayden 'Major Hayden' 17:00:14 .hello2 17:00:16 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 17:00:29 👋🏻 17:00:29 morning 17:00:37 .hello ngompa 17:00:38 .hi 17:00:38 Eighth_Doctor: ngompa 'Neal Gompa' 17:00:41 sgallagh: sgallagh 'Stephen Gallagher' 17:00:54 So we have quorum. 17:01:14 Let's dive right in. 17:01:18 #topic #2883 Change: Ostree Native Container (Phase 2, stable) 17:01:18 .fesco 2883 17:01:19 zbyszek: Issue #2883: Change: Ostree Native Container (Phase 2, stable) - fesco - Pagure.io - https://pagure.io/fesco/issue/2883 17:02:09 I'm in favor of this, although I am not sure I understand all the implications. :) 17:02:28 Same for me. 17:02:42 Also, same 17:03:49 there's a *lot* in that change proposal 17:04:06 I suggest we approve it and reserve the right to veto anything that turns out to cause a lot of problems. 17:04:27 * mhayden would love to see a visual (diagram?) or two 🤞🏻 17:04:35 (For the frame pointer proposal, can we delay that by one more week, we're trying to determine why Python slows down so much more than the rest of the benchmarks) 17:05:57 DaanDeMeyer[m]: sure, we can do that. 17:06:25 .hello churchyard 17:06:26 mhroncok: churchyard 'Miro Hrončok' 17:06:46 sorry, package delivery exactly when the meeting was about to start 17:07:10 so, yeah, I guess +1 and if anything blows up that we didn't understand would blow up, revisit it... ? 17:07:28 +1 17:07:50 0, wasn't able to dedicate my time looking into this yet, sorry 17:08:57 0, I'd need to re-read the proposal before voting, sorry. 17:09:33 0, read it but would like to see some kind of visual representation to help me understand it better 17:10:30 Hmm, I'd prefer to instead ask people to vote in the ticket. 17:10:44 And if there aren't enough votes, we vote on the next meeting. 17:10:49 👍🏻 17:11:48 OK, any other votes? 17:12:00 Oh, wait, it's 5 already. 17:12:15 Eighth_Doctor didn't vote. 17:12:27 0 17:12:36 With +2,4,0 it wouldn't pass. 17:12:40 * nirik has no objection to waiting more if we have questions. 17:12:49 That's fine with me also 17:12:57 I simply don't understand the implications of this proposal 17:12:59 #agreed Everybody is to re-read the prosal and vote in the ticket. 17:13:20 #info If that fails, we'll vote next week in the meeting. 17:13:32 #topic #2887 move IMA RPM file-signature change to F38? 17:13:32 .fesco 2887 17:13:33 zbyszek: Issue #2887: move IMA RPM file-signature change to F38? - fesco - Pagure.io - https://pagure.io/fesco/issue/2887 17:13:37 and one of them about chaining everything on top of FCOS concerns me because I don't understand the implications of what layered products wanting to remove stuff does 17:14:14 Eighth_Doctor: that kind of question is more suited for the mailing list… Maybe it's time to revive the thread. 17:14:26 probably 17:14:56 So… for IMA, the big question is whether something user-visible happened. 17:15:07 I'm not sure what to do here. It looks like the ima signing might not be working, but I don't understand it well enough to know whats broken. ;( 17:15:31 If all the parts that were done are in the backends and tooling and there's no user-visible change, then we can (and must) just mark the change as not-implemented. 17:15:40 I.e. move it to F38 I guess. 17:15:54 yeah, seems so... 17:15:58 so we aren't doing IMA signing atm? 17:16:13 And in the future, there's a lesson for us: if the change is described so sparsely that we can't even say if it happened, then we need to reject the change. 17:16:39 yeah 17:16:47 well, I think we are, but it's somehow not getting out to the end rpms in the composes... 17:16:54 The "how to test" section should really have a section that allows us or bcotton_ to verify 17:17:04 .hello music 17:17:05 music[m]: music 'Benjamin Beasley' 17:17:06 I am not sure if thats because koji isn't doing the right thing, or sigul or what 17:17:21 I guess it makes sense to defer to f38 17:17:23 "You can verify that a signature has been put in place by looking at the extended attribute by running: getfattr -d -m security.ima /usr/bin/bash (change /usr/bin/bash with the file to check). " 17:17:31 by virtue of the fact it gives time to fix it 17:17:36 The rpms are rewritten during signing… Maybe the signatures get lost then? 17:18:04 mhroncok: I tried that. 17:18:07 koji uses detached signatures and writes out signed copies as requested. 17:18:26 so, might be that part thats not right, or might be the detached sigs or... 17:19:15 proposal: Change doesn't seem to have been implemented. It can be resubmitted for F38 with more details. 17:19:23 +1 17:19:56 +1 17:20:14 +1 17:20:25 +1 17:20:35 Eighth_Doctor? 17:20:39 But the change owners say it is implemented 17:20:48 surely they know somethign we don't 17:21:08 +1 17:21:23 well, I don't know that we should talk about implementing... rather working. It was implemented, but it's clearly not working right. 17:21:55 +1 17:21:56 sigh 17:22:15 #agreed Change doesn't seem to have been implemented. It can be resubmitted for F38 with more details. 17:22:19 #undo 17:22:19 Removing item from minutes: AGREED by zbyszek at 17:22:15 : Change doesn't seem to have been implemented. It can be resubmitted for F38 with more details. 17:22:34 #agreed Change doesn't seem to have been implemented. It can be resubmitted for F38 with more details (+6, 0, 0) 17:22:43 #topic #2817 Change proposal: Add -fno-omit-frame-pointer to default compilation flags 17:22:46 https://pagure.io/fesco/issue/2817 17:23:08 I think we're pretty much set to reject this one 17:23:10 So… DaanDeMeyer[m] asked for this to be moved to next week. 17:23:55 this whole thing makes me wish we could do OBS-style automatic alternate publish targets with tweaks like this 17:24:11 FWIW, I'm thinking that we might want to enable this for F38 with the proviso that if it turns out to cause a noticable overhead, we'll discuss reverting for F39. 17:24:17 but then we also need tracked automatic rebuilding, which we also don't have... and arrgh 17:24:57 See also https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/6TQYCHMX4FZLF27U5BCEC7IFV6XNBKJP/ 17:26:15 But I haven't read all the latest comments, so if nobody objects, I'd skip the discussion today. 17:26:24 #info https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/6TQYCHMX4FZLF27U5BCEC7IFV6XNBKJP/ 17:26:25 here's the problem I have: are we deciding to make a Change that guarantees a 2%~10% perf loss on the possibility someone might work on the codebases to restore that? 17:27:01 because unless someone is outright committing to working to restore the performance lost, I don't think this is a good idea :/ 17:27:15 * nirik nods. 17:27:16 but I am willing to be convinced otherwise 17:27:47 Eighth_Doctor: various features that make debugging and introspection easier have a cost: minidebuginfo, -debug packages, package notes, using -O2 instead of -O3, etc. 17:28:09 we use -O2 instead of -O3 because -O3 breaks packages too much 17:28:20 otherwise, I think we would use it 17:28:42 we already don't do super-well in benchmarks, I'd rather not make it worse :( 17:28:58 and there's also downstream implications 17:29:22 Eighth_Doctor: I'm willing to accept the argument that this makes benchmarking significantly more profitable and can result in much bigger savings. 17:29:22 this doesn't really do a ton of good if prominent downstreams rebuild Fedora without it because the performance lost is too much to bear 17:29:39 Anyway… OK to move to the next topic? 17:29:53 +1 17:30:09 Everyone's favorite! 17:30:10 #topic Next week's chair 17:30:22 I don’t know what to make of the Python upstream recommendation. As I said in the ticket, for me 1% is probably worth it, 2-3% is hard because it is obviously worth it to some and obviously unacceptable to others depending on background and priorities. I don’t think I could consider voting for it without understanding why Python is so much worse than 2-3% because I’m afraid there are other applications or ecosystems that could 17:30:22 be similarly affected. 17:30:40 Next week is Thanksgiving week here in the USA 🦃 17:30:43 I'm out next week, as I expect many others in the US will 17:30:47 * nirik will not be here next week. 17:31:19 dcantrell, Eighth_Doctor are US-based too. 17:31:25 zbyszek: I'm willing to accept it if I thought it would be used 17:31:25 the problem is: I don't think it will 17:31:43 lol 17:31:44 laggodoom 17:31:52 but yes Thanksgiving next week :D 17:32:06 (wifi in the office is half-broken, hence this happening) 17:32:29 #info Next week is Thanksgiving in US. Next meeting will be in two weeks. 17:32:38 OK, volunteers to chair in two weeks? 17:32:38 yay! 17:32:39 DST? 17:33:07 So… we agreen on 17:00 UTC. 17:33:11 *agreed 17:33:25 it apparently means lunchtime here 17:33:32 I'm fine with moving the meeting, if people want to. 17:33:39 * Eighth_Doctor shrugs 17:33:42 no strong feelings 17:34:06 this is actually better for me 17:34:36 I think people in Europe prefer that too, it's always nicer not to end at 20:00. 17:34:37 This is trivially worse for me but still OK. 17:34:39 I just eat lunch later now I guess 17:34:54 or if I'm lucky enough to get food before this 17:35:08 then I can eat and watch text scroll by 17:35:12 #info We will keep the meeting time at 17:00 UTC for now, which means 18:00 in Europe. 17:35:21 So… volunteers for next chair? 17:35:34 "in Europe" might be confusing for some 17:35:51 #undo 17:35:51 Removing item from minutes: INFO by zbyszek at 17:35:12 : We will keep the meeting time at 17:00 UTC for now, which means 18:00 in Europe. 17:35:55 #info We will keep the meeting time at 17:00 UTC for now, which means 18:00 in EU. 17:35:57 * mhroncok checks the calendar 17:35:57 I'll take it in two weeks 17:36:32 #action sgallagh will chair the next meeting (Nov 29th, 17:00 UTC) 17:36:38 #topic Open Floor 17:36:43 sgallagh: thanks! 17:37:03 zbyszek: there are three timezones in the EU (don't undo it, it's fine) 17:37:04 No problem 17:37:34 mhroncok: Hmm, I forgot about Ireland. 17:37:40 Oh, and Greece and so on. 17:37:47 OK, that was stupid. 17:38:28 OK, if nobody has nothing, I'll close in a minute. 17:38:57 zbyszek++ 17:38:57 mhroncok: Karma for zbyszek changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:39:14 See y'all in two weeks. 17:39:15 #endmeeting