16:01:41 #startmeeting fpc 16:01:41 Meeting started Thu May 14 16:01:41 2015 UTC. The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:41 #meetingname fpc 16:01:41 The meeting name has been set to 'fpc' 16:01:41 #topic Roll Call 16:01:44 Nope. Maybe I should start running xchat through Tor. ;)P 16:01:49 * limburgher here 16:01:56 morning 16:02:09 #chair limburgher 16:02:09 Current chairs: geppetto limburgher 16:02:12 #chair tibbs 16:02:12 Current chairs: geppetto limburgher tibbs 16:02:15 #chair orionp 16:02:15 Current chairs: geppetto limburgher orionp tibbs 16:02:38 Hello 16:02:47 #chair mbooth 16:02:48 Current chairs: geppetto limburgher mbooth orionp tibbs 16:02:56 hey everyone :) 16:03:50 Howdy. 16:03:51 * limburgher waves 16:04:20 We were down to 10 tickets.... 16:04:32 Le sigh 16:04:37 Actually I could do an announcement and get rid of a couple. 16:04:48 Will do that after the meeting. 16:04:54 #chair tomspur 16:04:54 Current chairs: geppetto limburgher mbooth orionp tibbs tomspur 16:05:08 racor won't be here today. 16:05:10 * tomspur is finally here... Seems irc with ipv6 is not working over here... 16:05:11 tomspur: I assume you are here ?:-o 16:05:24 so … situation normal with ipv6 then ;) 16:06:19 Ok, well we can start 16:06:24 #topic Schedule 16:06:28 https://lists.fedoraproject.org/pipermail/packaging/2015-May/010648.html 16:06:44 Anyone here for anything specific? 16:06:58 #topic #530 request copylib exception for dcraw.c 16:06:59 .fpc 530 16:06:59 https://fedorahosted.org/fpc/ticket/530 16:07:00 geppetto: #530 (request copylib exception for dcraw.c) – fpc - https://fedorahosted.org/fpc/ticket/530 16:07:21 My opinions are all in the ticket. 16:08:09 "it is, apparently, managed with RCS upstream" 16:08:11 It was suggested in the recent CVE BZ for LibRaw that I include bundles(dcraw)n. 16:08:24 I saw your comment about globals yesterday or tuesday 16:09:30 We should certainly document the bundling in all instances where it exists. 16:09:33 my opinion is roughly the same as yours and the nicest way to express it is probably "upstream too stupid/apathetic to release library/API" 16:09:40 But I'm not up for a blanket exception. 16:10:24 It's just an old-school programmer with some old-school code. Which is fine, but don't bundle it. 16:10:31 geppetto: +1 16:10:41 The more software I look at, the more I consider becoming a garderner... 16:10:50 He wants it called as a separate executable. That's fine. Things that want to use it should obey his wishes. 16:10:56 mbooth: +1 16:10:59 duct tape and bailing wire 16:13:15 So, I doubt we'd get +5 on a blanket exception here. 16:13:16 So, do we have a proposal here? I'm not clear on that 16:13:38 The proposal was for a blanket copylib exception for dcraw. 16:13:40 Yeh, I think we are all in favour of everything that includes this to have to use a bundled() 16:13:54 But also to has as few things as possible bundle it 16:14:28 As I wrote in the ticket, I would vote for an exception for libraw, assuming it's just not considered to be forking the dcraw code wholesale. 16:15:00 hi guys 16:15:04 sorry but I can't stay 16:15:06 #chair Rathann 16:15:06 Current chairs: Rathann geppetto limburgher mbooth orionp tibbs tomspur 16:15:10 have a bit of emergency at home 16:15:13 ok, no problem 16:15:30 if there are not enough votes, I'll vote in the tickets later 16:15:31 Yeh, I'd consider libraw a fork 16:15:32 bye 16:15:33 I haven't looked at the code yet, been AFK for a few weeks and getting caught up. Just updated to current where possible and backported the patch for f20. 16:17:35 Seems like it is a lot of work to port to libraw? 16:18:08 Yeah, it is. 16:18:21 Anyway, what else can we do here? 16:18:22 yeh, probably … but I don't see any other good options 16:20:40 We're not going to get to +5 for a blanket exception. 16:20:59 We could, I suppose, vote on an exception for libraw. 16:21:22 Otherwise I think we ask the various packages which bundle dcraw to document that. 16:21:37 Not sure it's worth it … given how forky it seems 16:21:43 I agree. 16:21:50 #action Everything using it should add a bundled(dcraw), until it's a true fork. 16:22:25 #action It's way too big and messy to be classified as a copylib though, any potential users should probably look at moving to libraw 16:22:39 #topic #528 Allow Mono 4.0 to be bootstrapped with monolite 16:22:40 .fpc 528 16:22:40 https://fedorahosted.org/fpc/ticket/528 16:22:42 geppetto: #528 (Allow Mono 4.0 to be bootstrapped with monolite) – fpc - https://fedorahosted.org/fpc/ticket/528 16:22:53 this seemed kind of trivial to me 16:23:08 I'm somewhat surprised we needed to get invovled to rebootstrap something 16:23:31 +1 -- seems sensible enough 16:23:38 Yeah. E_JUSTDOIT 16:23:38 +1 16:23:53 +1 16:23:53 +1 16:24:26 +1 - the guidelines say to contact the FPC 16:24:45 I think it is good to be aware of any bootstrapping 16:24:57 +1 16:24:59 Fair enough 16:25:01 #action Reboostrap mono with monolite binaries (+1:7, 0:0, -1:0) 16:25:12 #topic #527 AppData for Application Addons 16:25:13 .fpc 527 16:25:13 https://fedorahosted.org/fpc/ticket/527 16:25:13 * tibbs|w presses easy button. 16:25:14 geppetto: #527 (AppData for Application Addons) – fpc - https://fedorahosted.org/fpc/ticket/527 16:25:23 I haven't had time to look at this. 16:25:57 https://fedoraproject.org/w/index.php?title=User%3AVondruch%2FDraftAppDataGuidelines&diff=412575&oldid=412571 16:26:02 Is the new policy/diff 16:26:25 Does anyone else find the whole MUST and SHOULD thing annoying? 16:27:08 I know it comes from RFCs but I've always had a preference for just writing English without yelling where possible. 16:27:27 A little but I think it helps call attention to it for those with a tendency to skim. 16:27:31 There are minor grammatical errors which I could fix up later if approved. 16:27:46 it's probably better to yell a little bit in packaging instructions/policy 16:28:04 I can't see anything that makes me not want to +1 … so +1 16:28:25 This change basically documents what I have already been doing... so +1 16:28:58 Except I haven't been validating my metadata files... oops 16:29:01 Note also that "appdata-validate --relax" seems to have changed to "appstream-util validate-relax". 16:29:02 I think validating belongs to %install 16:29:17 tibbs: yeh, vond mentioned that in the ticket 16:29:25 +1 16:29:41 That is a "just do it" in any case. 16:30:28 Is there a better location for the AppData spec page besides hugsie's personal page on freedesktop? 16:30:46 The appstream spec page has an "official" location. 16:30:59 +1 16:31:02 Anyway, I'm just asking random questions. 16:31:06 +1 in any case. 16:31:23 Only AppData must be validated but not AppStreams? 16:31:43 Also the last section needs a rename, which I will take care of. 16:32:00 tomspur: My best guess is that appstream-util does both. 16:32:14 * tomspur would guess so too 16:32:34 Third section of the diff says that appdata must be validated with appstream-util, so.... 16:33:17 +1 on the guideline, the validation of appstream data can be added/asked for in the ticket 16:34:04 e.g. in the examples of usages for a *..metainfo.xml would be fine 16:34:33 * tomspur needs to go also soonish because of the holiday over here... 16:34:49 no problem … this is the lastof the new tickets 16:34:58 And I don't think we really have anythng to do on the old tickets 16:34:59 Which holiday is it, BTW? 16:35:07 I did make a little progress in some of them. 16:35:15 oh, cool 16:35:26 Did 527 pass? 16:35:38 it's really close atm. 16:35:45 but a couple of people haven't voted 16:35:48 6 +1s, no? 16:35:59 Ascension Thursday and Fathers Day 16:36:16 I get +5 16:36:27 Yeah, I see +5 as well. 16:37:15 No, +6; didn't catch mbooth's at teh end of the line. 16:37:29 Ohh, is that everyone now? 16:37:37 Seems so :) 16:37:46 #action AppData for application Addons (+1:6, 0:0, -1:0) 16:37:51 thought we had 7 at one point 16:38:00 Rathann came and went. 16:38:10 * geppetto nods 16:39:04 * geppetto shrugs 16:39:12 #topic Open Floor 16:39:29 tibbs: So any of 281/508/513 you want to talk about? 16:39:42 .fpc 126 16:39:44 tibbs|w: #126 (bundling exception for scintilla) – fpc - https://fedorahosted.org/fpc/ticket/126 16:39:49 ha 16:39:58 Oh, wait, we talked about this last week, didn't we? 16:40:05 yeh 16:40:09 * tomspur needs to go... sorry. See you next week 16:40:16 tomspur: see ya 16:40:17 There's really nothing else we can do to that one, I think. 16:40:30 This one also makes me want to become a gardener... 16:40:37 * orionp wonders what broke mock... 16:40:48 I mean, if there was a real scintilla package that someone was willing to maintain, perhaps two or three of the bundlings might be able to be cleaned up. 16:41:00 Certainly scite, because it doesn't modify the bundled copy. 16:41:05 And probably qscintilla. 16:41:17 But the rest, we may just have to live with. 16:41:32 Unless someone wants to grab the power and say we can start forcing change. 16:41:45 tibbs|w: How much work is it would a real scintilla package be? I mean, how often do new versions appear? 16:41:56 Every few months, I think. 16:42:02 It does have an active upstream. 16:42:18 I could maybe take it on, if it was low maintainence 16:42:29 I would suggest that it be a joint project between the qscintilla and scite maintainers. 16:42:35 If I could just hand out effort like that. 16:42:59 rdieter said he's been meaning to do it if he could find the time. 16:43:08 So there would probably be some help there. 16:43:31 But I haven't even looked at it, and that's the first step. I guess a static library would be preferable to the current state. 16:43:43 Indeed 16:43:54 Anyway.... 16:43:57 .fpc 529 16:43:58 tibbs|w: #529 (Bootstrap recipes for stages 1-3 in fedora git) – fpc - https://fedorahosted.org/fpc/ticket/529 16:44:05 Does anyone understand this at all? 16:44:17 I mean, I understand what they're trying to do, but not at all how they plan to do it. 16:44:42 Is this even in our remit? 16:44:50 They just want a git repo? 16:44:55 It depends on how they plan to do it, I think. 16:45:37 I don't think they want a git repo. … I think they want to do something to a bunch of git repos. for packages 16:45:44 If they're talking about basically importing some new packages, not our business unless they want to skip the review process and FESCo decided they want us involved in that. (WHich is a discussion for a bit later.) 16:46:11 If they're indeed going to go in and make changes to existing packages to add some macros or ifdefs or something then, yeah, that's our business. 16:46:28 But so far we just have a "you have to pass it to see it" kind of thing. 16:46:53 I _think_ they want to store a few extra files in Fedora git for some core packages, which will do something during RCM (or mass rebuilds? or somewhere else?) 16:47:11 It could be that they're asking if we would be amenable to accepting such a thing before they go working on it, but I doubt it. 16:47:21 ¯\_(ツ)_/¯ 16:47:38 If they just want to check other files into current packages.... they should feel free. 16:47:46 If they want to modify the spec files, please tell us how. 16:48:15 So we should ask all this in the ticket then 16:48:28 If they want to import specs under different names, that does currently violate the guidelines but I would be happy to give them an exception. 16:48:36 I've kind of been asking but haven't gotten many answers. 16:48:53 I will convert the questions we've come up with here into more direct questions for them. 16:49:06 There may be a bit of a language barrier here as well; I'm not sured. 16:49:12 I guess also point them to this discussion when asking the next question … so it's obvious we don't know what they want or why 16:49:12 "Moreover, I need approval/blessing for pushing the recipes to the fedora git as some owners/maintainers could take it as touching their sources without permission." -- just ask the maintainers? 16:49:53 Yeah, or just use provenpackager. I mean, if this is just some random extra files, jeez. 16:50:11 If they want to push some files into some core packages … I guess I'd +1 that … but they'd be much better off asking people so those maintainers know wtf those files are there for and don't just delete them 16:50:52 I don't even think we need to +1 that; it doesn't violate any existing guidelines to do that. 16:51:00 * geppetto nods 16:52:01 So, basically, if they're modifying existing specs, they should tell us how. If they're going to be uploading other things which are essentially specs, we should discuss it but I doubt we'd have any issue approving it. And if they're not doing either, then they should just go ahead. 16:53:31 Where is my python proposal? 16:53:39 Ah... 16:53:42 .fpc 526 16:53:44 tibbs|w: #526 (Mandatory python3 packaging when upstream supports python3) – fpc - https://fedorahosted.org/fpc/ticket/526 16:54:18 I thought that was on the agenda anyway. 16:54:30 Anyway, does anyone have any input? 16:54:49 Basically, if your python module supports python3, build it for python3. 16:54:57 I looked at it … I thought it was part of the py3 as default feature 16:55:00 I think it's probably a good idea, especially for new packages, for future-proofing. 16:55:03 so was a bit confused 16:55:27 If it was part of the py3 as default thing, I didn't see it get proposed to us. 16:55:33 The guidelines would have to change at some point. 16:55:47 Or have I still been misssing that requirement in the guidelines all along? 16:56:33 I mean … I just expected that when py3 was default then everything using python would be required/heavily-encouraged to move 16:57:07 Well, that's happening for F23, which has been a real thing for a while now, and yet.. no guideline change proposal. 16:57:12 Well, until I made one. 16:57:35 I'm + 16:57:38 +1 16:57:56 +1 obviously. 16:58:09 sure +1 16:58:51 +1 16:58:57 #topic #526 Mandatory python3 packaging when upstream supports python3 16:59:38 +1 16:59:54 #action Mandatory python3 packaging when upstream supports python3 (+1:5, 0:0, -1:0) 16:59:59 Well that was easy. 17:00:03 :) 17:00:10 #topic Open Floor 17:00:14 Also note the bit at the end. 17:00:16 https://github.com/fedora-python/packaging-guidelines/ 17:00:44 I guess github is as good a place as any, except it seems counterproductive to go back and forth between formats. 17:01:32 Also I did make some progress on 497. 17:01:39 The "clean up buildrequires" thing. 17:02:06 I floated it again on packaging and it seems like the feedback is positive, but the details are painfully difficult to pin down. 17:02:24 And I'm sort of running out of steam to push it forward. 17:02:55 It seems fine to me 17:03:21 At least if we want to move away from the current system … this seems like a great starting point 17:03:27 Indeed. 17:03:39 Really I just want to let releng decide what's in the buildroot and keep us out of it. 17:03:48 You want to vote on it? 17:04:01 Is the wording good enough now? 17:04:18 As I said, it seems fine to me 17:04:19 https://fedoraproject.org/wiki/User:Tibbs/BuildReqDraft 17:04:30 #topic #497 Clean up BuildRequires section; don't try to define the minimal build env 17:04:36 https://fedoraproject.org/wiki/User:Tibbs/BuildReqDraft 17:04:53 .fpc 497 17:04:54 Wait, I swear I changed it since that URL was posted. 17:04:55 geppetto: #497 (Clean up BuildRequires section; don't try to define the minimal build env) – fpc - https://fedorahosted.org/fpc/ticket/497 17:05:13 What the hell? 17:05:30 The wiki hates me, and I hate it. 17:05:44 Anyway, it's just the paragraph in comment 16, not what's currently on the wiki. Sorry. 17:06:14 Ok, +1 to comment 16 17:06:20 +1 obviously. 17:06:30 I like it +1 17:07:44 +1 17:07:51 * mbooth likes conciseness 17:08:14 limburgher: vote? 17:08:34 I think I'm +1. 17:08:40 #action Clean up BuildRequires section; don't try to define the minimal build env (+1:5, 0:0, -1:0) 17:08:49 #topic Open Floor 17:09:01 Ok … I think we are probably good now 17:09:07 Yeah, I'm out. 17:09:14 Oh, shit. 17:09:25 ? 17:09:28 There was one thing I wanted to make us aware of. 17:09:43 Have to dig it up. 17:10:02 .fesco 1435 17:10:04 tibbs|w: #1435 (Approving exceptions to the package review process) – FESCo - https://fedorahosted.org/fesco/ticket/1435 17:10:27 I filed that with fesco, but the details may come back to us. 17:11:02 * limburgher sighs 17:11:05 Basically, if someone wants to do a mass import or work around the arduous package review process (like, dunno, a texlive split or importing an scl stack if that was a thing). 17:11:31 Should be rare, but it is packaging and we might end up being asked to approve them. 17:11:47 * geppetto nods 17:12:04 Anyway, nothing really to discuss; I just wanted to make sure folks were aware of it. 17:12:35 I will write the process if it comes down to that, no big deal. 17:12:49 Thanks tibbs|w, CC'd myself 17:12:59 limburgher: Why the sigh, BTW? 17:13:26 tibbs|w: Thinking about texlive, that's all. 17:13:30 yeh, me too … we can all now crash into each other on the Cc bandwagon ;) 17:13:31 Ah, yeah. 17:14:25 Ok, well I'll close the meeting in a minute unless any brings up anything else 17:14:26 I think if we had this we wouldn't have had the current texlive situation. 17:14:36 And maybe the scl thing wouldn't have hit a brick wall. 17:14:41 Have a nice lunch, and I'll see you next week. 17:14:46 Thanks, folks. 17:14:50 * limburgher waves 17:15:32 #endmeeting