16:58:45 #startmeeting FESCO (2014-05-14) 16:58:45 Meeting started Wed May 14 16:58:45 2014 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:58:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:58:47 #meetingname fesco 16:58:47 The meeting name has been set to 'fesco' 16:58:50 #chair abadger1999 dgilmore mattdm mitr notting nirik pjones t8m sgallagh mmaslano jwb 16:58:50 Current chairs: abadger1999 dgilmore jwb mattdm mitr mmaslano nirik notting pjones sgallagh t8m 16:58:53 #topic init process 16:58:55 hi 16:58:58 .hellomynameis sgallagh 16:58:59 sgallagh: sgallagh 'Stephen Gallagher' 16:59:10 #info pjones will be unable to attend while at UEFI hackfest 16:59:12 Hello all 16:59:21 morning. I'm here, but also poking at the pkgdb upgrade thats still ongoing, so might be slow. 16:59:27 * notting is here, although very behind on e-mail/trac/etc 16:59:52 Looks to be a non-controversial agenda today. 16:59:53 I'm not really here -- dealing with pkgdb upgrade in infra. 17:00:13 If there's something that needs my vote to pass I can try to look back in 17:03:16 hi! 17:03:26 Anyone seen dgilmore today? 17:04:11 Ok, let's proceed 17:04:18 #topic #1178 Fedora 21 scheduling strategy 17:04:19 .fesco 1178 17:04:21 sgallagh: #1178 (Fedora 21 scheduling strategy) – FESCo - https://fedorahosted.org/fesco/ticket/1178 17:04:56 jreznik_ would like us to schedule the mass-rebuild 17:05:18 I'd prefer to have dgilmore's and nirk's attention for this, so maybe defer a week? 17:05:32 * nirik looks to see if we have all the info. 17:05:39 sgallagh, definitely +1 17:05:39 might be good to defer yeah... 17:05:54 sgallagh, +1 to defer that is 17:05:56 +1 wait for dgilmore 17:05:58 and propose a date and get the affected changes to weigh in 17:05:59 +1 17:06:12 fine with deferring, or doing in ticket 17:06:46 nirik: Yeah, contacting the Change owners would be a good idea. 17:06:50 Volunteers? 17:07:08 2014-06-09 (as proposed in the releng ticket) might be ok. 17:07:23 I can talk with dgilmore and we can update the ticket(s) with proposals. 17:07:50 nirik: That sounds like the best move 17:08:05 #action nirik and dgilmore to coordinate and make a recommendation in the ticket 17:08:26 Good enough for now? 17:08:53 sure 17:08:55 sgallagh: sorry, I was out 17:08:59 #topic #1250 F21 Self Contained Changes 17:09:00 .fesco 1250 17:09:01 sgallagh: #1250 (F21 Self Contained Changes) – FESCo - https://fedorahosted.org/fesco/ticket/1250 17:09:25 jreznik_: Were there any self-contained changes for this week? 17:09:34 nirik: I'll watch the ticket 17:09:47 sgallagh: no 17:09:54 ok, that was easy :) 17:10:01 * dgilmore is here 17:10:06 a few leftovers were announced today 17:10:10 #topic #1291 F21 System Wide Change: BerkeleyDB 6 - https://fedoraproject.org/wiki/Changes/BerkeleyDB_6 17:10:10 .fesco 1291 17:10:11 sgallagh: #1291 (F21 System Wide Change: BerkeleyDB 6 - https://fedoraproject.org/wiki/Changes/BerkeleyDB_6) – FESCo - https://fedorahosted.org/fesco/ticket/1291 17:11:06 Has upstream weighed in on the symbol problem? 17:11:17 sgallagh: btw. for contacting change owners for mass rebuild, already started pinging a few but any help welcomed :) 17:12:02 jreznik_: they should all be cc'ed on the releng ticket no? 17:12:11 jreznik_: we need all the side tags merged back into f21 first 17:12:12 Also, I heard something this past week about the AGPL change possibly resulting in issues for users too 17:12:41 sgallagh: well AGPL will require users to make thier source available 17:13:21 so if you have a webapp thats inhouse using bdb you will need to make your webapps sources available 17:13:23 nirik: should be but as QA guys says - it's s* word 17:13:28 huh, that's pretty bad 17:13:36 well, or switch to compat-db 17:13:42 right 17:13:43 Yeah, that's bordering on unacceptable 17:14:08 or switch to a upstream that doesn't relicense in crazy ways. ;) 17:14:15 also, it's not just *web* apps. it's anything network. 17:14:24 There's going to be a lot of fallout from that. 17:14:24 which could hit a lot of db-using things 17:14:25 I honestly think we should stay at db5 17:14:30 That's why the proposal is to have both, that’s not the issue under discussion AFAIK 17:14:42 Proposal: reject BDB 6 for Fedora 21 while the maintainers and upstream sort out the issues. 17:14:51 It’s just that we haven't heard from upstream 17:15:21 mitr: Having both doesn't necessarily solve the problem if we default to upgrading to 6 17:15:40 sgallagh: That has already been resolved by the owner promising to audit every package 17:16:02 mitr: That doesn't help anyone building on top of Fedora 17:16:22 mitr, if the agpl seriously changes things even for users it is bad to switch the default for any dependent app 17:16:26 sgallagh: -1 I can’t see that anything has changed regarding licensing, and I haven’t seen that the delay in getting the versioning plan implemented is problematic enough to warrant such a drastic action 17:16:28 Using packages from CPAN/PyPI/NPM/etc 17:16:48 (alternatively, "reject and allow them to sort out and reaply" and "defer" are the same thing except one is more emotionally charged) 17:16:53 users can very easily get to a point where they unkowingly violate the license 17:17:22 That can happen with all the upstream tarballs either way; we can wash our hands of it or actually help solve that problem for upstreams 17:17:38 sgallagh, I'd still prefer deferring the rejection at this time and give maintainers chance to sort it out 17:17:46 Carrying both is only acceptable in my opinion if the upgrade path does not force anyone onto 6 17:17:58 sgallagh, +1 17:18:23 sgallagh so that argues for new name for the 6 package 17:18:33 mitr: In general, I agree with you. However BDB is somewhat exceptional in that it's used everywhere (often inside a dependency that you don't know about) 17:18:56 mattdm: I was trying to avoid mandating an implementation, but yes that's the most likely approach 17:19:47 mattdm: db6/db6-devel isn't without precedent 17:20:00 indeed 17:20:06 I’m not really happy with the implication that the longer a FESCo ticket stays open, the more likely it is for FESCo to reverse its position without new facts... OTOH if it compelled maintainers to respond 17:20:31 Well, the longer it stays open, the less comfortable we are with landing the change in a particular cycle 17:20:52 *stays open with unanswered questions and known issues 17:20:53 we can't always avoid upstream license changes for users... 17:21:19 nirik: No, but when we have advance knowledge we can try to mitigate it 17:21:27 nirik: we can't, but this particular change has very wide ranging implications 17:22:24 I suppose. It kinda sets a nasty precident if we try and always protect users from changes tho... but I agree this is a widespread package. 17:22:49 anyhow, last time I asked the change owner questions they were quick to answer... we were waiting for upstream this time tho right? 17:23:03 nirik: yeah, seems upstream is quiet 17:23:17 proposal: wait another week for upstream response 17:23:22 notting: +1 17:23:22 +1 notting 17:23:26 notting, +1 17:23:47 +1 17:24:21 #info Waiting one more week for upstream response 17:24:52 #info FESCo is concerned about the wide-ranging impact that the license change to AGPL may cause and is considering how to proceed. 17:24:52 notting: +1 17:25:18 #topic #1307 F22 System Wide Change: Default Local DNS Resolver - https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver 17:25:19 .fesco 1307 17:25:20 sgallagh: #1307 (F22 System Wide Change: Default Local DNS Resolver - https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver) – FESCo - https://fedorahosted.org/fesco/ticket/1307 17:25:33 so, was this for f21? 17:25:50 no its F22 17:25:56 this is for F22 AFAIK 17:26:06 plus we already asked for some stuff. 17:26:07 right. ok. 17:26:28 i think this should be taken off the agenda for 6 months or so 17:26:38 yep 17:26:40 ok 17:26:52 There will be a meeting discussing this on Thursday next week, so 2 weeks at least seems necessary 17:26:59 didn't see any answers to the docker question. so maybe remove meeting keyword until we have those? 17:27:08 I dropped the 'meeting' keyword for now 17:28:10 #topic Next week's chair 17:28:19 sgallagh, I can do it 17:28:28 #undo 17:28:28 Removing item from minutes: 17:28:51 #info Taking off the meeting agenda until we receive feedback on the container issues 17:28:54 #topic Next week's chair 17:29:03 #info t8m to chair next week's meeting 17:29:06 #topic Open Floor 17:29:34 sgallagh: id like to go back to mass rebuild, i was finishing up lunch at the start of the meeting 17:29:51 #topic #1178 Fedora 21 scheduling strategy 17:30:03 for mass rebuild we need all the things with side tags to be done and merged back in 17:30:04 dgilmore: You have the podium :) 17:30:19 some of them seem to be taking overly long 17:30:28 and not really doing any work 17:30:40 * nirik nods sadly. 17:30:51 we could give them a deadline if we schedule the mass rebuild? 17:31:03 the python 3.4 guys did ask me to rebuild everything for them 17:31:27 i had to fix some issues for them last week 17:31:38 there was some packaging bugs in some python packages 17:32:12 how many side tags do we have? /me looks 17:32:18 too many 17:32:19 dgilmore: Say it ain't so! ;-) 17:32:23 ruby tcl and puthon 17:32:25 python 17:32:40 f21-llvm f21-python f21-ruby f21-tcl 17:32:41 tcl has been there for 6 months 17:32:48 f21-xorg 17:32:53 xorg is done 17:32:55 (but I thought that one was done) 17:33:00 ok 17:33:06 llvm is done too right? 17:33:16 yes 17:33:24 active is python and tcl 17:33:29 http://koji.fedoraproject.org/koji/buildtargets 17:33:49 deadline would be nice to set -> miss deadline, you're not going into f21... 17:34:22 there's also boost, pmachata put it into the ticket 17:34:23 jreznik_: well we merge the tag in, remove the target and they deal with breakages in rawhide 17:34:40 jreznik_: boost cant be handled in mass rebuild 17:34:47 it will need a side tag 17:34:54 boost and python have quite a bit of overlap, would be nice to finish one before the other one starts 17:34:56 dgilmore: he told me it's done this way 17:35:02 it can be done before or after the mass rebuild 17:35:08 jreznik_: what way? 17:35:25 how about we give them until the 26th, and do the mass rebuidl on jun 9th 17:35:35 dgilmore: part of mass rebuild, if not, better... petr told me it was done as part of mass rebuild all the time 17:35:50 but seems he has short memory :) 17:35:55 jreznik_: its not possible 17:36:18 jreznik_: and its never been done as part of the massrebuild 17:36:35 dgilmore: ok, for some reason he was confused, doesn't matter now 17:36:44 jreznik_: it involves soname bumps and build ordering 17:36:52 dgilmore: I get it 17:36:54 the mass rebuild goes from a-Z 17:37:10 and the builds of the mass rebuidl do not land in the buildroot 17:37:18 we put them in a side tag 17:37:26 and then merge them in when done 17:37:58 I wouldnt be oppsosed to writing tooling to do mass rebuilds for soname bumps 17:38:07 but we do not have that today 17:38:14 sure 17:38:58 nirik: 26th seems ok, if communicated now and I've been asked by a few people to include it in the schedule so they know 17:39:20 id rather start the mass rebuild on a monday or a friday 17:39:36 last time i started friday night and it was done monday morning 17:39:47 I'd like to suggest that boost rebuild is better to land _before_ the mass rebuild 17:39:50 the reason is that boost ships a lot of it's libraries in header only form 17:39:54 and without a mass rebuild, it can be hard to be sure all consumers have been rebuilt 17:40:06 * nirik thinks mass rebuild will be faster yet this time. we have more builders. 17:40:20 dgilmore: Jun 9 is Monday 17:40:41 * dgilmore looked at the wrong month 17:40:48 I looked at July 17:41:06 so i think id rathe do it June 6th 17:41:24 then we should be able to merge it back in Monday the 9th 17:43:00 fine with me 17:43:07 is the 26th ok for a side tag deadline? 17:43:18 lets aim to have all the side tags merged back by MAy 26th 17:43:31 its fine by me 17:43:41 we can have a weeks leeway 17:43:46 hopefully boost can get done by then too 17:44:34 kalev: can you get onto the boost guys to get the side tag in? 17:44:46 dgilmore: I'll talk to Petr 17:45:22 yeah, that would be better, I haven't had any contact with the boost people 17:45:45 jreznik_: cheers 17:48:20 any objections to that plan? 17:48:32 I'm good with it 17:48:35 proposal side tags done May 26th Mass rebuild June 6th 17:48:52 +1 17:49:32 +1 17:49:35 im +1 obviously 17:49:40 +1 17:49:42 +1 17:49:54 mattdm: notting: pjones: 17:50:03 * mattdm wakes up 17:50:07 sorry +1 17:50:09 sure, +1 17:50:23 Still not present. 17:50:39 #agreed Side tags must complete their builds by May 26th. The mass rebuild will take place on June 6th. (+7, 0, -0) 17:50:45 #topic Open Floor 17:50:51 Anything for open floor this week? 17:50:52 could you please announce it? better to have it written by you guys 17:51:01 and I'll update schedule with dates 17:51:24 dgilmore, nirik: ^^^ 17:51:29 jreznik_: sure 17:51:40 dgilmore: thanks! 17:53:29 I'll close out the meeting in one minute if there is nothing else 17:54:40 Hey look, we kept a FESCo meeting under an hour! 17:54:42 #endmeeting