16:00:56 #startmeeting fpc 16:00:56 Meeting started Thu May 16 16:00:56 2019 UTC. 16:00:56 This meeting is logged and archived in a public location. 16:00:56 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:56 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:56 The meeting name has been set to 'fpc' 16:00:56 #meetingname fpc 16:00:56 The meeting name has been set to 'fpc' 16:00:56 #topic Roll Call 16:01:08 hey 16:01:12 #chair mhroncok 16:01:12 Current chairs: geppetto mhroncok 16:01:14 hey 16:01:45 geppetto: BTW there was a request to add a ticket to the agenda 16:01:53 * geppetto nods 16:03:37 hey o/ 16:03:51 #chair decathorpe 16:03:51 Current chairs: decathorpe geppetto mhroncok 16:03:57 hi 16:04:02 #chair redi 16:04:02 Current chairs: decathorpe geppetto mhroncok redi 16:04:17 sorry I could make it last week, was looking after a sick child 16:06:34 * geppetto nods 16:07:34 doesn't look good 16:07:43 need one more or it's going to be a quick talk only meeting 16:07:44 yeh 16:08:41 Hey, folks. 16:08:49 hey number 5 :) 16:08:50 Sorry; another busy day here. 16:08:53 #chair tibbs 16:08:53 Current chairs: decathorpe geppetto mhroncok redi tibbs 16:09:08 no problem 16:09:14 #topic Schedule 16:09:18 #link https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/5TS5QLTP5QDZ35OVTKSUAULKOKHUMRSD/ 16:10:21 + 890 requested by zbyszek 16:10:25 #topic PR#890 Stop using %systemd_requires for packages which only install unit files 16:10:31 yeh, doing that first 16:10:41 https://pagure.io/packaging-committee/pull-request/890 16:10:45 * zbyszek is here 16:10:48 zbyszek: hi 16:11:52 zbyszek: So the ordering thing is for the first transaction … it means that if something doesn't require systemd but can use it then it happens in the transaction after systemd 16:12:30 semantic breaks in the new paragraph (lines 34-40) would make it easier to review 16:12:37 I'm certainly OK with trimming the dependencies. 16:13:21 I haven't got time to read this properly, but I think the change makes sense 16:13:21 geppetto: there's two "ordering things": %systemd_requires, and %systemd_ordering, and both create ordering constraints. Which one do you mean? 16:14:14 zbyszek: Your question about using %systemd_ordering instead of nothing 16:15:38 geppetto: Oh, that. My question was a reply to ngompa's suggestion to recommend %systemd_ordering. 16:16:04 * geppetto nods 16:16:23 What you said is true, but I doesn't seem to apply to the common case, i.e. using the macro is not useful most of the time. 16:16:58 The real question is what happens outside of "most of the time"? 16:17:19 What's the breakage? How do you detect it? Is it common enough that we need to document it? 16:17:35 %systemd_ordering was originally created to cater to this specific case which has been obsoleted by the call to preset-all which was added later on. 16:18:49 tibbs: if a tool is used and mandatory, the spec file must declare dependencies on it. This general rule applies here. 16:20:01 but my understanding was that if you are putting systemd files down you should still use ordering 16:20:03 That's why I didn't want to turn %systemd_requires into a noop, but instead to prefer to remove its use from a) guidelines for %systemd_post* scriptlets, b) individual spec files after review. 16:20:59 geppetto: that used to be true, but there's no technical reason anymore. 16:21:04 ok 16:21:15 fair enough, I'm +1 then 16:22:09 I guess I am +1 too 16:22:14 +1 16:22:34 +1 16:23:06 redi 16:23:11 If you want me to repush the branch with more breaks, I can do it quickly. 16:23:15 Now I just wish I understood why ngompa wanted %systemd_ordering to be used. 16:23:30 +1 16:23:52 #action PR#890 Stop using %systemd_requires for packages which only install unit files (+1:5, 0:0, -1:0) 16:24:11 To be fair, I don't completely understand what OrderWithRequires: does. 16:24:31 #topic #886 Enable BRP for detecting RPATH 16:24:35 .fpc 886 16:24:36 geppetto: Issue #886: Enable BRP for detecting RPATH - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/886 16:24:53 I have long wondered why that's not enabled. 16:24:55 tibbs: it does the ordering part of requires … without doing the requires part. 16:25:13 tibbs: it's supposed to affect transaction order if both packages happen to be present in the transaction 16:25:38 tibbs: maybe because it used to have an extra dependency? 16:26:25 mhroncok: It's only recently that we started caring so much about buildroot dependencies. 16:26:40 I'm +1 on this 16:26:50 I'm +1 obviously 16:26:56 ignatenkobrain is +1 16:27:05 me too 16:27:11 My only fear is breakage. 16:27:43 Do we need to tweak the "beware of rpath" section to mention disabling this check? 16:28:00 yeah I think so 16:28:13 We would definitely need to change that section to remove mention of turning it on. 16:28:22 any check should have a documented way to disable it, because somebody always needs to 16:29:25 of course 16:29:37 Yes, we switched to a consistent way to disable things in %__os_install_post a while back. 16:29:49 * geppetto nods 16:30:05 is __arch_install_post something that is only called for arched packages? 16:30:13 In this case you would %global %__brp_check_rpaths %nil 16:30:41 mhroncok: No, not really. 16:30:56 The real macro is %__spec_install_post 16:31:01 omg 16:31:05 so many install posts 16:31:28 Which includes %__debug_install_post (if defined), %__arch_install_post and %__os_install_post. 16:31:32 The latter two unconditionally. 16:31:52 So... I don't know. I'll look deeper to see how those get defined just in case. 16:32:28 %__spec_install_post is simply appended to the end of the %install section as if it had been pasted there. 16:32:44 Which is why adding 'exit 0' screws up the world so badly. 16:33:48 So %__arch_install_post is defined in platform/XXX/macros file, so it can change definition depending on which platform you're building for. 16:34:30 But.. so is %__spec_install_post. So, I mean, whatever. If I look any deeper I will hurt myself. 16:34:54 :D 16:35:20 Anyway, it looks like the "beware of rpath" section is completely out of date. 16:35:32 The things it suggests that you add are already there in Fedora. 16:35:45 Or will be if we approve this. 16:35:54 (check-buildroot is there now) 16:36:00 ANyway, +1. 16:36:16 +1, but needs moar docs 16:36:17 Ok, that's +4 … I think 16:36:24 +5 now .. wooo 16:36:44 decathorpe: you want to vote? 16:37:46 I said, +1 me too :) 16:38:57 I can do some docs since that section needs to be cleaned up anyway. 16:39:10 ahh, missed that … looking for the +1 symbols :) 16:39:17 #action Enable BRP for detecting RPATH (+1:6, 0:0, -1:0) 16:39:31 #topic #887 Review Process Exemption: colcon - collective construction 16:39:37 .fpc 887 16:39:38 geppetto: Issue #887: Review Process Exemption: colcon - collective construction - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/887 16:40:36 * mhroncok was +1 in the ticket 16:41:07 yeh, got to the end and I'm +1 too 16:41:18 the "examples" got approved already? 16:41:24 yeh 16:41:29 then I'm #1 too 16:41:31 +1 16:41:43 +1 16:42:12 I'm OK for exceptions to fully templated packages _as long as license checks were done_. 16:42:50 yes, I assume that has been done 16:43:24 +1 16:43:28 You know what they say about assuming. I should have asked the question in the ticket. 16:43:36 gotta go now, sorry 16:43:47 right :D 16:43:52 bye redi 16:44:00 the packages generally are all Apache licensed 16:44:10 of course they might be some hidden gems in them 16:44:14 *there 16:44:25 At least according to the LICENSE files on github, everything but the docs site is ASL2. 16:45:19 But certainly, stuff could be in there. It would be an interesting question to spot and the legal team: how much checking needs to be done before importing things? 16:45:27 #action Review Process Exemption: colcon (+1:5, 0:0, -1:0) 16:45:39 #topic Open Floor 16:45:57 Ok, with redi gone we only have 4 … and we are nearing the end of the hour anyway 16:46:05 anything anybody wants to talk about? 16:47:23 nope 16:48:55 Not me. 16:49:52 Ok, see you next week. 16:49:55 #endmeeting