16:00:21 #startmeeting fpc 16:00:21 Meeting started Thu Apr 11 16:00:21 2019 UTC. 16:00:21 This meeting is logged and archived in a public location. 16:00:21 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:21 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:21 The meeting name has been set to 'fpc' 16:00:21 #meetingname fpc 16:00:21 #topic Roll Call 16:00:21 The meeting name has been set to 'fpc' 16:00:27 Hey, folks. 16:00:32 #chair tibbs 16:00:32 Current chairs: geppetto tibbs 16:00:51 hey 16:00:52 hey 16:00:52 Another crazy busy week and day for me. Maybe one day this will let up. 16:01:04 hi 16:01:05 #chair redi 16:01:05 Current chairs: geppetto redi tibbs 16:01:38 Hi guys:) 16:02:02 #chair decathorpe 16:02:02 Current chairs: decathorpe geppetto redi tibbs 16:02:08 hi guys :) 16:02:15 hey 16:02:32 * decathorpe is online on phone only, for now 16:04:48 It's meeting time isn't it? 16:05:08 andi89gi: yes 16:05:36 We need 5 16:05:48 mhroncok: ahh, I missed you 16:05:55 #chair mhroncok 16:05:55 Current chairs: decathorpe geppetto mhroncok redi tibbs 16:06:27 #topic Schedule 16:06:32 #link https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/S4HDZPSDOLHCMWXLQF2OXE27KLYTPPG3/ 16:06:44 #topic #876 Mass Python 2 Package Removal - policies and exceptions 16:06:49 .fpc 876 16:06:50 geppetto: Issue #876: F31 System-Wide Change: F31 Mass Python 2 Package Removal - policies and exceptions - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/876 16:07:26 so we'd liek to get some exceptions from package reviews 16:07:35 fesco approved this, but I don't know if they read it all :D 16:07:55 +1 to exempting these from review. 16:08:29 Sure +1 16:09:01 FTR I'm +1 16:09:22 +1 16:09:26 redi: decathorpe: Vote? 16:09:29 Doesn't mean someone shouldn't try to make them clean but I don't see a reason to go all the way through bugzilla. 16:09:30 yeah, +1 too 16:09:33 andi89gi: Who are you? 16:09:43 yeah +1 16:10:14 #action Exceptions from full package reviews (+1:5, 0:0, -1:0) 16:10:20 which rmeinds me I need to make all the boost-python2 stuff conditional 16:10:23 *reminds 16:10:25 I'm Andi, new in the developing-list, Fedora maintainer(Telegram chat) 16:11:14 welcome. this is a meeting of the Fedora Packaging Committee (FPC) so the votes are from committee members 16:11:16 andi89gi: That's cool, feel free to participate but please don't vote … as you aren't an FPC member, and I get confused easily :) 16:11:47 mhroncok: Anything else we want to vote on today? 16:12:06 * mhroncok looks 16:12:08 #3 seems like an easy win 16:12:16 geppetto: ok thx for the info;) 16:12:24 How's best way to participate? 16:12:59 andi89gi: If tickets come up that you know things about, you can provide that info. to everyone :) 16:13:09 geppetto: did we just veot the entire ticket or just the review exceptions? 16:13:23 mhroncok: I thought just the review exception 16:13:52 so basically there are 4 points where we said we want FPC approval 16:14:04 all linked formt he ticket 16:14:42 it's long 16:14:45 sorry about that 16:14:48 vote in the ticket? 16:14:52 I believe two of those aren't up to us at all. 16:15:02 technically, FPC approval is not needed 16:15:16 I guess an "FPC acks this" is what we really want 16:15:30 The review exceptions are our thing. 16:15:41 geppetto: ah okay;) thx 16:15:44 The packaging requirements are our thing. 16:15:51 if the output is FPC does not concern this FPC bussines, that's Ok as well 16:16:11 At least if my summary in the first reply is correct.... 16:16:27 1 Require specific and explicit conditionalization of python2 support in all specs. 16:16:39 pretty sure ntoe xactly what we proposed 16:16:44 *not exactly 16:17:10 the change says you need to conditionalization python2 if you are about to rip it off (but dependent packages exist) 16:17:21 I took that from step two of "Removing Python 2 parts". 16:17:38 tibbs: and that's right, except "in all specs" 16:17:49 it "in specs of packages where this happens" 16:18:11 IIUC, this means python2 needs to be behind conditionals, so it can be ripped out more easily when it comes to that? 16:18:18 Then I'm unclear on the specs where python2 is to be supported but this wouldn't happen. 16:18:46 mhroncok: ok, that makes more sense … so something that is py2 only doesn't need to change? 16:18:46 nothing changes there. you can conditionalize, but are not required to do that 16:18:50 I thought the idea was to force either removal or conditionalization. 16:19:30 nope. the idea is to give maintainers the ability to remove in a documented way where others cans ee what's being removed if they want to adapt it 16:19:51 Oh, OK, then I had completely the wrong impression. 16:20:00 ah. that makes more sense 16:20:08 geppetto: somethign that's py2 only will get questions from us, but doesn't need to add any conditionals 16:20:17 * geppetto nods 16:21:33 packaging guidelines that require conditionalization of python2 would be kinda weird, because it would be only applicable retroactively, since new py2 packages are forbidden 16:21:45 So then change my #1 to "Modify guidelines to prescribe the method for conditionalizing python2 support." 16:21:52 OTOH it is not sucha bad idea, once we decide to pull the plug 16:22:18 so that's for packagers who maintain different branches of fedora / epel with one spec? 16:22:28 nope 16:22:44 then I don't understand what it's for 😂 16:22:47 And sure, while are changes aren't _usually_ retroactive, that doesn't mean we can't make a change and then start asking people to follow it. 16:22:57 in the change proposal... (and I don't know if it so badly written or just too long)... 16:23:11 we just say: if you maintain py-foo and you want to get rid of py2-foo, here's how 16:23:29 (assuming that py2-foo is still required - otherwise you have to get rid of it) 16:23:49 ah, so for moving it to a separate source package 16:24:00 and one of the requirement is: first, you conditionalize py2, so inetrested other maintainers can clearly see what do you want to remove 16:24:31 Then why bother with conditionalizing the python2 support. Just coordinate with someone who wants to do the python2 package. You delete the stuff from your package and they add theirs. 16:25:09 As long as there aren't any circular dependencies, things shouldn't explode though maybe rawhide has broken deps for a little while. 16:25:10 tibbs: 1. the problem is when there is noone who wants to do the python2 package 16:25:27 Well we can't force anyone. 16:25:40 the idea here was: the packjager draws a line in the package and says: I'm orphanning this half 16:26:05 I guess I understand the point but don't see how that's really useful. 16:26:13 and if nobody takes it, it's "retired" (the conditional is flipped and/or the bits are deleted) 16:26:26 * geppetto nods 16:26:35 And I guess you could accomplish the same thing just by sending an email. 16:26:41 to who? 16:26:57 The devel list. 16:26:58 (and you send e-mail in the process as well) 16:27:00 and how would you keep track of orphaned python2-foo subpackages? 16:27:01 you do 16:27:21 decathorpe: you don't. you just spam the depndents for a while and then you stop caring 16:27:27 My point is that should be enough. If we need more then someone can keep a list and post it occasionally. 16:27:38 mhroncok: the best process ;) 16:27:46 "These python2 packages will be removed in X weeks unless someone offers to maintain them." 16:27:51 yep 16:27:53 basically 16:28:10 So... why are any changes to the spec required for any of this? 16:28:12 disclaimer: i also find the conditional parts reduntant 16:28:14 Ok, is there any other bits we feel like we should vote on here or move on to the next ticket? 16:28:22 Seems to me that if you want to keep it simple, just... keep it simple. 16:28:54 I'Ve decided to stop bikeshedding about this part with the rest of the change owners and just keep it there 16:29:37 * decathorpe shrugs 16:29:41 Oh hi, I was busy and spaced on time. 16:29:42 so unless you consider this really bad, I suggest the same. but if we want to change the procces by removing that part, I'd support it 16:29:54 #chair limburgher 16:29:54 Current chairs: decathorpe geppetto limburgher mhroncok redi tibbs 16:30:13 if they want to make it more complicated than it needs to be? I don't particularly care about that 16:30:45 I think it's pointless but if we do want to standardize on how the conditionalization would be done ("%if %{with python2}") then we should vote on adding that to the guidelines. 16:30:57 pviktori: the conditionalization of python2 bits in the specfile seems to be considered as more complicated than it needs to be. are you still around? 16:31:01 Just so that nobody starts making up their own thing. 16:31:19 And that should just be a couple of sentences in the existing python2 page. 16:31:30 tibbs: I agree, if we do it, it should be the same everywhere 16:31:45 tibbs: I can agree to that 16:33:11 it'd just be a short and short-lived addition to the python packaging guidelines 16:35:27 Ok, is there any bits we feel like we should vote on here or move on to the next ticket? 16:35:39 proposal: conditionalization of python2 (if used) SHOULD be done with %if %{with python2} 16:35:46 +1 16:35:54 ok +1 16:35:55 +1; I'll trust you to patch that in appropriately. 16:36:33 +1 FTR 16:37:58 +1 16:38:48 decathorpe: vote? 16:38:59 +1 16:39:06 #action conditionalization of python2 (if used) SHOULD be done with %if %{with python2} (+1:6, 0:0, -1:0) 16:39:08 sorry 🙊 distracted 16:39:11 no problem 16:39:57 as for the mass removal change. anything you feel strongly opposed to? 16:40:17 I kind of put #3 and #4 together 16:40:41 like if py2 packages don't work it should be easy for someone pick them up, but if nobody does then they get removed quickly. 16:40:57 that the idea 16:41:13 * geppetto nods … +1 on both then :) 16:42:04 Yeah. No sense dragging this out. 16:42:33 * decathorpe nods as well 16:43:22 We want to vote on it … or just assume it's fine? 16:43:42 i THINK IT'S FINE 16:43:44 oops 16:43:51 Ow, my ears. 16:43:53 👍 16:43:54 lol 16:43:57 VERY FINE 16:43:58 :) 16:44:11 https://giphy.com/gifs/form-z9AUvhAEiXOqA 16:44:12 Fine by me. 16:44:21 lol yeah 16:44:30 redi: FYI it's really easy to remap caps lock to something useful in Fedora. 16:44:49 caps lock is useful. for shouting ;) 16:44:50 ARE YOU SAYING CAPSLOCK IS NOT USEFUL? 16:45:00 :D 16:45:21 I'll probably drop off the grid in a few seconds, will be back in 5 minutes 16:45:35 should I try to remove the conditionalize everyhting first part of the process? 16:47:19 I think the only thing it does is hurt your compliance ratio. 16:47:40 Many users would send an email but if they have to mess with the spec and follow guidelines.... 16:47:46 But that's not really FPC business. 16:48:13 makes sense 16:48:28 ok, enough of this :D 16:49:34 * decathorpe is back 16:49:59 ok 16:50:07 #topic #878 Package Naming Guildelines for lua packages 16:50:11 .fpc 878 16:50:12 geppetto: Issue #878: Package Naming Guildelines for lua packages - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/878 16:50:32 The only comment I had was in the ticket. 16:50:40 I agree with tibbs 16:51:03 lua5.2-foo makes the most sense, considering the rest of the guidelines 16:51:28 Yeh, I'm fine with it … +1 16:51:31 I can only guess that they would want the "compat-" prefix to avoid having to set up a whole new set of packages when they want to roll the versions over. 16:51:50 I assume they just seen compat-foo and foo-compact 16:51:51 But I think that's actually a feature, and allows them to have three or more supported versions if they really want. 16:51:57 and they tried to make it less confusing 16:52:02 and we say: change it entirely 16:52:04 +1 also. Interesting that I *just* processed some lua SCM requests. . . 16:52:05 and they will not 16:52:40 well, we can't force anything 16:52:45 Note that there's also a lua module called "compat" which might be confusing if you see it. 16:52:52 :) 16:52:58 So under their scheme you would have compat-lua-compat which.... 16:53:06 :) 16:53:21 * limburgher puts vodka in her tea 16:53:45 limburgher: good idea ... 16:54:26 tibbs: So I assume you are +1 … that gives us +3 atm. 16:54:34 +1 16:54:40 I'm +1 to the suggestion I made, yes. 16:54:50 * geppetto nods 16:54:56 Not +1 to the scheme that was originally proposed. 16:55:09 And boo to Arch for implying that lua version 51 exists. 16:55:23 I'm +1 too, FTR 16:55:35 Ok, that's 5 16:55:36 Arch has a history of doing weird thigns with version numbers 16:55:42 I made them stop doing it for gcc 16:55:48 Both the the arch users can complain 16:55:52 s/with version numbers//g 16:55:57 redi++ 16:55:58 decathorpe: Karma for jwakely changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:55:58 https://src.fedoraproject.org/rpms/python-u-msgpack-python 16:56:03 https://src.fedoraproject.org/rpms/python-into-dbus-python 16:56:04 :D 16:56:18 OFFS 16:56:22 lol 16:56:31 💩 16:56:41 good grief 16:56:45 +1 for the lua thing 16:56:54 #action Pkg Naming guildelines (for lua), with tibbs change (+1:6, 0:0, -1:0) 16:57:05 #topic Open floor 16:57:06 I have a hard stop in 3 min. 16:57:26 That's fine … I think we are done for the week anyway 16:57:35 So it seems. :) 16:58:10 https://src.fedoraproject.org/rpms/perl-rpm-build-perl 16:58:22 16:58:34 mhroncok: stop making me sad 16:59:36 Ok, see you next week 16:59:39 #endmeeting