16:00:05 #startmeeting FESCO (2017-01-20) 16:00:05 Meeting started Fri Jan 20 16:00:05 2017 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:05 The meeting name has been set to 'fesco_(2017-01-20)' 16:00:05 #meetingname fesco 16:00:05 The meeting name has been set to 'fesco' 16:00:05 #chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann 16:00:05 Current chairs: Rathann dgilmore jforbes jsmith jwb kalev maxamillion nirik sgallagh 16:00:05 #topic init process 16:00:11 hi 16:00:19 who all is around? :) 16:00:20 .hello maxamillion 16:00:21 maxamillion: maxamillion 'Adam Miller' 16:00:25 .hello jforbes 16:00:27 jforbes: jforbes 'Justin M. Forbes' 16:00:28 hi everyone 16:00:49 sgallagh said he would be a few min late. 16:02:10 .hello rathann 16:02:10 * nirik waits for at least one more 16:02:11 Rathann: rathann 'Dominik Mierzejewski' 16:04:05 .hello sgallagh 16:04:06 sgallagh: sgallagh 'Stephen Gallagher' 16:04:24 alrighty. Thats 5, so lets go ahead and start. ;) 16:04:33 #topic #1635 F26 Self Contained Changes 16:04:33 .fesco 1635 16:04:33 https://pagure.io/fesco/issue/1635 16:04:35 nirik: Issue #1635: F26 Self Contained Changes - fesco - Pagure - https://pagure.io/fesco/issue/1635 16:04:40 .hello jsmith 16:04:41 jsmith: jsmith 'Jared Smith' 16:04:42 Sorry I'm late 16:04:43 there's several of these, shall we do them one at a time? 16:04:47 no worries 16:04:53 hola 16:04:58 Do we want to cover the fontconfig one separately? 16:05:02 (First, or later?) 16:05:06 sure, lets do it first 16:05:15 sgallagh: you talked with folks about that? 16:05:22 Yes, see the comment in the ticket 16:05:28 yeah. 16:05:28 I can summarize here, though. 16:05:57 if you like. I'm +1 at this point 16:06:00 The short version is that I think the primary confusion in the debate is the word "cache" and the different participants' definitions thereof. 16:06:12 * kalev appears in a poof of magic. 16:06:14 sorry guys, a bit late here 16:06:15 I read the summary in the ticket, +1 here as well 16:06:16 yes, it makes sense now 16:06:33 +1 from me too, makes a lot of sense now 16:06:36 thanks sgallagh for checking it 16:06:37 +1 to the fontconfig index from me 16:06:40 is the index portable between arches? 16:06:42 +1 here as well 16:06:53 if yes, then perhaps /usr/share/fontconfig would be a better location 16:07:15 while not ideal ostree could run fc-cache on boot for changes 16:07:23 but that data can be moved 16:07:41 dgilmore: I suggested that as well, but they would prefer to avoid special-casing things 16:08:02 If they were going to do a special-case, they'd rather just add a symlink for the ostree case. 16:08:10 sgallagh: Agreed... 16:08:13 thats +5, other votes? 16:08:14 Rathann: I did not think to ask that question. 16:08:45 I'm +1 to my own proposal, if that was unclear. 16:09:11 +1 anyway 16:09:53 sgallagh: we could make everyone run it via systemd but sure 16:10:54 #agreed Fontconfig cache directory change approved (+7,0,0) 16:11:17 I am honestly not sure how to vote on it 16:11:27 ok, we have also Transdiff and Automated AMI test and release. 16:11:59 Transdiff doesn't warrant a change in my opinion 16:13:14 i thin the ami testing means fed-img not fedming 16:13:26 fed-img is teh tool that uploads the images 16:13:27 I am +1 to both, personally 16:13:51 also, Transdiff is more for upstreams than for package maintainers 16:14:05 well, without the change people may not know transdiff exists to run it? but yeah... seems more end user than changey 16:14:18 the change also directly effectes releng even though it says it doesn't :( 16:14:20 +1 to both as well 16:15:10 the ami uploading I think needs some more detail but I am +1 to the idea 16:15:20 +1 to both 16:15:39 +1 to AMI, -1 to Transdiff 16:15:52 I think transdiff really should be done in taskotron, or elsewhere, but that could be done in addition 16:16:00 Changes are not just for marketing 16:16:08 well, or transdiff could just be a release note. ;) 16:16:12 exactly 16:16:14 Rathann: I'm curious, why are you against transdiff? 16:16:47 dgilmore: taskotron integration would be very good there I agree. 16:17:02 I don't see anything in that proposal that would require a Change proposal 16:18:04 are we expecting users to run transdiff? 16:18:09 that was mentioned on the list and they were going to investigate taskotron integration... 16:18:29 dgilmore: that seems like the case yeah... 16:18:52 "oh, my translations are out of date" "hey upstream, please do a new release" 16:19:09 I'm +1 to both transdiff and AMI testing 16:19:30 I am not opposed to it. I think there is different interaction points we should look at 16:19:44 but I will give it a +1 also 16:19:50 I guess I can be +1 to both 16:20:22 I'm +1 to AMI ... still pondering Transdiff 16:20:30 * nirik counts 16:20:41 transdiff I really am on the fence about it beinga change 16:20:47 I think its a useful tool 16:21:05 #agreed Automated AMI test and release change is approved (+8,0,0) 16:21:13 it's more about marketing really 16:21:19 do we want to punt for more list discussion? it kind of petered out... 16:21:32 I think it's an useful tool, I just don't fully understand the scope of the Change ... are we just introducing that package to Fedora? is this being incorporated in the build/release pipeline? 16:21:34 but I think taskotron, and test cases in openqa are probably better places for integration and can get things reported and fixed more rapidly 16:21:41 I know Rathann asked why it should be a change and never really got an answer 16:21:41 not to mention the proposal contains "More details TBD", "Will provide later." etc. 16:22:10 maxamillion: yes, just the package. no to anything further at this time 16:22:20 yes, it looks like my question was silently ignored 16:22:22 or missed 16:22:37 Rathann: probably no answer 16:22:42 not sure the change owners are here 16:22:43 proposal: wait a week for this change for more discussion on list 16:22:49 as they would have to answer it 16:22:52 nirik: +1 16:23:10 +1 16:23:18 +1 my own proposal 16:23:32 +1 16:23:44 +1 16:23:52 +1 I can agree on that 16:24:02 +1, seems fair 16:24:25 #agreed will wait a week for more discussion on Transdiff. (+7,0,0) 16:24:37 #topic #1665 Unresponsive maintainer: affix 16:24:37 .fesco 1665 16:24:37 https://pagure.io/fesco/issue/1665 16:24:38 nirik: Issue #1665: Unresponsive maintainer: affix - fesco - Pagure - https://pagure.io/fesco/issue/1665 16:24:55 so I'm not sure this went through the process... 16:25:36 but they are definitely non responsive in bz 16:26:40 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XOX7WLYKUY2LZ6H7M3WPEUF7ZON3HU2K/ 16:26:57 nirik: an email was sent to devel@ in November last year 16:26:58 ah, there was a devel post, ok. 16:27:07 ahh, good 16:27:30 so, sure +1 to orphaning 16:27:33 would also be nice to add unresponsive maintainters to the pagure ticket, so they can see what's going on 16:27:34 nirik: and it is not the first time he/shee has come up non responsive 16:27:36 affix hasn't logged in to FAS since May last year 16:27:38 but +1 anyway 16:27:38 I'm always in favor of handing a package over to someone willing to actually maintain it. 16:27:39 +1 16:27:42 https://bugzilla.redhat.com/show_bug.cgi?id=1145830 16:27:42 so, +1 16:28:04 https://pagure.io/fesco/issue/1479 16:28:12 +1 16:28:21 +1 here 16:29:08 +1 16:29:20 apologies, need to step afk for a couple minutes 16:29:24 #agreed will orphan affixes packages (+7,0,0) 16:29:38 #topic #1668 F26 System Wide Change: GCC7 16:29:38 .fesco 1668 16:29:38 https://pagure.io/fesco/issue/1668 16:29:39 nirik: Issue #1668: F26 System Wide Change: GCC7 - fesco - Pagure - https://pagure.io/fesco/issue/1668 16:29:41 +1 here 16:29:53 +1 as well, would be good to get this as soon as possible in rawhide 16:29:54 +1 top gcc 16:29:56 to 16:29:58 +1 16:30:41 +1 as well 16:30:43 kalev: agreed sooner is better 16:31:26 +1 16:31:43 jsmith: what say you? 16:31:59 +1 16:32:14 #agreed GCC7 change is approved (+7,0,0) 16:32:15 (Sorry, got pulled into a phone call for ${DAYJOB}) 16:32:22 #topic #1669 F26 System Wide Change: Parallel Installable Debuginfo 16:32:22 .fesco 1669 16:32:22 https://pagure.io/fesco/issue/1669 16:32:24 +1 here 16:32:24 nirik: Issue #1669: F26 System Wide Change: Parallel Installable Debuginfo - fesco - Pagure - https://pagure.io/fesco/issue/1669 16:32:37 very big +1 here 16:33:22 +1 16:33:23 isn't it duplicate of F25 change? 16:33:33 +1 from me... 16:33:37 It wasn't done in time for f25. 16:33:38 +1, this is an area that has been lacking in improvements for a while 16:33:59 +1, but I'm slightly concerned about potential cleanup... debuginfo packages are BIG 16:34:54 nirik: ah, right. Thought that it's some similar, but not same 16:35:05 #agreed Parallel Installable Debuginfo Change is approved (+6,0,0) 16:35:08 sgallagh: what cleanup do you mean? 16:35:16 +1 from me as well 16:35:23 #undo 16:35:23 Removing item from minutes: AGREED by nirik at 16:35:05 : Parallel Installable Debuginfo Change is approved (+6,0,0) 16:35:27 #agreed Parallel Installable Debuginfo Change is approved (+7,0,0) 16:35:38 kalev: Today, if I install a newer version of the glibc debuginfo, it removes the older one, saving space 16:35:39 I think folks that know to use debuginfo packages can manage them... 16:35:45 With this change, I now have two large packages. 16:35:59 nirik: Yeah, which is why I voted +1, but it's still in the back of my mind 16:36:02 sgallagh: do you? 16:36:32 * nirik typically installs, debugs and removes. 16:36:52 anyhow, anything more on this? 16:36:56 * maxamillion is back ... apologies 16:37:10 Shall we move on? 16:37:12 #topic Next week's chair 16:37:17 who wants it next week? 16:37:28 I can do it 16:37:38 will we have enough people for the meeting next week?> 16:37:48 ahh, good question 16:37:59 * maxamillion will not be available 16:38:00 * nirik should be around 16:38:00 I will not be attending 16:38:08 * dgilmore will be at devconf 16:38:09 * jforbes will be here 16:38:15 * kalev will be here 16:38:22 and at fosdem the week after 16:38:27 I'll take Feb 03 though 16:39:01 so sounds like we won't have enough people next week? 16:39:07 sounds like it 16:39:24 kalev: you want feb 3rd or want sgallagh to have it? 16:39:35 jsmith: will you be here next week? 16:39:35 nirik: sgallagh can have it 16:39:42 ok. 16:39:54 dgilmore: I should be, yes? 16:40:03 #info people traveling next week so no meeting on 2017-01-27 16:40:08 so likely only 4 people 16:40:17 #info sgallagh will chair the 2017-02-03 meeting 16:40:23 dgilmore: By "here", I mean in IRC, not "there" physically 16:40:43 We have a number of old tickets... I didn't ping any of them but we could address some if we want... 16:41:05 https://pagure.io/fesco/issues 16:41:15 jsmith: that is what I was asking 16:41:37 Might be good to do a bit of housekeeping 16:42:02 yeah, I didn't want to last night... was late, but I or someone could ping on them soon. 16:42:09 Would be good to get some done. 16:42:17 Anyhow, that takes us to... 16:42:20 #topic Open Floor 16:42:21 I do not think we will get a good answer for https://pagure.io/fesco/issue/1444 and given our future paths it seems like it may no longer be relevant 16:42:23 anything for open floor? 16:42:51 dgilmore: indeed. 16:43:50 nirik: I will close it 16:43:58 fine with me. :) 16:44:08 ack 16:44:15 ok, if nothing else will close out in a minute%rand 16:44:34 Nothing from me for the open floor 16:45:23 ok, thanks for coming everyone! 16:45:26 #endmeeting