17:00:31 #startmeeting fpc 17:00:31 Meeting started Thu Feb 18 17:00:31 2016 UTC. The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:31 The meeting name has been set to 'fpc' 17:00:31 #meetingname fpc 17:00:31 The meeting name has been set to 'fpc' 17:00:31 #topic Roll Call 17:00:48 geppetto limburgher mbooth orionp racor Rathann SmootherFr0gZ tibbs|w tomspur: FPC ping 17:00:56 hello 17:00:56 Hi 17:00:57 * SmootherFrOgZ here 17:01:05 .hello smdeep 17:01:06 #chair orionp 17:01:06 Current chairs: geppetto orionp 17:01:06 smdeep: smdeep 'Sudeep Mukherjee' 17:01:09 #chair mbooth 17:01:09 Current chairs: geppetto mbooth orionp 17:01:11 #chair SmootherFrOgZ 17:01:11 Current chairs: SmootherFrOgZ geppetto mbooth orionp 17:01:57 * Rathann here 17:02:20 #chair Rathann 17:02:20 Current chairs: Rathann SmootherFrOgZ geppetto mbooth orionp 17:02:50 tibbs: You here? 17:03:33 #chair racor 17:03:33 Current chairs: Rathann SmootherFrOgZ geppetto mbooth orionp racor 17:05:16 Ok, let's get started 17:05:20 #topic Schedule 17:05:22 https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/VDENG5YJBCQ7MTPOKMTFLUAVOAJSXL33/ 17:05:29 #topic #597 php Guidelines update 17:05:32 .fpc 597 17:05:33 geppetto: #597 (php Guidelines update) – fpc - https://fedorahosted.org/fpc/ticket/597 17:05:55 +1 17:05:59 * RemiFedora here if question 17:06:46 +1 from me, and tibbs too 17:07:03 +1 from me 17:07:14 Hey, folks. 17:07:23 tibbs|w: hey you 17:07:42 #chair tibbs 17:07:42 Current chairs: Rathann SmootherFrOgZ geppetto mbooth orionp racor tibbs 17:07:46 Hey there 17:07:47 Pretty sure I +1'd the PHP stuff already. 17:07:51 * geppetto nods 17:08:22 +1 from me 17:08:47 Ok, that's +5 17:09:14 mbooth: racor: want to vote for the record? 17:09:19 +1 17:10:16 0, I don't feel knowledgeable enough to vote 17:10:26 #action php Guidelines update, for file triggers (+1:6, 0:1, -1:0) 17:10:40 #topic #598 introduce pyp2rpm tool on Packaging:Python page 17:10:44 .fpc 598 17:10:45 geppetto: #598 (introduce pyp2rpm tool on Packaging:Python page) – fpc - https://fedorahosted.org/fpc/ticket/598 17:10:55 draft author here 17:11:15 Draft: ​https://fedoraproject.org/wiki/User:Marbu/PackagingPythonGuidelines 17:12:04 As I've voiced in the ticket, I don't think this is a particularly good idea. 17:12:09 I'm not sure I'm happy about recommending using a packaging tool. I've also never used pyp2rpm 17:12:40 mbooth: Is this the diff? https://fedoraproject.org/w/index.php?title=User%3AMarbu%2FPackagingPythonGuidelines&diff=435548&oldid=433940 17:13:24 this is just a simple way to get started, right? 17:13:29 mbukatov: TODO-python-packaging-quickstart wiki page doesn't exist 17:13:34 Like cpan2spec or whatever? 17:13:34 geppetto: I haven't read it yet 17:13:34 As a comparison - https://fedoraproject.org/wiki/Packaging:Perl#cpanspec 17:13:36 and it's linked to 17:13:39 geppetto: yes 17:13:49 mbukatov: Is this the diff? https://fedoraproject.org/w/index.php?title=User%3AMarbu%2FPackagingPythonGuidelines&diff=435548&oldid=433940 17:13:56 mbooth: wrong mb tab complete 17:13:58 Rathann: yes, I haven't done this yet 17:14:08 not sure this really has to do with guideline 17:14:26 geppetto: yes, including the category and warning note 17:14:27 Based on the experience with cpanspec (Perl) I am -1 on the proposal. Mentioning is OK, but not in first place. 17:16:09 Plus, really, we have no idea at all if that tool actually provides guideline-compliant specs. Or if it will change in line with the guidelines. 17:16:25 The guideline pages really shouldn't be a packaging HOWTO. They're too long as it is. 17:17:24 ok, could I address your concerns by rewording the section somehow? 17:18:02 I guess everyone would be happy if it looked more like the perl one? 17:18:07 Not mine. 17:18:14 And I'd prefer that the perl one go as well. 17:18:18 ok 17:18:33 tibbs|w has a point 17:18:51 pyp2rpm is mentioned here: https://fedoraproject.org/wiki/SIGs/Python#Packaging_Quickstart 17:18:53 In any case, without that "TODO-python-packaging-quickstart" document I think this whole discussion is premature in any case. 17:18:56 that seems appropriate 17:19:27 orionp: Fair enough 17:19:48 I think it would be great if someone arranged some sort of packaging howto hierarchy in the wiki that shadowed the guidelines but had more instructional content. 17:20:13 But I really don't want to have to gate guidelines changes on changes to those documents, or spec generation tools or anything like that. 17:20:19 mbukatov: Ok, did you want us to come back and look at "TODO-python-packaging-quickstart" in a week or two, or let you open a new ticket? 17:20:59 If a set of documents existed, I would certainly be for adding a note on the main guidelines page referencing it. 17:21:11 But I really don't think this stuff needs to be in every guideline page. 17:21:15 +1 to tibbs|w idea 17:21:19 geppetto: let the ticket open, I would like to make changes based on your input including the todo-quickstart document 17:21:30 ok 17:22:07 so basically you say that pyp2rpm tool should not be mentioned at all 17:22:12 #info There are references in https://fedoraproject.org/wiki/SIGs/Python#Packaging_Quickstart 17:22:50 mbukatov: Well, it's already mentioned on the python sig page, no? What extra does amending the guidelines get us? 17:22:55 #action Against the idea of including lots of references to tools in the main pages, but maybe a more organizational change would work. Also waiting on "TODO-python-packaging-quickstart" page. 17:23:06 I think any howto kind of information belongs elsewhere, and we should reference the collection of that information once in the guideline. 17:23:40 * mbukatov tries to understand what changes needs to be done to the draft 17:23:49 So, whip up a master packaging howto page with links to the various resources in the wiki, and I'll draft a section to add to the main guidelines. 17:24:27 so if I remove the pyp2rpm paragraph, and leave initial section, link to will be quickstart and link to python sig page - would that be ok 17:24:37 Not to me, sorry. 17:25:00 My proposal: 17:25:04 1) Drop this draft entirely 17:25:19 2) Someone whips up a packaging howto page with useful links to all of this info. 17:25:31 tibbs|w: https://fedoraproject.org/wiki/How_to_create_an_RPM_package <- is that what you mean as a start page? 17:25:32 3) I draft a section to add to the main guidelines which points to this page. 17:25:46 Rathann: Perhaps; I haven't read that page in a while. 17:26:01 It's probably a bit long, and so it's something that should be linked from some master page. 17:26:56 ok, that could work 17:26:56 The master page can get fleshed out over time. We can even move some howto information from the guidelines eventually. 17:27:24 I just don't have time to write that master page right now, so if someone else does it I can take care of the rest. 17:27:36 I will try to draft a python quickstart page for the next week 17:28:03 that said, there is one thing left from my draft: 17:28:17 headline: Python Packaging Guidelines 17:28:30 and the 1st line starting: This page documents the guidelines and conventions ... 17:29:16 I don't see anything there that isn't either obvious or covered by the main guidelines page. 17:29:32 my point is that this page is 1st google result for "python packaging fedora" and the fact that it's a guideline is hidden in the bottom 17:29:35 You mean the paragraph beginning "This page documents...." 17:29:46 yes 17:30:01 It's a Fedora Python packaging guideline; of course it documents the guidelines for Python packaging in Fedora. 17:30:37 I mean, if people really think we need to say that.... 17:31:11 Then wouldn't just a header "Fedora Python Packaging Guidelines" instead of just "Packaging:Python" do the trick? 17:31:32 Seems like it to me 17:31:58 yes, that would work as well 17:32:22 tibbs: You want to just tweak that? 17:32:34 To put things in perspective, if a guideline page is more than two or three screenfulls on my monitor with my font (which I know is a pointless metric) not including contents and sample spec then it's too long. 17:32:44 And I should collapse the sample spec, too. 17:32:55 geppetto: Yeah, I'll figure out how to do that in wikinoise. 17:33:01 #action Tweak page title due to google result 17:33:07 #undo 17:33:07 Removing item from minutes: ACTION by geppetto at 17:33:01 : Tweak page title due to google result 17:33:10 #action tibbs Tweak page title due to google result 17:33:15 Ok 17:33:20 #topic #593 use RPM tags for langpacks description 17:33:27 .fpc 593 17:33:29 geppetto: #593 (use RPM tags for langpacks description) – fpc - https://fedorahosted.org/fpc/ticket/593 17:33:57 I'm still +1 here. 17:34:08 racor: mbooth orionp: Any one of you want to vote, the rest of us already have +1s 17:34:45 SmootherFrOgZ: You get to vote too :) 17:34:59 I really haven't had time to look, but I can trust others here... 17:35:01 What do you want us to vote on? The weak deps or the package renamer part? 17:35:06 * SmootherFrOgZ was reading 17:35:11 +1 17:35:22 Use RPM tags for langpacks (+1:4, 0:0, -1:0) 17:35:33 racor: Which package renamer part did you mean? 17:35:41 The part where it says that they don't need to be renamed? 17:35:52 racor, we are not renaming packages 17:35:56 ok, that's +5 17:35:57 rename all "lang" packs into *-langpack 17:36:11 no its for newly added packages in fedora only 17:36:24 OK, then that on weak deps 17:38:01 It's using %define, not %global 17:38:08 -1, silhan copr did not provide sufficent testing. Experience with weak deps/dnf already found in rawhide communicated the experience this all premature and not ready. 17:38:35 orionp: It's a parameterized macro, isn't it? 17:39:00 Is that the need then? I'm never sure... 17:39:08 Can't %global parameterized macros. 17:39:19 Obviously you don't want them expanded at the time of definition. 17:39:30 Is that going into a macros package somewhere? 17:39:59 The problem is that it's not generic. 17:40:16 That macro is in that spec as a specific example of what that package needs. 17:40:45 My argument is that if they have any applicability to more than one package then they really should be stuck in a macro file. 17:40:50 But I can work on that over time. 17:42:15 What's going to own %{_datadir}/pear-data/Horde_Perms/locale/%{1} ? 17:42:28 When writing this up I would probably make that a bit clearer by augmenting the final sentenct before the snippet to indicate that the definition of the macro is specific to the way that piece of software stores its language files. 17:42:39 orionp: It's supposed to be owned in %files later. 17:42:58 The example shows that, doesn't it? 17:43:22 Just under "Suppose you have a package with the following spec file" 17:43:37 %{_datadir}/pear-data/Horde_Perms/locale is owned, but not the language subdirs 17:43:59 also, there is "locales" and "locale" 17:44:00 Sure it is. 17:44:11 That line isn't %dir, it's a recursive ownership. 17:44:29 Oh, crap, never mind. 17:44:43 so then duplicate files? 17:44:46 Yeah, if you look at it that way, things do become a bit confusing. 17:45:01 That example really isn't well-written. 17:45:11 I can take a pass at it to try to make it understandable. 17:45:46 Basically it says that you're supposed to remove all of the text from the first snippet and replace it with the stuff in the second. 17:45:57 Seems like the file entry in the macro should just be %{_datadir}/pear-data/Horde_Perms/locale/%{1} 17:45:59 But then that leaves unowned directories, though that's pretty simple. 17:46:06 Well, simple to gix. 17:46:22 I would have to look at the actual package, I think. 17:47:11 we have this implemented now in tesseract package 17:47:13 http://pkgs.fedoraproject.org/cgit/rpms/tesseract.git/plain/tesseract.spec 17:47:22 I mean weak deps 17:47:28 That did already have its custom macro stuff. 17:47:41 paragan: Do you have a list of packages which you believe would need this? 17:48:10 I would (in my copious spare time) like to see if there is any commonality in those packages which could be pulled out into generic macros. 17:48:29 https://fedoraproject.org/wiki/I18N/Langpacks/BasePackages 17:49:13 I'll look at it one day. 17:49:21 sure thanks 17:49:37 Still embroiled in EPEL macros. 17:50:30 ok, Well this is still at +5/0/-1 so far … anyone want to change votes, or say anything? 17:50:44 If not then I'll pass it in a couple of minutes 17:51:50 Eh, +1 from me too 17:52:15 I will try to do some clarification as part of the writeup as I usually do, but if anyone objects to any of that then let me know. I will also fix that macro to not leave unowned dirs. 17:52:24 I look forward to trying it with my package 17:52:34 #action use RPM tags for langpacks description (+1:6, 0:1, -1:1) 17:52:36 paragan: Once I've written it up, please have a close look. 17:52:40 tibbs: Both things are fine with me 17:52:47 tibbs|w, sure I will 17:52:51 #topic #591 Description of filtering macros in Perl is outdated 17:52:51 That's kind of become the usual way I do things these days. 17:52:55 .fpc 591 17:52:57 geppetto: #591 (Description of filtering macros in Packaging:AutoProvidesAndRequiresFiltering#Perl is outdated) – fpc - https://fedorahosted.org/fpc/ticket/591 17:53:11 Otherwise the tickets bounce between meetings for way too long. 17:53:15 Do we have a final change for perl yet? 17:53:25 I don't think there was any movement at all. 17:53:35 ok 17:53:47 #topic Open floor 17:53:55 Honestly I've lost the context on that ticket. 17:54:09 racor is probably the most familiar with the perl filtering stuff. 17:54:10 tibbs: auto requires filtering 17:54:22 geppetto: I mean that the details are all swapped out now. 17:54:30 * geppetto nods 17:54:36 One problem is that the update perl filter is not in EPEL 17:54:58 orionp: Have you done any investigation to see if it's possible to have it there? 17:55:16 I seem to recall that the better filtering stuff wasn't done in RPM macros but was implemented further down. 17:55:20 tibbs|w: I just started looking, but it looks like there may be rpm changes as well 17:55:45 Still, I thought %autosetup was more than macros but it turns out that it isn't. 17:56:43 but with the right understanding, it should be possible 17:56:59 Could be. Maybe even just something close would be good enough. 17:58:42 Anyway, I guess that's something we can play with. 17:59:01 geppetto: Will you ping them in the ticket (591) or should I? 18:00:22 I can do it 18:00:46 #topic #591 Description of filtering macros in Perl is outdated 18:00:50 On a happier note, I actually did all of the writeups and made the announcemt. 18:01:14 #action Still need final change for perl. 18:01:21 #topic Open floor 18:01:24 Cool 18:01:48 There was one question, though. 18:01:57 tibbs|w: Sorry, was AFK 18:01:57 What was that? 18:02:03 On 567, what was I supposed to announce? 18:02:08 https://fedorahosted.org/fpc/ticket/567 18:02:11 .fpc 567 18:02:16 geppetto: #567 (Packaging Python 3 applications and modules for EPEL 7+) – fpc - https://fedorahosted.org/fpc/ticket/567 18:02:54 orionp: do you remember what I was supposed to do with that ticket? 18:03:20 tibbs: Says orionp had an EPEL7 section 18:03:43 There are so many links and diffs and such. 18:04:06 My fault for waiting too long and losing the context. 18:04:14 tibbs: https://fedorahosted.org/fpc/ticket/567#comment:10 18:04:31 Right, but there's a lot in that diff. 18:05:10 yeah, it's a mess. I think we were going to link to the epel guidelines, but even those aren't right yet 18:05:25 Right, so I'll just hold off on that. 18:05:34 Note that I did just go ahead and add this to the main guidelines: 18:05:53 ... too many damn guidelines.... 18:05:58 https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_for_EPEL 18:06:18 that's fine, tibbs|w 18:06:23 Crap, my wikinoise there was wrong. Well, I'll fix that. 18:06:25 So according to the logs, it's the last EPEL7 section of https://fedoraproject.org/w/index.php?title=PackagingDrafts%3APython&diff=cur&oldid=422445 18:07:54 rigtht, but we shouldn't link to a draft, and should the epel guidelines be in Packaging: or EPEL: ? 18:08:09 the epel guidelines should be under EPEL (because that makes the most sense). 18:08:12 EPEL: I'd guess 18:08:30 Okay, I'll work on getting a page there.. 18:08:40 We can revisit when that's done but really, why don't we just make it so that things aren't a bit different? 18:08:56 I guess that's the point of those fancy python macros we were writing. 18:09:23 I'm about done with the hard part of the EPEL stuff and I've learned more tricks so I can get back to them soon. 18:12:03 Ok, anything else? 18:12:13 If not I'll close in the next couple of minutes 18:12:21 And see you all next week :) 18:12:24 I'm good. 18:12:28 not really an agenda item, but is anyone from the FPC coming to Flock this year? 18:12:29 later 18:12:38 I should be at flock. 18:12:40 In Poland? 18:12:48 I'm obviously coming since it's in my home country :D 18:12:58 yes, geppetto 18:13:09 not as far as I know 18:13:17 Somehow it magically worked out. I was due to fly from Amsterdam back to Houston on the 1st. So I'll just divert. 18:13:30 Will have Jennifer with me and her goddaughter. 18:13:35 that's excellent news, tibbs|w :) 18:13:40 I'm also bringing my family 18:13:50 cool 18:13:51 Rathann: Can I bug you if I need to deal with the hotel? 18:13:57 tibbs|w: sure 18:14:54 We have Polish friends but they're from Warsaw and live either in Malmö or way up in Norway so they can't be too much help. 18:15:35 geppetto: Surely you can get RH to pay for some airfare.... 18:15:59 They're talking about doing fewer talks and more "work sessions" so there might be some opportunities for trying to clean up packaging. 18:16:28 tibbs: Well I went to devconf, and am still recovering from that 18:16:43 RH doesn't have a huge travel budget 18:16:50 With flock tacked on I'll be away from home for over a month. 18:16:59 ouch 18:17:04 Not sure how I'll handle that. 18:17:45 We're starting pretty far up in Norway and moving south until we hit Oslo, then to Amsterdam (renting a houseboat of all things) and then to Krakow. 18:18:42 Anyway, I guess this is super offtopic, but to make it on topic, perhaps we should think about whether we can do some sort of packaging sprint. 18:19:25 Rathann: I was trying to see if I could get a suite for the hotel, but they only have four and there's no pricing info. 18:19:35 The hotel only has ~160 rooms total. 18:20:26 And they only have seven pairs of adjoining rooms. I could do that and rent out the extra bed, though that might be weird. 18:22:42 weird 18:23:34 Ok, see you all next week. 18:23:37 Thanks for coming 18:23:40 #endmeeting