14:34:27 #startmeeting RELENG (2014-10-13) 14:34:27 Meeting started Mon Oct 13 14:34:27 2014 UTC. The chair is dgilmore-bne. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:34:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:34:46 #meetingname releng 14:34:46 The meeting name has been set to 'releng' 14:34:46 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson 14:34:46 Current chairs: bochecha dgilmore dgilmore-bne masta nirik pbrobinson sharkcz tyll 14:34:47 #topic init process 14:34:58 hi there 14:35:00 * nirik is here, but still reading email barge. 14:37:42 lets see if anyone else turns up 14:37:58 * pbrobinson is here 14:40:50 okay we have 4 14:41:06 #topic Secondary Architectures updates 14:41:11 #topic Secondary Architectures update - ppc 14:42:27 so RC1 went out last week 14:42:57 hows the testing? 14:42:59 awaiting feedback, we need another RC with some anaconda related fixes I believe but other than that over all it's positive 14:43:11 awesone 14:43:18 awesome 14:44:13 so hopefully we'll have Alpha out soon and we can move on to beta 14:44:30 EOF 14:45:25 cool 14:48:41 #topic Secondary Architectures update - s390 14:49:03 any sign of sharckcz today? 14:49:08 he's been about 14:49:23 network here i being crapp 14:49:33 I kicked off a s390 signing rung yesterday morning. Currently at 13727/66544 14:49:47 for f-21 tag 14:49:58 okay 14:50:01 thanks 14:50:25 #topic Secondary Architectures update - arm 14:50:27 while i know he's only aiming for beta I figured it was worth catching up as it's likely 4-5 days 14:50:44 similar to PPC Alpha RC1 went out yesterday 14:50:53 pbrobinson: yeah, its going to take awhile 14:51:09 only one report of issue and that's for updating the efi boot records 14:51:49 but it's only if it's not a clean install I believe and there's a manual work around 14:52:37 other than that aarch64 is looking pretty good 14:52:59 pbrobinson: [B[B[B[B[B[B[B[B[B[B[B[B[B[B[B[B[B 14:53:04 gahh 14:53:06 :) 14:53:18 what time is it in bne? 14:53:29 pbrobinson: thats odd, last i did a install the efi vars was nit clean and it all was updated fine 14:53:36 nearly 1am 14:54:02 yea, so at the moment I don't believe it's a blocker to get RC out as it appears to be fairly corner case 14:54:38 so I think if nothing else comes up we'll call Alpha gold and move on to beta 14:55:00 it doesnt sound like an alpha blocker, might want to double check with qa 14:55:34 there's a manual work around too 14:56:51 yeah, I think it should be okay 14:57:49 ultimately we'll be straight into beta TCs 14:58:11 dgilmore-bne: you might need to send an email out about that time change 14:58:30 pbrobinson: yeah. we discussed it in the meeting 14:58:43 i should have changed fedocal 14:58:59 #topic #5931 [Proposal] Move new branch and unretire requests to pkgdb2 14:59:10 dgilmore-bne: I remember, I thought it was actually moved forward 2 hours 14:59:20 https://fedorahosted.org/rel-eng/ticket/5931 14:59:35 pbrobinson: i suggested 2 it seemed 1 worked better for others 15:01:08 pingou: so the updates in the ticket look okay 15:01:48 * pingou here 15:02:22 dgilmore-bne: if you have more checks you want to see automated, let me know 15:02:45 and then, there is the question about new epel branch: https://lists.fedoraproject.org/pipermail/rel-eng/2014-October/018554.html 15:03:51 once we decide on this, the remaining question is: when do we want to it to land ? 15:03:54 pingou: epel is a special beast 15:04:00 clearly is :) 15:06:14 pingou: so el7 has acls coppied from el6 if the exist but git from f19 if it exists 15:07:03 pingou: el6 we used to copy acls from el5 and branch from f12 if it exists 15:07:22 but as the fedora release goes eol its much less relevant 15:08:05 pingou: we need to make sure a epel package is not in rhel unless its not on all arches 15:08:42 there is also the case where some maintainers choose not to look after epel and are okay with others doing so 15:08:44 dgilmore-bne: what about checking if it's in CentOS for that ? 15:08:58 pingou: its not enough 15:09:13 pingou: centos is x86_64 only 15:09:46 ok 15:09:58 I was actually under the impression that we have no way of checking if something is in RHEL automatically 15:10:39 we would have to write something 15:11:03 I can write it, but I don't know where to look for the info 15:11:13 we have rhel mirrored for epel arches 15:11:26 we would need to write something to grab the metadata 15:11:30 publicly accessible? 15:11:33 no 15:11:35 k 15:11:39 internal in phx2 15:12:02 I can query yum's metadata sure 15:12:53 dgilmore-bne: let's figure this out by email later 15:14:17 okay 15:14:39 so is left the question about the epel branches 15:15:05 how do we create them? 15:16:40 i think from the fedora they rhel branched form 15:16:42 from 15:16:54 if it doesnt exist master 15:17:28 hard-coded ? 15:17:41 what about allowing the maintainer to specify it in the SCM request? 15:17:44 epel7 == f19 (w/ fallback to master) ? 15:17:53 with some defaults 15:18:09 sharkcz: that was my idea at first, but I can't get the info from pkgdb to the script running from a fedmsg 15:18:11 sharkcz: a valid option 15:18:45 that's where tyll 's idea to just create the new branch and point it to the first commit ever in the repo came in 15:18:49 * nirik doesn't much care. I often have to sync to master. 15:18:49 which is also fine 15:20:54 im not too fazed 15:20:54 * sharkcz agrees 15:21:05 as long as maintainers can easily do what they want 15:21:06 with tyll's idea 15:21:30 * pingou searches `fazed` in a australian -> us dic 15:22:11 ok, so let's try tyll 's idea and let see how that turns out :) 15:22:28 sure, +1 15:22:53 lets look into it 15:23:01 so once this fix is in, we should be all set infra-wise 15:23:15 we have 10 minutes more. I really want to sleep 15:23:24 ETA: F21 release? 15:23:47 nirik: should we be bold and try to land this at the same time we land pkgs01 on el7 with gitolite3? 15:23:55 ha. 15:24:08 well, I'd say after f21 in any case, but doesn't need to be the exact same time 15:24:20 (although we could likely land the fedmsg-based branch handling before) 15:25:22 I think we want to wait until after f21... don't want to cause much disruption... 15:25:42 sure, wfm :) 15:26:24 really dont want to break anything 15:27:37 anything else? 15:28:02 just if you think of other checks you would like to run automatically :) 15:28:18 otherwise, I'm good to go :) 15:28:25 okay will think about what we can automate 15:28:34 #topic open floor 15:28:42 i have one thing 15:28:49 What about https://fedorahosted.org/rel-eng/ticket/6016 ? May I proceed or do you need more info about that? 15:28:58 does someone want to run next weeks meeting? 15:28:58 * pbabinca is here obviously 15:29:30 I have to be at the airport early Tuesday, to catch my flight to FUDCon LATAM 15:29:56 pbabinca: we are out of timev:( 15:30:14 I guess I could run the meeting next week... 15:30:15 dgilmore-bne, np. That isn't really a problem 15:31:09 pbabinca: lets see about coming up with a plan 15:31:33 nirik: thanks https://fedoraproject.org/wiki/ReleaseEngineering/Meeting_Process 15:31:43 we switched up secondaries this week 15:31:54 ok. Will try and do so... 15:32:03 anyone have anything else? 15:32:41 not from me 15:33:57 #endmeeting