16:00:06 #startmeeting fpc 16:00:06 Meeting started Thu Sep 30 16:00:06 2021 UTC. 16:00:06 This meeting is logged and archived in a public location. 16:00:06 The chair is geppetto. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:06 The meeting name has been set to 'fpc' 16:00:06 #meetingname fpc 16:00:06 #topic Roll Call 16:00:06 The meeting name has been set to 'fpc' 16:00:54 .hi 16:00:55 carlwgeorge: carlwgeorge 'Carl George' 16:01:06 .hello2 16:01:07 decathorpe: decathorpe 'Fabio Valentini' 16:01:53 #chair carlwgeorge 16:01:53 Current chairs: carlwgeorge geppetto 16:01:56 #chair decathorpe 16:01:56 Current chairs: carlwgeorge decathorpe geppetto 16:09:06 #topic Open Floor 16:09:12 Anyone need to talk about anything? 16:09:27 I commented on https://pagure.io/packaging-committee/issue/1099 this morning 16:10:16 tibbs did too 16:10:34 I'm fine with leaving it or changing it or removing it 16:10:42 I haven't followed that ticket yet, I'll catch up on it later 16:11:18 Yeh, I don't think it's a big deal … I know when legal wanted the license file shipped people were worried about the sizes of images etc. 16:11:32 but I don't think that's really been our problem there 16:12:03 Anyway … anything else we should get a ping on before I close for the week? 16:12:31 Damn, sorrty. 16:12:37 I don't think so. 16:12:39 tibbs: no problem 16:12:45 I'm sitting here doing other things and didn't notice the time. 16:13:12 I tried to work on open PRs and any issues which were recent and got things a bit more under control. 16:13:47 There are a number of PRs tagged as meeting, but those won't show up in a ticket report, which is mildly annoying. 16:14:47 tibbs: They should show up in the PR report: https://pagure.io/packaging-committee/pull-requests?tags=meeting 16:15:09 Huh. 16:15:22 OK, well that's good. 16:15:41 I'm not sure we actually talked about some of them, though. 16:17:10 And at some point we really need to talk about the build constraints thing, because that's just a mess. 16:20:17 yeah, I'd rather not document something that's broken and was not fixed after receiving negative feedback. 16:20:43 I believe Michel is coming back from paternity leave soon 16:20:50 so he can look at this when he's back 16:20:55 #chair Eighth_Doctor 16:20:55 Current chairs: Eighth_Doctor carlwgeorge decathorpe geppetto 16:21:02 #chair tibbs 16:21:02 Current chairs: Eighth_Doctor carlwgeorge decathorpe geppetto tibbs 16:21:04 👋 16:22:00 Technically that's 5 … if we want to do anything we need quorum for 16:23:21 Well, I wouldn't mind getting opinions on the build constraints thing. 16:23:38 Technically that's https://pagure.io/packaging-committee/pull-request/1094 but the issue is bigger than the PR. 16:23:43 This seems like a trivial change: https://pagure.io/packaging-committee/pull-request/1064 16:24:30 I didn't just merge 1064 because honestly I've forgotten most of the context around the hardened build stuff. 16:24:56 It does seem OK to me. 16:25:18 But an ack from someone who remembers more about it would be good. 16:27:17 Not sure who that would be :) 16:28:33 I remember most of it :) 16:28:36 The change looks good to me, but the line breaks look weird 16:28:56 yeah 16:29:22 It's an attempt to use semantic line breaks as requested, but.... it's not. 16:29:23 other than that ... 16:29:50 I can merge and then re-flow since that's most of what I've been doing lately anyway. 16:30:08 that would be great 16:30:24 OK, I'll just do that. 16:30:30 Cool 16:30:42 Anything else? 16:30:59 If not I'll close early and give you all 30 mins. back 16:31:13 I mean, 1094 unless we really don't want to talk about it. 16:31:32 I had a look at it 16:31:39 let's not and wait for salimma to get back first 16:31:46 It seems like it needs someone to talk to upstream a bunch and come up with a new patch 16:31:53 so ¯\_(ツ)_/¯ 16:32:14 Is there anything we can do? 16:32:25 I'm more annoyed at how unresponsive upstream is until someone does something to make them upset 16:32:30 We can remove the macros from redhat-rpm-config 16:32:32 being proactive is almost not worth it 16:33:04 tibbs: Are there any downsides right now? 16:33:07 Panu raised objections well before this stuff was pushed. 16:33:19 I don't see how that's too late or unresponsive. 16:33:22 Can we just add a comment that says "this is a huge hack and upstream wants it down differently"? 16:33:32 And then they went and rewrote the macros and didn't even give him time to comment. 16:34:03 I agree that there have been issues with responsiveness in the past, but I just don't see that in this specific instance. 16:34:57 I tried to get a clear statement from Panu as to what he would prefer that we do, just so we can take it into consideration. 16:35:02 But I don't think we really got that. 16:35:25 yeh, hence the need to talk to upstream a bunch more 16:35:36 And I don't think I have the ability to personally implement what he outlined. 16:36:21 And the last statement he made seemed to me like "I wish it could have been done the right way" instead of "please remove it while we work up something that's more acceptable". 16:37:03 Which just doesn't help me make any kind of decision about what we should actually do. 16:37:06 my understanding is that that the macro would need to be a "simple" lua script that set _smp_build_ncpus globally for it to be generally useful 16:37:37 and right now it just evaluates to "-j N" with N depending on the argument and available memory 16:39:43 Looking at it more closely, I can say this: %limit_build is not intrusive and is limited in scope. The underlying situation is unfortunate but really the macro is kind of a small thing which doesn't hurt anything. 16:40:24 yeah, but it's just not all all like the feature that was proposed and approved by FESCo. 16:40:25 If we one day implemented what Panu wanted, which is some way to scale RPM's idea of the CPU count, then that wouldn't really interfere with this macro, and this macro wouldn't interfere with that unless we wanted to use the name. 16:41:02 To be fair I did not pay attention to that FESCo process. (There are a lot of things that move through the feature process.) 16:41:26 so, I mean, FPC can document this macro, but we shouldn't pretend that this is what was originally envisioned 16:41:39 Is FESCo is happy with how the the implementation matches the feature proposal? 16:42:45 speaking for myself, no. it's just completely different in both usage and implementation. 16:45:05 Well if FESCo wouldn't be satisfied then that's a whole different conversation, I think. 16:45:28 Just shows how badly this was all done, even though it's not really a big thing. 16:45:45 Let me take a look and see if I can figure out what an implementation would look like. 16:45:53 But maybe FESCo should have its own conversation. 16:46:58 I think it was this ticket: https://pagure.io/fesco/issue/2642 16:47:34 should we add a comment there? 16:47:55 #action tibbs Will look at #pr-1094 and see if he can find out what an upstream happy implementation would look like. 16:48:10 decathorpe: You seem like the perfect person to do that 16:49:04 yeah, given that I processed that ticket :) 16:49:29 Also that you are in both groups :) 16:50:07 that also applies to two others here ;) 16:51:54 fair 16:52:26 geppetto: https://pagure.io/fesco/issue/2642#comment-754095 16:53:16 Seems like an easy enough question 16:54:27 I hope so 16:54:46 as I seem to have problems communicating without upsetting people today shrug 16:55:28 eh, sometimes we have those days … and sometimes other people are heving them with us 16:56:02 Anyway … 5 mins. left so I'm really getting ready to close now ;) 16:58:58 #endmeeting