16:00:03 #startmeeting fpc 16:00:03 Meeting started Thu Aug 27 16:00:03 2020 UTC. 16:00:03 This meeting is logged and archived in a public location. 16:00:03 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:03 The meeting name has been set to 'fpc' 16:00:03 #meetingname fpc 16:00:03 #topic Roll Call 16:00:03 The meeting name has been set to 'fpc' 16:01:07 .hello2 16:01:08 decathorpe: decathorpe 'Fabio Valentini' 16:01:11 #chair decathorpe 16:01:11 Current chairs: decathorpe geppetto 16:01:28 hello geppetto :) 16:01:33 hey 16:01:45 Hey. 16:01:53 #chair tibbs 16:01:53 Current chairs: decathorpe geppetto tibbs 16:02:07 I still have power but didn't get a whole lot of sleep. 16:02:14 .hello2 16:02:15 * geppetto nods 16:02:15 carlwgeorge: carlwgeorge 'None' 16:02:26 Hey, carl 16:02:39 hey 16:02:44 #chair mhroncok 16:02:44 Current chairs: decathorpe geppetto mhroncok tibbs 16:03:04 * limburgher here 16:03:08 #chair limburgher 16:03:08 Current chairs: decathorpe geppetto limburgher mhroncok tibbs 16:03:40 tibbs: Is the uni opening in a normal way? 16:04:17 The university is basically closed. 16:04:18 tibbs: besides not sleeping, you're ok? 16:05:08 But that was more than a precaution; the thing basically missed us completely and all we got was some wind. I'm not close to the coast so the storm surge wasn't a concern (and it was only 70cm anyway). 16:05:39 * geppetto nods 16:06:34 #topic Schedule 16:06:37 #link https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/XNDM5XLLI2A337LEB32REEXLG352PHYE/ 16:07:00 That's a relief. 16:07:22 All of western Louisiana is in very bad shape, though. 7 meters of storm surge in places and > 200kph winds. 16:07:32 Jesus. 16:07:39 So no new tickets/PRs … but we have some from last week … mhroncok asked people to vote on PR's 1011 and 1013, I think we are missing a couple of votes though 16:07:49 Anyone have any questions/concerns about those? 16:08:55 tibbs: Having that in kph is impressive :) 16:10:13 #topic #pr-1011 Python guidelines updates 16:10:13 https://pagure.io/packaging-committee/pull-request/1011 16:10:29 * decathorpe voted on both PRs 16:10:39 decathorpe++ 16:11:23 I didn't read all the details, but I've been looking at the "implementation" / "usage" side of things at they look good, and I trust Miro to write good Guidelines 16:11:46 yeh, that was basically my +1 too 16:12:31 :) 16:12:58 The "Python Extras" bit is the meat of the change. 16:13:25 the commits are spearted and can be reviewed one by one 16:13:36 (this actually fixes bugs in two of my packages, so I like this) 16:13:39 Python Extras indeed is the longest part and deserves the most attention 16:15:41 +1. The Extras stuff is just documenting a change that was already acked through other means. The rest is documenting existing things and cleaning up some stuff. 16:16:21 that was the idea 16:19:13 Ok, that's +5 16:19:20 \o/ 16:19:46 #action Merge pr-1011 Python guidelines updates (+1:5, 0:0, -1:0) 16:19:59 #topic #pr-1013 Document py_reproducible_pyc_path macro 16:19:59 https://pagure.io/packaging-committee/pull-request/1013 16:20:31 Again, everyone but tibbs has already voted 16:20:58 Feel free to have a look though carlwgeorge, and let us know if you see anything 16:21:57 This seems reasonable to me; it's obscure but in the appendix and if you are unlucky enough to hit the problem then it will be nice to have it documented somewhere. 16:22:00 +1 16:23:10 makes sense to me 16:23:20 +1 16:23:28 * mhroncok tried to fix the typo but cannot force push to the fork for some reason :/ 16:23:48 so I push it to master manually and close the PR 16:24:01 #action Merge #pr-1013 Document py_reproducible_pyc_path macro (+1:5, 0:0, -1:0) 16:24:01 WFM :) 16:24:14 mhroncok: git being a git 16:24:19 Yeah, it does need a grammar pass but obviously minor. 16:24:43 #topic #pr-942 Recommend storing changelog entries in separate file. 16:24:44 https://pagure.io/packaging-committee/pull-request/942 16:24:55 Ok, so this is technically new … but it's been around a bit 16:24:56 .hello ngompa 16:24:56 King_InuYasha: ngompa 'Neal Gompa' 16:24:59 sorry I'm late 16:25:01 Hey, neal 16:25:06 work meeting ran over 16:25:29 oh, we're talking about changelogs now, just in time I suppose 16:25:33 Also tried to ping sgallagh but failed. 16:25:52 so ... I don't think PR 942 is a good idea on its own. I'd rather see this integrated with pingou's rpmautospec 16:25:59 yes 16:26:00 Hmm? 16:26:13 in my opinion, this provides no benefits and adds complexity 16:26:41 that 16:26:41 sgallagh: See https://pagure.io/packaging-committee/pull-request/942 … wanted to see your opinion on having changelogs not be in specfiles directly. 16:26:46 Don't we have like three competing implementations at this point? 16:26:46 this is a situation that I deal with fairly regularly in openSUSE, and it's just not apprecibly different from just having the changelog in the main file 16:27:03 it's arguably worse because it's easier to forget to update the changelog 16:27:14 Will look. Eating lunch right now. 16:27:26 decathorpe: Yeh, there are a bunch of things trying to get here … lots of automated rebuilding. 16:27:27 tibbs: yes 16:27:38 tibbs: yeah, but at least the one that was deployed in koji-staging was opt-in and integrated with other workflows (other than rpmdev-bumpspec) 16:27:44 yup 16:27:50 and fixing it for rpmdev-bumpspec won't be hard 16:28:00 just with no staging environment, no way to test 16:28:31 King_InuYasha: Does OBS do anything we could borrow for auto rebuilding etc. 16:28:54 it has a spec parser and resolver that identifies the dep chains, sorts them, and rebuilds them correctly 16:29:12 * decathorpe shivers when hearing the words "spec parser" 16:29:14 and the spec parser allows it to update the release field semi-intelligently on each rebuild 16:29:24 well, OBS' parser predates the existence of rpmspec 16:29:31 and an API in rpm for parsing spec files 16:30:39 when Factory 2.0 was being worked on, I had hoped we'd get something like that in Fedora too 16:30:43 Yeh, I kind of feel like this PR and other efforts are trying to do something without having to have a spec parser 16:30:45 but alas, my hopes were dashed 16:31:11 there's no way around it, you *need* a spec parser to do this right 16:31:32 King_InuYasha: Just drop the last 4 words and we gud ;) 16:31:38 :D 16:31:57 From a guideline standpoint, we don't care what happens under the hood; we only care about what packagers need to do. 16:32:04 right 16:32:27 from my perspective, we should reject pr-942 16:32:56 it will hopefully be superseded by something "better" soon :) 16:33:07 1. we have no tooling for putting it back together for package builds and 2. this doesn't solve any problems compared to status quo 16:33:07 +1 tot reject 16:33:09 *to 16:33:12 I'm struggling to understand what the motivating benefit of this is. Maybe I missed something. What pain does this fix? 16:33:41 limburgher: IIUC it doesn't, at least not without other changes that aren't there yet 16:33:43 I guess it makes specfiles shorter? Maybe makes merges easier? 16:33:58 tibbs: I think merges are the main point 16:34:04 ... 16:34:05 it doesn't fix merges because commits don't specifically care about files, they care about blobs 16:34:07 Also, does this %external_changelog macro even exist currently? 16:34:12 it does not 16:34:19 Then, uh.... 16:34:24 you can do a bunch of automation if there's no changelog and the release is handled by robots 16:34:29 yup 16:34:29 Right, to git, it's not files, it's a pile of lines. 16:34:42 geppetto: that's a big part of what OBS does 16:34:56 King_InuYasha: I've had lots of cherry pick merges fail due to changelog entries 16:35:02 though since the OBS VCS sucks, they have a changelog file 16:35:16 What does this give us that rpmdev-bumpspec doesn't? 16:35:18 and OBS auto-formats it into a %changelog section and appends it to spec 16:35:19 second the cherry-pick thing 16:35:41 carlwgeorge, geppetto: think about this: if it's a separate file but in the same commit, how will that help for merging? 16:36:04 or cherrypicking 16:36:13 i didn't claim putting it in a separate file helps, just that making cherry-picks work better is a good goal :D 16:36:13 it changes 1 file with 2 merge conflicts into 2 files with 1 merge conflict each :) 16:36:19 King_InuYasha: git restore CHNAGELOG --source=origin/master :D 16:36:20 King_InuYasha: was hoping the seperate file would be generated … or ignore merges on it … or something 16:36:29 haha 16:36:36 yeah, this PR does not propose any of that 16:36:54 pingout's rpmautospec will actually provide a path to that, though 16:36:56 So the benefit of this PR would appear, with the current RPM to be nil? 16:36:59 yes 16:37:12 also, still no solution for releng tooling :) 16:37:20 geppetto: I don't think I saw your ping, but I'm completely opposed to this approach. 16:37:22 I think it gets us to a place where the benefit could be non-nil … but eh 16:37:33 sgallagh: Fair enough :) 16:37:40 It's a lot of churn for *could* 16:37:54 I'm -1 unless I hear a compelling argument. 16:38:02 -1 for me as well 16:38:03 I'd much rather see an approach that just encodes the changelog text in the git commits. 16:38:07 -1 from me as well 16:38:11 -1 as well 16:38:30 -1 16:38:43 as a side note: https://github.com/encukou/rpm-spec-merge-driver 16:39:12 #action #pr-942 rejected … pretty much everyone doesn't like this approach to solving the problem. Speak to pingu, sgallagh, rpmbumpspec devs etc. 16:39:19 -1 16:39:33 It doesn't really solve any problem, unless the problem is that the specfiles are just too long. 16:40:21 I do still have the example where I was forbidden from stripping ancient changelog entries from a specfile. 16:40:58 Did you try to do that as a non-maintainer? 16:41:05 s/maintainer/owner/ 16:41:37 I would happily support a two-Fedora-release maximum on Changelog entries. 16:41:43 No, I co-maintain the package in question. 16:41:48 Eh, I probably don't care … too much of this was a good idea when we had 200 packages and now not so much. 16:42:15 200? good ol' times 16:42:17 sgallagh: I wouldn't, but ehh 16:42:26 King_InuYasha: Shorter? 16:42:35 I personally like being able to read about what happened to a package in the olden days but I'm odd. 16:42:37 geppetto++ 16:42:37 sgallagh: Karma for james changed to 6 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:42:38 geppetto: I am generally not in favor of trimming changelogs 16:42:48 I had rewritten the specfile from scratch for a new major version of the software, but years and years ago Red Hat had incorporated someone else's specfile and promised that their changelog entries would remain in perpetuity. 16:42:51 King_InuYasha: same 16:43:02 Trim the changelog into a file after two releases, maybe? 16:43:06 That would be a reasonable compromise. 16:43:07 I get screwed surprisingly often by long ago changes, and being able to figure that out is nice 16:43:15 sgallagh: we already do that automatically with rpm 16:43:24 We do? 16:43:26 only the spec file has the complete changelog 16:43:33 everything else is trimmed to two years 16:43:34 Yes, rpm just ignores old changelog entries. 16:43:40 huh, I did not know that 16:43:49 King_InuYasha: At this point I feel like unless you can git blame it almost nobody will see it after 12 months. 16:43:54 yup, rpmbuild cuts off all changelog entries that are older than a year I think? 16:44:05 geppetto: I can't rely on git because of CentOS/RHEL 16:44:08 which is funny when you build old SRPMs 16:44:09 and openSUSE 16:44:23 But this is Fedora. 16:44:27 tibbs: I don't think that's true … createrepo trims them automatically, from being in the repo. 16:44:34 this is Sparta! 16:44:45 But if you look at a package, or install it … all of it is still there. 16:44:46 tibbs: and Fedora has EPEL, you're point? 16:44:51 *your 16:44:59 redhat/macros:%_changelog_trimtime %{lua:print(os.time() - 2 * 365 * 86400)} 16:45:07 it applies to having to deal with CentOS/RHEL packages 16:45:14 This committee is not concerned with EPEL. 16:45:19 and we don't exist in a vacuum 16:45:40 tibbs: huh … so that's an rpmbuild thing? 16:45:45 geppetto: yep 16:45:47 (this discussion is not getting us anywhere) 16:45:57 it was added like five years ago, I think? 16:45:57 mhroncok: indeed 16:46:12 and we turned it on three years ago? 16:46:15 Regardless, the PR under discussion was already rejected; this is just rambling. 16:46:21 King_InuYasha: the changalog for when this was added is long gone :D 16:46:22 King_InuYasha: So became usable a few months ago in rhel8? 16:46:29 * geppetto ᕕ( ᐛ )ᕗ 16:46:37 geppetto: yeah, it's in RHEL 8 already :D 16:46:49 #topic #977 Get new members? 16:46:49 .fpc 977 16:46:49 https://pagure.io/packaging-committee/issue/977 16:46:50 geppetto: Issue #977: Get new members? - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/977 16:47:03 That kind of leads us to this … 16:47:06 * King_InuYasha keeps thinking of "Got milk?" campaign with that statement 16:47:11 carlwgeorge and King_InuYasha wave to everyone 16:47:13 so I assume we got carlwgeorge and King_InuYasha? 16:47:17 * carlwgeorge waves 16:47:20 * King_InuYasha waves to the flat crowd 16:48:02 mhroncok: technically we haven't all officially voted … but I've not seen anyone say anything negative either, so I'm guessing we'll be adding both 16:48:05 should we make it official? 16:48:17 decathorpe: That's kind of what we do :) 16:48:33 put a ring on it :D 16:48:37 * decathorpe goes to fetch the big rubber stamp 16:48:39 I assume that we would replce mbooth, right? 16:49:20 yeah, I think he already stepped down a few months ago? 16:49:33 Then yeh 16:49:41 he said "if you got somebody else, feel free to swap me" 16:49:45 we have 8 atm … aiming for 9 16:49:57 8 includes mbooth 16:50:42 so we still need another? 16:50:52 ok, proposal: replace mbooth with carlwgeorge and King_InuYasha 16:50:58 King_InuYasha: 7 16:50:59 King_InuYasha: not really 16:51:04 King_InuYasha: 7+2 == 9 :) 16:51:08 :D 16:51:19 math is hard, doncha know? :P 16:51:20 mhroncok: +1 16:51:40 No complaints from me. 16:51:45 Sounds good. 16:52:05 \o/ 16:52:07 geppetto: ? 16:52:18 Ok, I'm going to just stamp it then … collect your rings from the front desk. 16:52:30 that is basically +5 16:52:35 That would be the SufferRing, yes? 16:52:38 #action Add carlwgeorge and King_InuYasha as new members 16:52:49 sgallagh: hahaha 16:53:07 you won't be laughing for long ;) 16:53:14 * King_InuYasha laughs and sighs 16:54:05 sgallagh: We generally prefer to wait for at least the second time they are here officially before letting them know what a terrible idea it was 16:54:34 Come play with us carlwgeorge and King_InuYasha .... come play with us forrrreeeeeevvveeeerrrrrrrr 16:54:34 carlwgeorge: you are carlgeorge in FAS, rght? 16:54:36 *right 16:54:52 mhroncok: nope, carlwgeorge 16:54:59 limburgher: wow that was dark 16:55:01 carlwgeorge: oh, sorry 16:55:14 decathorpe: I'm that girl. :shrugs: 16:55:17 #topic Open Floor 16:55:18 carlgeorge was my old fas, but there is no way to change a fas so i started over at some point 16:55:48 the "w" stands for "with a w now". it's very meta 16:55:48 new AAA system might let us actually do renames :D 16:55:54 Ok, going to try to end before the hour this week so bcotton doesn't have to #action me ;) 16:56:09 Council is in #fedora-meeting now 16:56:11 geppetto: no council meeting this week, so you're okay :-) and we moved to #fedora-meetnig in the future 16:56:12 so he's not going to 16:56:25 King_InuYasha: oh i still might ;-) 16:56:29 hah 16:56:37 Ohh, back to dealines making a nice whooshing sound then 16:56:45 https://fedoraproject.org/wiki/Packaging_Committee#Members 16:57:19 mhroncok++ 16:57:51 also https://pagure.io/packaging-committee 16:57:56 there is no FAS group, right? 16:58:44 IIRC we only needed that for Trac. 16:58:49 * limburgher has dated herself 16:59:01 carlwgeorge: https://fedoraproject.org/w/index.php?title=User:Carlgeorge&redirect=no 16:59:55 limburgher: bah, trac wasn't that long ago … was it? 16:59:58 heh, some out of date stuff there 17:00:21 geppetto: after this year, who can remember? 17:00:39 limburgher: indeed, everything is now the before times. 17:01:10 Remember kids, commit to CVS before submitting a build to plague! 17:01:20 oh god 17:01:22 I remember that 17:01:29 LOL 17:01:38 wow, limburgher with the black and white TV references 17:01:44 King_InuYasha: I'm somehow glad I don't :) 17:01:57 Sort of astounding that we still got stuff done... 17:01:57 plague was in the process of being replaced with Koji when I started contributing to Fedora 17:02:02 * mhroncok only remembers CVS in rpmfusion 17:02:20 the CVS to Git change happened a few years later 17:02:25 Yeah. 17:02:31 The plague days were so much simpler. 17:02:44 "Do you remember when we had to cvs commit for plague builds? Well RPM committee remembers" 17:02:53 * limburgher dying 17:03:10 * King_InuYasha cracks up 17:03:19 smooge: Oh, for sure you remember too 17:03:34 Barring head trauma... 17:03:43 thinks cvs was a move too modern 17:03:58 RIP limburgher 17:04:12 * limburgher haunts bcotton 17:04:17 RCS over rsh gave you everything you ever needed 17:04:58 then again still uses emacs ~N~ as his version control system on his desktop 17:05:15 Unless someone has something else, I'll go eat my sepia-toned lunch in the drawing room... 17:05:24 ls /etc does take a couple of hours.. but I can see all the changes 17:05:33 * geppetto checks for smooge in ~/.rhosts 17:05:36 :O 17:05:45 X_X 17:05:54 Sounds good 17:05:59 have a good lunch 17:06:10 Thanks all, stay safe! 17:06:10 enojoy your lucnh 17:06:16 it's wine time for me already :) 17:06:22 maybe we can relive the version control wars of 20 years ago next time 17:06:32 smooge: SCCS ftw 17:06:35 Bitkeeper forever. 17:06:42 I don't disagree geppetto 17:06:50 :) 17:06:51 haha 17:06:53 heh 17:07:10 Now available as Open Source, didn't know that 17:07:34 I actually learned that one first, then RCS because we lost our licence to use the SCCS binaries 17:07:40 mhroncok: yeh, I downloaded it when it went that way … a few years too late 17:08:04 #endmeeting 17:08:20 #endmeeting