16:00:42 #startmeeting fpc 16:00:42 Meeting started Thu Mar 17 16:00:42 2022 UTC. 16:00:42 This meeting is logged and archived in a public location. 16:00:42 The chair is geppetto. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:42 The meeting name has been set to 'fpc' 16:00:42 #meetingname fpc 16:00:42 The meeting name has been set to 'fpc' 16:00:42 #topic Roll Call 16:01:01 #chair tibbs 16:01:01 Current chairs: geppetto tibbs 16:01:06 .hi 16:01:10 carlwgeorge: carlwgeorge 'Carl George' 16:01:18 Not sure what's happening in the other channel. 16:01:20 .hi 16:01:21 mhroncok: Sorry, but user 'mhroncok' does not exist 16:01:24 DST? 16:01:26 #chair mhroncok 16:01:26 Current chairs: geppetto mhroncok tibbs 16:01:30 .hello churchyard 16:01:31 mhroncok: churchyard 'Miro Hrončok' 16:01:33 .hello ngompa 16:01:34 Eighth_Doctor: ngompa 'Neal Gompa' 16:01:36 Yeah, probably a time zone mess thing. 16:01:42 tibbs Meeting tied to UTC instead of EST … so collisions 16:01:48 #chair Eighth_Doctor 16:01:48 Current chairs: Eighth_Doctor geppetto mhroncok tibbs 16:01:57 * Eighth_Doctor needs to check to see if Fedora Cloud is tied to US/Eastern or not 16:01:58 it's supposed to be 16:01:58 Fortunately there is now at least a reasonable chance of the time change going away in the US soon. 16:02:08 yeah 16:02:15 holy crap I jumped for joy when I saw that 16:02:23 permanent DST would make me so happy 16:02:24 yeh, I've heard that for years … but seems more likely now 16:02:38 it got unanimous support by the Senate 16:02:41 that literally never happens 16:03:10 yeh, but still waiting for congress to vote it down because 40% believe the earth is flat or something 16:03:24 still has to pass the house and the president's desk 16:03:30 #chair carlwgeorge 16:03:30 Current chairs: Eighth_Doctor carlwgeorge geppetto mhroncok tibbs 16:03:41 and even then, it wouldn't take effect till 2023 iirc 16:04:14 I don't care, hope springs anew! 16:05:11 the bill was submitted by a member of each party 16:05:13 #topic Schedule 16:05:16 #link https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/ADMQKPELLRWMEO2QNAY5F7BOFEB4W7OP/ 16:05:38 that email is long 16:05:41 You may notice this is last weeks schedule … AFAIK it's the same. I am very prepared 16:05:42 are we actually looking at all that? 16:05:50 looking, yes 16:05:54 dealing with, no 16:05:57 groceries arrived, will be missing for a while 16:06:02 lol 16:06:08 :D 16:07:03 Bottom line is that we do need to address all of that in some form, even if it's just pinging or closing old stuff. 16:07:27 I think that SELinux policy PR has been there for actually years 16:07:36 But most of it doesn't need doing in an actual meeting. Probably very little of what we need to do actually needs a meeting. 16:07:47 Talking of … 16:07:49 #topic #1159 Ban use of %configure in %prep 16:07:49 .fpc 1159 16:07:49 https://pagure.io/packaging-committee/issue/1159 16:07:50 geppetto: Issue #1159: Ban use of %configure in %prep - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/1159 16:08:10 That selinux ticket is one of those things that someone worked on but never seemed to want to actually make acceptable for a packaging guideline. 16:08:16 Everyone agrees this is bad … why haven't we closed it? 16:08:45 Do we just need text from someone? 16:08:47 1159 sort of turned into a bigger thing that I do occasionally work on. 16:09:22 The idea was to just make an autotools page like meson or cmake and then put this there. 16:09:25 We probably need a status of "everyone agrees this is the right direction, but someone needs a few hours to write some policy text" 16:09:41 I don't mind abusing needinfo, but eh 16:09:45 Indeed, that's the state this ticket is in. 16:09:45 yeah, maybe a milestone or tag for it? 16:09:51 err priority or tag 16:10:03 Can make new tags easily. As long as it drops out of meeting. 16:10:13 The problem, of course, is that there are loads of tickets like that. 16:10:38 I guess https://pagure.io/packaging-committee/pull-request/1163 is in that state too? 16:10:49 * geppetto nods 16:11:02 If pagure would ever load.... 16:11:17 yep 16:11:25 Yes, the issue was that it's a good idea but the PR as is would lead to some weird confusion. 16:11:36 #topic Open Floor 16:11:49 I had hope it would be revised, but it looks like we will need to revise it. 16:11:51 Well those were the two main things I wanted to talk about, so … 16:11:53 Something else for the list. 16:11:56 * geppetto nods 16:12:35 Anything else anyone wants to talk about? 16:13:07 https://pagure.io/packaging-committee/pull-request/1157 16:13:31 I'm still iffy about that one 16:13:44 I don't have a problem with it. 16:13:52 But wasn't the part you didn't like removed? 16:15:11 it was 16:16:25 Yeh, I thin kit's fixed now 16:16:39 I'm +1 16:16:44 Bottom line is that there's no reason to number patches in most cases. Sources is maybe more complicated. 16:17:29 But our examples should generally just show the simple case unless it doesn't work or it conflicts with what packagers will most often need to do. 16:17:44 amen 16:17:49 agreed 16:18:18 could we include a note about the numbering and when one might need to do it? 16:18:19 note that this does not imply "you should not number your sources and patches" 16:18:34 I'r rather not block the examples change on that 16:18:37 but we should 16:18:42 sure, can be separate 16:18:42 yeh 16:19:00 I'm fine with anyone doing other improvemnets I'll happily +1 … just don't block this one 16:19:09 * carlwgeorge nods 16:19:43 Ok, any objections then before I click the merge button? 16:20:15 * carlwgeorge is curious what Eighth_Doctor was iffy about 16:20:39 s/iffy/still iffy/ 16:20:47 we have enough cases where having the numbers is useful by default that I'm not sure it's a good idea to change our guidance 16:21:30 We aren't changing the guidance, just making the simple examples simpler 16:21:54 yeah this pr isn't guidance, the actual guidance can be "use your best judgement" 16:22:09 okay 16:22:32 Ok, I clicked the button 16:22:36 Our examples also use autosetup, which in general makes numbering patches pointless, doesn't it? 16:22:39 We did something ;) 16:22:47 yipee 16:22:47 tibbs: for patches, yes, for sources no 16:22:50 yeah! 16:23:22 my guess is the majority of spec files are single source anyways 16:23:31 Yes, I'm explicitly indicating patches here. 16:24:13 argh, DST. hey guys 16:25:04 #chair decathorpe 16:25:04 Current chairs: Eighth_Doctor carlwgeorge decathorpe geppetto mhroncok tibbs 16:25:19 hello Fabio Valentini :D 16:25:27 decathorpe: yeh, same next week … but then we change it again :) 16:25:37 wonderful 16:26:00 but hey, we might be finally adopting DST year round in the US 16:26:14 so that'll simplify things and then it's just on the EU to fix their timezone mess :D 16:26:28 yup ... 16:27:13 well, if Us will lead the way... the EU can always wait and observe 16:27:36 we will measure how many daylight have you saved 16:27:43 and maybe do the same :D 16:28:00 or you can sell us some of it, if you save too much 16:28:37 DST really is a misleading term ... you don't save anything, you're just stealing from the morning and giving it to the evening 16:28:41 (actually, it seems that mos tof the EU countries want to cancel timezone switching, but there is no agreement on whether it should be dst-on or dst-off) 16:28:54 ultimate late stage capitalism … we are now selling daylight :-o 16:29:03 daylight stealing time 16:29:11 perfect. 16:29:32 I sleep til 10 AM. I like DST 16:29:38 i prefer if we had even more of it 16:29:58 (sounds like the meeting is over?) 16:30:15 sounds like it. perfect timing for my arrival 16:30:32 Probably … also maybe have to burn mhroncok at the stake 16:30:56 * mhroncok runs 16:32:22 Ok, see you all next week 16:32:28 #endmeeting