17:01:25 #startmeeting RELENG (2018-01-11) 17:01:25 Meeting started Thu Jan 11 17:01:25 2018 UTC. The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:25 The meeting name has been set to 'releng_(2018-01-11)' 17:01:25 #meetingname releng 17:01:25 The meeting name has been set to 'releng' 17:01:25 #chair dgilmore nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin 17:01:25 Current chairs: Kellin dgilmore masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 17:01:25 #topic init process 17:01:55 morning 17:02:13 nirik: morning, how goes? 17:02:30 not too bad. nice rainy day 17:02:49 .hello2 17:02:50 dustymabe: dustymabe 'Dusty Mabe' 17:03:14 * mboddu prefers snow to rain :) 17:03:48 hi 17:05:34 mboddu: snow is eeeeeeevil 17:05:37 since dustymabe blessed us with his presence :P, lets start with rpm-ostree issue 17:06:00 #topic #7201 Initial discussion for rpm-ostree jigdo 17:06:02 ahh. is there one? 17:06:07 ahh indeed 17:06:08 #link https://pagure.io/releng/issue/7201 17:06:35 walters: are you around? 17:06:45 dustymabe: ^ any idea about this ticket? 17:07:01 mboddu: i think this ticket is mostly for awareness and invited collaboration 17:07:28 the goal is mainly to deliver ostree content via traditional rpm payloads rather than having a separate ostree repo. 17:07:43 it's still heavy in the design phase and there are parts of it I like and parts of it I don't like 17:08:05 so I have to ask - where is jigdo even used? 17:08:12 I haven't seen it around in a decade or more 17:08:27 we're planning to try to get together with some people at devconf and go over some more of the details and invite collaboration on design 17:08:33 Kellin: it's not actually jigdo. It's just the "idea" 17:08:41 we used to ship jigdo files... they broke and no one noticed for a year or so. ;) 17:08:44 We're adopting the idea of Jigdo, hence the terminology. Though to be clear, much of the design and all of the implementation is fundamentally different, so we'll generally say "rpm-ostree jigdo". 17:08:51 (quote from the rpm-ostree issue) 17:09:01 yeah, just the ideas... 17:09:51 dustymabe: Okay, thanks for the info, so you will have a definitive design after DevConf? 17:10:00 so - instead of downloading files from an ostree remote over https it will grab the rpms from a yum repo and reconstruct the ostree locally 17:10:36 mboddu: we'll have a better idea of what it looks like 17:10:46 dustymabe: so, I do have some things I'd be worried about, but I can explain that somewhere else 17:11:00 puiterwijk: indeed. i have concerns as well 17:11:05 dustymabe: Okay 17:11:16 For example: this means we need to maintain every single RPM that has ever went into an ostree commit or people won't be able to re-assemble it. And in the same repo 17:11:19 that's why having discussions soon are important and why raising awareness (like with this ticket) are important 17:11:30 * nirik nods. +1 17:11:45 Agreed on discussions, yeah 17:11:57 puiterwijk: indeed - that problem is one that concerns me 17:12:02 i'm keeping an open mind right now though 17:12:06 we'll see where we land 17:12:17 dustymabe: yeah, that's going to make mirroring harder, not easier I'm afraid :(. But yeah, let's see. 17:12:56 next ticket :) ? 17:13:11 dustymabe: Yes, adding the info to this topic 17:13:44 #info rpm-ostree jigdo is still under discussion phase and we will have a better idea of how it looks after DevConf 17:14:25 #topic #7174 Proposal: Give Bodhi a REST API for mashing 17:14:31 #Link https://pagure.io/releng/issue/7174 17:15:28 puiterwijk, bowlofeggs : anything you want to add here, just a quick update or something 17:15:45 mboddu: I personally see it as an headsup. 17:16:09 But Randy opened the ticket, maybe has other thoughts 17:16:33 IIRC, Randy wants to discuss something about it, hence he asked me to add the "meeting" tag 17:16:58 "I filed this ticket so we could discuss it during one of your weekly meetings, if you like.". That sounds like a "headsup but if you want to discuss, we can" 17:17:45 puiterwijk: Okay, thanks, so just wanted to know - how is the work coming along? 17:18:10 mboddu: It's being picked back up now that Randy's back, but likely won't resume full speed until after devconf 17:18:23 puiterwijk: Okay, thanks for the update 17:19:12 #info Bodhi REST API is under work in progress. 17:19:31 yeah it was mostly just a heads up from me 17:19:44 the masher is about to get a lot nicer :) 17:19:47 bowlofeggs++ 17:19:50 and we should stop calling it masher 17:19:53 It's going to be really nice 17:19:54 it's already a lot nicer 17:19:58 i'm trying to say "compose" now 17:20:07 i just can't get my brain to keep doing it :) 17:20:13 bowlofeggs: rename it 'mashah'? 17:20:18 hahah good idea 17:20:19 bowlofeggs: "masher nicer" - I like it :D 17:21:09 Next topic 17:21:21 #topic #7147 automatically put the latest composed Modular Fedora containers into the Fedora candidate registery 17:21:29 #link https://pagure.io/releng/issue/7147 17:21:41 puiterwijk, dustymabe : ^ more container stuff ;) 17:22:01 there is no software at all to automate that 17:22:19 So that'd need to be written, probably using loopabull 17:22:31 puiterwijk: Yes, same thoughts here 17:22:49 mboddu: I think you and I should go through and finish up that deliverable list taiga card 17:23:04 mboddu: and get that along with other delivery problems all queued up, documented, and on the larger roadmap 17:23:36 Kellin: Okay 17:24:11 puiterwijk: So, atm I guess we should put this work on hold and get back to it when we have enough resources? 17:24:45 sure 17:24:58 mboddu: https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/801 17:25:23 mboddu: may not be related because it's not 'per release', but it is 'post release' maintenance yeah? 17:25:37 #info We dont have anything to automate it right now, we will get back to it when we have enough resources 17:26:26 Kellin: I didnt get it 17:27:44 Kellin: We can discuss about it after this meeting since its not related 17:27:48 next topic 17:27:54 #topic #7227 [RFE] Add new repositories for modular[-updates[-testing]] 17:28:03 #link https://pagure.io/releng/issue/7227 17:28:39 So, now we have an idea here, but I just want to what needs to be done here 17:29:00 Just creating the tags and the respective repos? 17:29:16 And update the bodhi to use those tags? 17:33:41 well, it needs pungi work first no? 17:34:07 or perhaps just config 17:34:36 nirik: configs- sure, not sure if it requires any update to pungi itself 17:36:15 puiterwijk: ^ is my assumption right here? 17:36:36 mboddu: no, it does need pungi devel work 17:36:40 That's still in progress 17:37:48 puiterwijk: So, only bodhi devel work and creating tags and repos, thats it right? 17:37:54 mboddu: no. 17:38:06 This needs actual pungi development work since we can't generate the repos they want yet 17:38:17 So right now, the best we can do is empty repos 17:38:30 Okay 17:38:55 * mboddu read "need" as "not" 17:39:24 puiterwijk: Okay, thanks for the info 17:39:41 #info Pungi devel work is in progress right now for this change 17:41:08 Next topic 17:43:01 #topic Alternative Architectures updates 17:43:09 sharkcz: any updates? 17:46:14 * mboddu assumes everything is great in alternate world 17:46:16 moving on 17:46:21 #topic Open Floor 17:46:29 Anybody has anything to share? 17:46:42 puiterwijk: You wanna update on FLIBS automation? 17:47:04 give an update on* 17:47:41 The scripts work now 17:47:58 short and sweet, huh? 17:48:20 #info FLIBS automation is working now, thanks to puiterwijk 17:49:05 Anybody has anything else to share? 17:50:36 Okay, I guess thats it 17:50:41 Thanks everyone for joining 17:50:44 #endmeeting