16:01:00 #startmeeting RELENG (2019-06-27) 16:01:00 Meeting started Wed Jun 26 16:01:00 2019 UTC. 16:01:00 This meeting is logged and archived in a public location. 16:01:00 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:00 The meeting name has been set to 'releng_(2019-06-27)' 16:01:00 #meetingname releng 16:01:00 The meeting name has been set to 'releng' 16:01:00 #chair nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu dustymabe ksinny jednorozec 16:01:00 Current chairs: dustymabe jednorozec ksinny masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 16:01:13 morning 16:01:28 nirik: Hello, how goes? 16:01:49 mboddu: we should probibly adjust that chair line... I think a lot of those people aren''t around/don't care about releng meetings anymore. ;) 16:01:59 not too bad, how about with you? 16:02:24 nirik: Yes, I will adjust the people and include only that showed up in the last few weeks 16:02:34 nirik: Doing okay 16:03:49 I have to cut this meeting short due to some work 16:04:10 But I was thinking and wanted to talk about few stuff before we end the meeting 16:04:18 #topic EPEL8 16:04:50 * dustymabe waves 16:04:52 #info We are at a position to build the packages in epel8 16:05:06 yay 16:05:18 (in staging) 16:05:31 #undo 16:05:31 Removing item from minutes: INFO by mboddu at 16:04:52 : We are at a position to build the packages in epel8 16:05:38 #info We are at a position to build the packages in epel8 in stg koji 16:05:54 #info mboddu is testing stg bodhi, but the composes seems to get stuck in 'Requested' state, cverna is looking into it 16:06:08 I couldn't figure it out as there wasn't any processes running on the box 16:06:25 I tried resuming, kill it and push again, but nothing helped 16:06:35 mboddu: if we are going to do a beta period with rawhidelike composes, we also will need a pungi config for it... 16:06:44 odd. ;( 16:06:58 FWIW, it worked in my previous tests (which failed due to other reasons), but now they seems stuck 16:07:46 nirik: I thought about rawhide like composes, but then while its being tested, we could try to fix bodhi and if it works we will just keep using it for epel8 ga 16:08:32 nirik: On that note, does epel8 ga will overwrite epel8 beta content? Or it will synced to a new location and changing the repo location? 16:08:59 we could do either... 16:09:39 I prefer the first one if its not going to break anything and people can just start getting ga content if they were on beta 16:09:45 the reason for wanting a rawhide like beta (nightly compose, all builds just go in) is to get the repo populated... if everything has to spend 2 weeks it will be hard to get things done 16:09:49 Rather than asking them to change again 16:10:23 and it would cause a ton of overrides (basically everything) 16:10:28 nirik: Ahhh, okay, got it, then we could use that and for ga we will enable bodhi 16:10:31 sure, we could do it that way, thats fine. 16:10:39 yeah, that was my thought. 16:11:11 #info mboddu will work on pungi config for epel8 beta and will create the nightly compose scripts for testing 16:11:28 While testing, they wont be synced to mirrors until beta goes live 16:12:26 Anything else before I jump to next topic which is related to epel8 16:12:32 ? 16:15:12 * nirik is fine moving on 16:15:19 Okay, next thing I need to talk about epel8 is branching 16:15:44 Currently I am doing it which can be scripted easily, provided there is a list of packages 16:16:01 well, one thing that someone noted this last week... 16:16:03 Its kinda scripted, but not great 16:16:27 our usual process for branches/etc... already deals with pretty vast numbers of things... 16:16:44 like there was several hundred go packages the other day 16:17:17 so, perhaps we just tell people to use the normal process? but then they may not have it scripted to request on there end 16:17:58 nirik: Yes, my suggestion is updating 'fedpkg request-branch' and 'fedscm-admin' to handle epel8 branch requests 16:18:25 Then give them a shell script, which will help them to request epel8 branches for all the packages they maintain 16:18:35 the other question is: from what branch does it make the new one from? master? 16:19:10 nirik: Thats what I am thinking, since it might still support epel8 and carry the latest patches that they might require 16:19:23 I will definitely wouldn't suggest epel7 16:19:41 mind pinging me when we get to open floor? 16:20:00 dustymabe: Sure :) 16:20:32 By support I mean, build-able on epel8 16:20:57 * tdawson gives a +1 to branching from master. 16:21:02 well, it's hard to say... but I guess master is the best if we don't give them the choice. 16:21:15 with epel7 we allowed them to choose, but thats a extra pain 16:21:50 nirik: Well, we could give that option but as you said, might be an extra pain 16:22:05 * mboddu will see what he can do 16:24:39 today, I use the F28 repo as my "EPEL 8" until the real thing is available 16:24:42 master is likely fine, they can merge other or do whatever after. 16:26:24 #info We will update fedpkg and fedscm-admin to support requesting epel8 branches 16:27:37 cyberpear: The problem with that, is that most developer "fixes" (things that allow the pacakges to build on RHEL8) were put in F29 and F30. 16:28:10 Up to F28, all the fixes were mostly done by me, and there were plenty that I didn't get to. 16:28:11 * nirik looks at empty coffee cup. 16:28:12 cyberpear: Yeah, I would suggest f29+ 16:28:29 nirik: Few more min and I got to run as well 16:28:33 #topic Open Floor 16:28:38 dustymabe: You are up 16:29:00 nirik: In the mean time quick question, does the infra openshift instance has access to /mnt/koji? 16:29:22 mboddu: it could, I don't think we have anything that has it currently... 16:29:23 mboddu: thanks 16:29:24 Basically thinking of creating a service to run minimal composes 16:29:44 mboddu: odcs won't work? 16:29:49 nirik: +1, then I will work on it after epel8 16:29:59 mboddu: just wanted to draw you and kevin to give expert advice on https://pagure.io/fesco/issue/2152#comment-579046 16:30:02 nirik: It might, now that they support pungi configs 16:30:23 we don't have to discuss it here, but it would be nice to get an answer in the ticket (or tag in other people who would know) 16:31:38 dustymabe: yeah, have been following that, just haven't had time to chime in. Basically I think the process should work fine, and we can always adjust it... 16:32:53 dustymabe: I guess you can be able to specify a commit from which you can submit a build, but I dont think that will solve your issue, right? 16:34:22 mboddu: basically can we push a git commit into a repo (not on a branch) and tag it 16:34:23 * nirik thinks the branches are fine personally. 16:34:24 and 16:34:37 do a fedpkg build from a commit/tag 16:35:09 dustymabe: Where do you push that commit? If not on a branch? 16:35:17 mboddu: directly to the repo 16:35:36 alternatively can we push a tag+commit at the same time 16:36:49 dustymabe: That I am not sure 16:37:03 what good is the tag? just to make it more clear what you are doing? 16:37:34 nirik: correct - people like the idea of using a tag for each backport, rather than a branch 16:38:06 sure, that works too I guess... 16:38:13 just create a branch as called `f30-hotfix` as needed for these items? (then only even merge f30 into this one, never the other way?) 16:38:37 (and once that branch is created, fcos would follow that one instead of f30?) 16:38:55 * nirik had one last item for open floor too if we have time 16:39:36 cyberpear: Thats what the initial request is 16:39:58 it wouldn't follow it forever, these are all short term backports. 16:40:13 dustymabe: I guess a separate dist-git branch should work, but I still dont see any use case where you would two branches to carry two different patches 16:40:15 after a few weeks it would go back to following the fedora branch 16:41:29 dustymabe: But I will take a look at the ticket and will comment on it 16:41:37 nirik: Sure, go ahead 16:42:13 just a quick thing: 16:42:13 sorry nirik mboddu - i got pulled away 16:42:16 reading scrollback 16:42:31 I spent some time yesterday on container/cloud composes. 16:42:47 containers are back to all working except armv7, and pbrobinson is going to look into that. 16:43:05 cloud I think is all back to working 16:43:31 nirik++ 16:44:02 we set armv7 to non blocking on f30, but not f29, so those container runs are failing. 16:44:04 #info Cloud composes are back to working and except for armv7 container composes are also working, pbrobinson is looking into the armv7 issue 16:44:11 the 30 ones are finishing incomplete 16:44:35 nirik: Yeah, aarch64 became blocking for f30 16:44:40 so hopefully builders are back to normal/stable finally after the great python3 upgrade 16:44:59 the aarch64 ones are all finishing fine now. ;) 16:45:06 Yay 16:48:05 * nirik has to get coffee... back in a bit if anyone is still here. 16:48:05 Anything else? 16:48:14 nirik: I guess thats it 16:48:28 Thanks everyone for joining 16:48:34 #endmeeting