15:37:05 #startmeeting RELENG (2016-03-14) 15:37:05 Meeting started Mon Mar 14 15:37:05 2016 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:37:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:37:05 The meeting name has been set to 'releng_(2016-03-14)' 15:37:05 #meetingname releng 15:37:05 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson pingou maxamillion 15:37:05 The meeting name has been set to 'releng' 15:37:05 Current chairs: bochecha dgilmore masta maxamillion nirik pbrobinson pingou sharkcz tyll 15:37:08 #topic init process 15:37:30 .hello maxamillion 15:37:30 maxamillion: maxamillion 'Adam Miller' 15:38:03 morning 15:38:20 * pbrobinson waves 15:38:32 * masta is here 15:38:47 sorry for those who this is an hour early 15:40:08 oh ritght 15:40:50 dgilmore: is it technically meeting time or did we jump the gun? (not sure if the meeting is held in UTC or if it travels around with DST) 15:41:19 maxamillion: it travels around with dgilmore ;-) 15:41:23 maxamillion: it si 15:41:26 it is 15:41:30 rgr 15:41:37 maxamillion: the meeting is always 10:30am US Central 15:42:31 lets get started 15:42:39 #topic Secondary Architectures updates 15:42:57 lets start with generic secondary arch discussions 15:43:17 I know pbrobinson got pungi composes working for ppc and aarch64 15:43:21 dgilmore: rgr that 15:43:33 well I got them working on aarch64 15:43:40 ppc needs a patch to lorax 15:43:47 I've sent a pull request upstream for that 15:44:02 but over all they're mostly working there as well 15:44:30 I'm just cleaning them all up today and getting them to a point they can run from a cron job 15:44:37 should have that crossed off today 15:44:45 okay 15:44:58 there was a complaint that aarch64 sent out broken dep emails 15:45:01 at the moment they're just a Everything and Server compose 15:45:13 dgilmore: already replied to that email, it was a bug in my script 15:45:53 cool. 15:46:13 cool 15:46:14 once I have the above bits cleaned up I'll be added extra bits like qemu and docker images 15:46:18 its all on the mirrors also 15:46:27 will have to tweak mirrormanager 15:46:30 and hacking in stuff like arm images 15:46:42 dgilmore: cool, the secondary mirror sync was on my todo list 15:46:44 it requires going in and manually fixing up urls to the base 15:47:17 pbrobinson: http://dl.fedoraproject.org/pub/fedora-secondary/development/24/ 15:47:45 dgilmore: I think I have a means of moving s390 over to the process just for an Everything repo compose, I'll be looking at that later in the week 15:47:50 pbrobinson: what was the issue with lorax on ppc? 15:47:57 dgilmore: hang on... 15:47:58 pbrobinson: okay 15:48:06 can we not go in and fix the db in mm for a bit? 15:48:08 dgilmore: it wanted docker on ppc64 which we don't currently have 15:48:15 so that mm folks can see how it's broken so we can actually fix it? 15:48:24 nirik: was not going to look at it until later 15:48:28 dgilmore: it'll be the same issue for s390, so I fixed that at the same time 15:48:40 nirik: I used the web interface for primary 15:48:42 sure, but I'd like to make sure we have a chance to record how it's broken at least for them... 15:48:57 yes, but thats not a real fix. ;) it should auto detect it right... we need to make it so 15:48:59 pbrobinson: lorax wants docker? that seems wrong 15:49:24 nirik: it just does not update the pointer to the new location 15:49:24 dgilmore: don't disagree, see the latest, or one of the latest changelog 15:49:40 nirik: https://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=aarch64 15:49:48 dgilmore: as in it pulls in docker as part of building sutff 15:50:06 dgilmore: not as the lorax rpm actually depends on it 15:50:07 nirik: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-24&arch=aarch64 is correct 15:50:07 right, will ask mm folks to look. 15:50:51 dgilmore: rawhide looks a bit messed up too on the primary mirror http://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/ 15:51:29 pbrobinson: how? 15:51:48 dgilmore: it has Everything, Server plus all the old arch directories 15:52:02 pbrobinson: s390 and ppc have not moved yet afaik 15:52:06 you said ppc failed 15:52:16 so I expect that to be the case until they move 15:52:27 aarch64 is gone 15:52:36 and it is the only one under Server and Everything 15:52:47 dgilmore: ah, OK, I didn't realise it would deal with that, I thought it was one or the other 15:53:01 it just gets what is on the arches 15:53:10 it does not know anything about the change 15:53:19 and for the most part does not need to 15:53:32 dgilmore: and ppc has a Everything directory there already, just not Server 15:53:44 dgilmore: so it should just be s390 15:54:16 pbrobinson: probably landed after the last sync 15:54:26 and will get fixed next time round 15:54:30 dgilmore: that landed Friday night 15:54:39 dgilmore: actually before aarch64 ;-) 15:55:12 pbrobinson: perhaps rsync to the hub is broken 15:55:37 dgilmore: possibly, lets sort it OOB and move on 15:56:17 I have nothing really else for secondary, basically we're almost ready for alpha, finally! 15:56:37 rsync: failed to connect to ppc.koji.fedoraproject.org (10.5.124.182): No route to host (113) 15:56:40 rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9] 15:56:43 Command '['rsync', '-avhHp', '--exclude=.snapshot', '--exclude=archive', '--exclude=SRPMS', '--exclude=source', '--exclude=arm', '--exclude=armhfp', '--exclude=aarch64', '--exclude=s390', '--exclude=s390x', '--exclude=repodata', 'rsync://ppc.koji.fedoraproject.org/fedora-ppc', '/srv/pub/fedora-secondary/']' returned non-zero exit status 10 15:56:48 rsync: failed to connect to ppc.koji.fedoraproject.org (10.5.124.182): No route to host (113) 15:56:51 rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9] 15:56:54 Command '['rsync', '-avhHp', '--exclude=.snapshot', '--exclude=archive', '--exclude=SRPMS', '--exclude=source', '--exclude=arm', '--exclude=armhfp', '--exclude=aarch64', '--exclude=s390', '--exclude=s390x', '--delete-after', 'rsync://ppc.koji.fedoraproject.org/fedora-ppc', '/srv/pub/fedora-secondary/']' returned non-zero exit status 10 15:56:59 it is broken 15:57:02 pbrobinson: okay cool 15:57:47 I need to sit down and write up a script to do TC's and RC's 15:58:06 I will do a better job of accounting for secondary arches with it 15:59:35 dgilmore: I think in most cases it should be OK, I think for f24 we're going to need to run on a branch anyway 16:00:01 I was also wondering how we're planning on doing bleed repo with pungi 16:00:17 I was thinking maybe a locked down tag like f24-bleed or similar 16:00:47 pbrobinson: tags 16:00:57 probably f24-compose 16:01:09 and we will do TC and RC composes against it 16:01:22 they will have to have inheritance on 16:01:39 which may make things tricky if packages get pulled in from f23 16:03:53 pbrobinson: anything you want to cover as part of the different arches? 16:04:02 or just skip that and move on to open floor? 16:04:23 dgilmore: don't think so 16:04:31 #topic open floor 16:04:38 I have one quick thing 16:04:59 there has been a raft of people doing silly things with packages causing nvr's to go backwards 16:05:12 only one of which was an intentional go backwards 16:06:38 yeah... that is silly stuff 16:06:47 dgilmore: it's not unusual it's just that the report is now highlighting them 16:06:52 perhaps we could draft a standard email and mail them about it? 16:07:09 or can pungi stop allowing it? ;) 16:07:10 pbrobinson: sure 16:07:14 dgilmore: I've often seen them and just fixed them because shadow/compare bits for secondary pick them up 16:07:22 but there has to be things that can be done 16:07:30 like a pre fedpkg build test 16:07:52 I have something real quick also 16:07:57 yes, I think a check in fedpkg would be the best spot to handle that 16:08:04 I's say fedpkg is a good place to catch this... easy NVR comparison 16:08:21 it means the packager can fix it before it lands anywhere 16:08:57 Package: eclipse-launchbar-1.0.1-1.gitedd5f69.fc25 16:08:57 Old package: eclipse-launchbar-1.0.2-0.1.git93cdb07.fc25 16:08:57 Summary: Eclipse Launchbar plug-in 16:08:57 RPMs: eclipse-launchbar 16:08:57 Size: 181382 bytes 16:08:59 Size change: -57708 bytes 16:09:02 Changelog: * Thu Mar 10 2016 Mat Booth - 1:1.0.1-1.gitedd5f69 - Take a post-release snapshot of 1.0.1 due to API breakage in newer versions 16:09:10 this one they went backwards and did not add an epoch 16:09:17 fun 16:09:32 dgilmore: It should have an epoch 16:09:54 http://pkgs.fedoraproject.org/cgit/rpms/eclipse-launchbar.git/tree/eclipse-launchbar.spec 16:10:10 there is a handy compare_tags_by_evr() routine in the rpmUtils python... 16:10:45 err... compareEVR() 16:11:01 mbooth: so it does. must be a bug in the report tool 16:12:28 might not actually take epoch into account 16:13:08 likely 16:13:15 just filed https://pagure.io/compose-utils/issue/4 16:14:13 one other thing I wanted to mention is that pungi is now running its test suite whenever a pull request comes in 16:14:30 we also run the full test suite when doing builds 16:14:50 while there is not full coverage, its getting better all the time 16:14:54 nice! 16:15:05 which gives us more confidence of changes coming in 16:15:29 is there a test case/scenario that does an actual compose on a small set of packages to prove that it works end to end? 16:15:35 I think we finally have everything we need for Alpha 16:15:44 maxamillion: there is 16:15:54 dgilmore: rocking 16:16:18 maxamillion: I just enabled that running in the rpm builds last week 16:16:27 because it started working 16:16:37 +1 16:16:46 all the tests run in Fedora's Jenkins 16:17:14 lsedlar is looking at getting fedpkg in there 16:17:20 rpkg already is setup 16:17:25 but not tied into pagure 16:18:23 I would like to get tests for other things we depend on running also 16:18:56 one other piece of info from me 16:19:30 I have one quick one when ever you're done 16:19:36 last week we had to coordinate changes to productmd, pungi, and pdc to support a request from QA 16:20:19 which reminded me, we probably need to document the tooling and things we use along with the ways they are tied together 16:20:31 thats it, maxamillion you're up 16:20:52 just a quick note: we're trying to diagnose a pycurl issue that is causing the koji-containerbuild plugin to fail in stage koji, so stage may or may not be in various states of functional for today (and maybe tomorrow) during the debug efforts .... apologies in advance 16:21:21 if this is problematic with something that others are doing, please let me know 16:21:26 maxamillion: kinda what it is for since we do not have a dev koji 16:21:27 good for me 16:21:38 dgilmore: +1 16:21:56 I did ask for a dev koji, but I doubt it will get funded 16:22:07 rgr 16:22:54 anyone have anything else? 16:24:12 not from me 16:24:35 no I 16:24:38 not I* 16:24:40 bleh, I can't type 16:25:10 #endmeeting