16:00:07 #startmeeting fpc 16:00:07 Meeting started Thu Sep 26 16:00:07 2019 UTC. 16:00:07 This meeting is logged and archived in a public location. 16:00:07 The chair is mhroncok. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:07 The meeting name has been set to 'fpc' 16:00:07 #meetingname fpc 16:00:07 #topic Roll Call 16:00:07 The meeting name has been set to 'fpc' 16:00:07 /msg limburgher FPC: /join #fedora-meeting-1 16:00:07 /msg mbooth,orionp FPC: /join #fedora-meeting-1 16:00:08 /msg SmootherFr0gZ,tibbs FPC: /join #fedora-meeting-1 16:00:08 /msg decathorpe,mhroncok FPC: /join #fedora-meeting-1 16:00:09 /msg ignatenkobrain,geppetto FPC: /join #fedora-meeting-1 16:00:39 .hello churchyard 16:00:40 mhroncok: churchyard 'Miro Hrončok' 16:01:34 .hello2 16:01:35 decathorpe: decathorpe 'Fabio Valentini' 16:01:41 I'm here! 16:01:42 #chair decathorpe 16:01:42 Current chairs: decathorpe mhroncok 16:01:46 decathorpe: hi 16:01:51 .hello2 16:01:52 ignatenkobrain: ignatenkobrain 'Igor Gnatenko' 16:01:59 #chair ignatenkobrain 16:01:59 Current chairs: decathorpe ignatenkobrain mhroncok 16:02:13 ignatenkobrain: o/ 16:03:12 mhroncok: \o/ 16:03:21 Hey. 16:03:44 #chair tibbs 16:03:44 Current chairs: decathorpe ignatenkobrain mhroncok tibbs 16:03:45 hi 16:04:10 I might disappear at some point if my wife is going to go giving a birth 🙂 16:04:26 ignatenkobrain: that's a big if 16:04:40 oh wow. congratulations ;) 16:04:59 ignatenkobrain: woah, congrats! :) 16:05:38 ignatenkobrain: I don't think we'll have quorum anyway 16:06:14 should I go trough the topics anyway or jump to open floor? 16:06:30 mhroncok: btw, your direct "FPC MEETING NOW" messages were malformed 16:06:37 decathorpe: how? 16:06:54 they didn't register as correct IRC commands I guess 16:07:08 they were just posted here? 16:07:11 "/msg SmootherFr0gZ,tibbs FPC: /join #fedora-meeting-1" I got this 16:07:24 "/msg decathorpe,mhroncok FPC: /join #fedora-meeting-1" and this 16:08:06 I think I did not receive this one 16:08:18 ok, will try differently next time 16:08:23 anyway 16:08:28 * decathorpe shrugs 16:08:35 #topic Open Floor 16:08:52 there is no quorum. ignatenkobrain might run... let's call it a day 16:08:56 one think 16:08:59 *thing 16:09:30 #info SELinux people approached me to ask what they can do to move https://pagure.io/packaging-committee/pull-request/814 forward 16:10:02 if you are able to review the latest changes, please do (I wasn't yet) 16:10:11 anyone has anything else to say? 16:10:41 I'll try to check it again. Last time I have checked, it was too much of useleess info there 16:11:16 Yes, that's always been the problem with that document. 16:11:22 yeah I think there's a lot in there that has nothing to do with packaging ... 16:11:54 And unless they have figured out why that's bad, this simply isn't going to move forward unless we take the pieces we want and turn that into a guideline. 16:12:23 ideally it should be split into two documents - one "how to package an selinux module" and "how to create a custom selinux module" (or something like that) 16:13:03 That's basically what I said when the document was first presented to us. 16:14:15 OK, I'll try to communicate that to their request 16:14:21 +1 16:15:49 I'll end in 2 16:16:24 Geez, I got called away. Congrats ignatenkobrain! 16:17:08 #chair limburgher 16:17:08 Current chairs: decathorpe ignatenkobrain limburgher mhroncok tibbs 16:17:37 so... ignatenkobrain, are you still with us? 16:17:51 I am :) 16:18:02 we have a quorum 16:18:11 #topic Schedule 16:18:17 #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NFH4A6XZLFQCL7XGYJJSZF3HZ5TU4E42/ 16:18:25 #topic #902 Cleanup & enhance spec files 16:18:25 .fpc 902 16:18:25 https://pagure.io/packaging-committee/issue/902 16:18:26 mhroncok: Issue #902: Cleanup & ehnance spec files - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/902 16:18:49 this is tagged with meeting 16:19:01 but I'm not sure there's anything to discuss 16:19:14 I guess we should remove tag and do it :) 16:19:21 2 months ago: Propose guideline changes we can vote on... 16:19:43 removing the meeting tag 16:19:58 anybody has something for this ticket? 16:20:14 yeah, I think we agreed that we need actual proposals for Guideline changes 16:20:33 otherwise these are only stylistic preferences 16:20:38 I don't even agree with #3 in their list. 16:21:01 #2 is absolutely correct because the compression can change and I though this was already mentioned somewhere. 16:21:17 Haven't really tried to understand #1. 16:21:31 it is: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_manpages 16:22:30 proposal: we close this, there has been no response in 2 months 16:22:44 The last sentence could use a tweak to use SHOULD/MUST language (as is the case with a bunch of stuff that existed from the old days) but otherwise, yes, they should feel free to go ahead with #2. 16:23:15 +1, I'm on board with that 16:23:48 (to clarify: say #2 is good, and close the ticket) 16:24:28 Doesn't hurt to keep it open to discuss the other stuff, I guess. 16:24:38 there is no discussion 16:25:00 myself I like all 3 suggestions 16:25:08 but I don't mind keeping it open 16:25:37 I strongly disagree with any prohibition on marking things as %doc just because there is RPM magic to mark them as %doc automatically. 16:26:14 I don't personally know the list of directories which get magically marked as %doc, and wouldn't expect most packagers to know, either. 16:26:48 But maybe I'm missing something. 16:27:55 I slightly disagree with prohibition of being more explicit 16:28:31 I wouldn't mind if the guidelines say that man pages are automatically maked as doc and the packagers don't need to mark them as such 16:28:48 Nor would I. 16:29:11 But this ticket was about bulk changing every package, and I just don't see the utility in doing that. 16:29:33 mhroncok: yes, we should definitely document that somewhere 16:30:04 #info We should document that man pages are automatically marked as %doc and the packagers don't need to mark them as such 16:30:36 move to the next? I don't think it's worth staying on this... 16:31:24 #topic #904 Caret versioning 16:31:25 .fpc 904 16:31:25 https://pagure.io/packaging-committee/issue/904 16:31:26 mhroncok: Issue #904: Caret versioning - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/904 16:31:40 this waits for F31. anything to discuss? 16:31:44 I think this is back on me. 16:32:14 Kind of lost the will to work on it for a while after the pointless nitpicky arguments. I should just ignore them, I guess. 16:34:46 so I guess https://pagure.io/packaging-committee/pull-request/908 needs a rebase and review? 16:35:15 Yes, and further work by me. 16:35:50 #topic #907 Which %__foo macros for executables are acceptable? 16:35:50 .fpc 907 16:35:50 https://pagure.io/packaging-committee/issue/907 16:35:51 mhroncok: Issue #907: Which %__foo macros for executables are acceptable? - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/907 16:36:29 there is a PR in python-rpm-macros -> https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/27 with an open question 16:36:36 I think it useful to stop referring to %__* macros in the guidelines, at least. 16:36:47 where it is possible 16:38:15 #info we should revisit our use of %__* macros in the guidelines, at least (possibly removing it where appropriate) 16:38:35 I think it would still be good to see what Panu has to say about the python question, but he's busy and it's often tough to get his attention. 16:39:09 OK, I'll try to get panu on borad 16:39:13 I thiink the open question is whether we want redefinition of, say, %python3 to change the definition of %__python3. 16:39:42 that's it 16:39:43 I think %python3 should be %python3 %__python3 16:40:11 I agree. 16:40:22 so the idea in the PR is that if people have old specfiles that redefine %__python3, it still works 16:40:51 but if they opt-in for the new macros, %python3, they don't need to worry about %__python3 at all 16:41:51 but I guess the question is, what will be used internally in %python3_version etc. %python3 or %__python3 16:42:22 Working on a PR to clarify the manpage language. 16:42:45 I wonder whether it is possible to have maco aliases 16:42:50 *macro 16:42:53 I guess it is not 16:42:54 mhroncok: If they use the new, non "__" macros then they don't have to worry about the internal macros _unless_ they want to redefine something. 16:43:17 If they do, then they can change the internal macro and see a redefinition of all of the macros which derive from it. 16:43:31 That's kind of the point of the internal macros. 16:44:00 it seems that really knows what is the point of the internal macros :D 16:44:22 if the point is: redefine me to change everything else, they should not be marked as internal, as they are part of the API 16:44:57 or the idea is: use %python3, %python3_version and %python3_sitearch to GET information, redefine %__pytohn3 to SET information? 16:45:17 because that kinda makes sense (at least it is consistent) 16:45:24 yeah that sounds good 16:45:40 Yes, I think that sums up Panu's comment on 907. 16:46:45 Ok 16:47:36 #action mhroncok to update the https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/27 in a line of what was said on this meeting (tl;dr use %python3, %python3_version, %python3_sitearch... to GET information, redefine %__python3 to SET information) 16:47:50 #topic #909 Suggest that linting/measuring-coverage is not for %check 16:47:50 .fpc 909 16:47:50 https://pagure.io/packaging-committee/issue/909 16:47:51 mhroncok: Issue #909: Suggest that linting code and measuring coverage is not %check's business - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/909 16:48:39 so we already tried to vote on something in there 16:48:59 https://pagure.io/packaging-committee/issue/909#comment-584794 16:49:10 thanks 16:49:10 you can have my +1 for that as well 16:49:45 +1 from me 16:49:50 You already have mine. 16:49:59 do I see +5? 16:50:18 I do 16:50:36 #agreed https://pagure.io/packaging-committee/issue/909#comment-584794 (+5,0,-0) 16:50:53 #topic #914 Automatic R runtime dependencies 16:50:53 .fpc 914 16:50:53 https://pagure.io/packaging-committee/issue/914 16:50:54 mhroncok: Issue #914: F31 System-wide Change: Automatic R runtime dependencies - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/914 16:51:23 I am pretty sure we've talked about this not so long time ago 16:51:25 So the last comment there somewhat moots some of the questions. 16:51:43 ignatenkobrain: we did 16:51:51 and IIRC we've agreed to wait for Legal and leave this to FESCo 16:52:05 but my memory might be wrong 16:52:05 I recall the same thing 16:52:18 Same. 16:52:19 Yes, but the last comment.... 16:52:44 Basically, filtering the extra Suggests is possible and easy, and sidesteps the legal issues. 16:52:52 https://pagure.io/packaging-committee/issue/914#comment-588089 16:53:01 At least according to the comment; I don't know how easy it actually is. 16:53:21 so to sum it up: https://pagure.io/packaging-committee/issue/914#comment-588089 till stands, but filtering the extra Suggests workarounds it 16:53:25 But if it doesn't result in Requires, Recommends or Suggests outside of the package set, then great, I'm all for it. 16:53:25 I'd like to see an example, that can be included in Guidelines. And the answer from legal. 16:53:26 *still 16:53:58 I'd like to see the answer from FESCo/Legal as well, but if this ticket doesn't depend on it then great. 16:54:15 I think in general we're all for automatic generation of dependencies wherever possible. 16:55:57 I guess qulogic would like to know, assuming legal and fesco would ack dangling suggests, whether the FPC would 16:57:04 but I'd rather not waste our time on a hypothetical problem 16:57:24 I don't think there's even a question. If FESCo says they're OK, then they're OK (and we make changes to the guidelines to indicate that). 16:58:07 ack 16:58:09 works for me 16:58:37 #info We'd like to see an example about filtering the extra suggest, so we can document it 16:59:10 #info FPC has no problem with dangling suggests as long as approved by legal and FESCo 16:59:12 I have to go, need anything from me in the next 60 seconds? 16:59:19 limburgher: not really, about to end 16:59:32 next item on scheule is the selinux PR and we've already covered that 16:59:41 #topic Open Floor 16:59:54 15 seconds to 1 hour 17:00:01 or 5 17:00:12 I got nothing :) I'll look at the %ghost and %verify stuff though 17:00:14 nope 17:00:19 Nothing from me. 17:00:39 ok, thanks everybody for being here 17:00:48 ignatenkobrain: good luck with your offspring 17:00:59 #endmeeting