14:31:14 #startmeeting RELENG (2017-06-05) 14:31:14 Meeting started Mon Jun 5 14:31:14 2017 UTC. The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:31:14 The meeting name has been set to 'releng_(2017-06-05)' 14:31:14 #meetingname releng 14:31:14 The meeting name has been set to 'releng' 14:31:14 #chair dgilmore nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin 14:31:14 Current chairs: Kellin dgilmore masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 14:31:14 #topic init process 14:31:42 * masta is around 14:31:53 .hello kellin 14:31:54 Kellin: kellin 'None' 14:31:56 .hello psabata 14:31:57 contyk: psabata 'Petr Ĺ abata' 14:32:12 .hello dustymabe 14:32:13 dustymabe: dustymabe 'Dusty Mabe' 14:32:41 FYI, nirik is on PTO this week 14:32:59 hello contyk, nice to see you last week in person. 14:33:22 masta: are you back in states or still in Brno? 14:33:39 back in Dallas, USA 14:33:52 masta: okay 14:33:55 masta: ah, that's you :) 14:34:15 contyk, yes! 14:34:59 lets give couple more min for people to join and then we will start 14:35:14 sharkcz: are you around? 14:35:33 hi all 14:35:36 mboddu: have another meeting running now ... :-( 14:35:38 * mboddu wants to get an update on Alt arch, its been a while since we were busy on other stuff in previous meeting 14:35:52 .hello maxamillion 14:35:53 maxamillion: maxamillion 'Adam Miller' 14:35:55 sharkcz: okay 14:36:00 Lets start 14:36:03 .pushduty 14:36:05 maxamillion: The following people are on push duty: Rob, Fedora Release Engineering 14:36:08 maxamillion: - https://apps.fedoraproject.org/calendar/release-engineering/ 14:36:23 #topic #6822 using include statements in pungi-fedora 14:36:32 #link https://pagure.io/releng/issue/6822 14:36:57 * dustymabe waves 14:37:19 maxamillion, thanks,.... I was worried I was on push duty. the calendar seem to be different in recent months 14:37:41 dustymabe: Do you remember whats lsedlar recommendation on this? If I remember correctly, its not advised but very useful to use, I might be remembering it wrong 14:38:03 mboddu: i think lsedlar's take was "why aren't we doing this already" 14:38:09 masta: :) 14:38:15 dustymabe: \o 14:38:17 there's no reason not to recommend it 14:38:34 lsedlar, dustymabe : okay, thanks 14:38:48 dgilmore, do you know of a reason why we aren't doing this today? 14:39:10 dgilmore: so, can we start using the "include" option for pungi configs? 14:39:15 dustymabe: because we are not 14:39:25 the use of them is not documented 14:39:39 there is no reason why we can't 14:39:42 the include thing is fine 14:39:46 dgilmore: cool - good to know 14:39:47 true, the format generally lacks any documentation 14:39:48 though for some thing it may get tricky 14:40:13 like keeping a historical record that this was the config used for Alpha, BEta, Final etc 14:40:28 but, I say we run the pungi validation script on anything that uses %include 14:40:41 dgilmore: i'm thinking we have a single config for a branch that is like basically a library of configuration 14:40:41 dustymabe: there is no intentional decision either way 14:40:50 dustymabe: huh 14:40:59 and then individual pungi configs will change only what they need to 14:41:11 lsedlar: may I request documentation be made? :) 14:41:19 I do not grok what you just said dustymabe 14:41:50 dgilmore: basically most configuration lives in one file - then individual configs (like atomic nightly cloud nightly, etc, just #include that one) 14:42:02 and change what they need to 14:42:11 maxamillion, yes you can :) 14:42:19 FTW pungi-config-validate 14:42:20 dustymabe: I think you need to use some more words 14:42:25 and be a bit clearer 14:42:53 does anyone else not know what I'm saying? 14:43:25 you want to include config files in other config files 14:43:26 i guess I just need to create an example 14:43:38 contyk: that I get 14:43:46 dustymabe, yes, I've no idea what you say. please express 14:43:54 but what he is proposing as to how he thinks it will work I do not 14:44:11 lsedlar: thanks :) 14:44:12 ok - basically there is a lot of config in fedora.conf 14:44:23 * dgilmore notes that the use fo include is not documented 14:44:32 dgilmore: that might be a problem :) 14:44:36 a lot of stuff at the top that doesn't actually tell pungi to build anything 14:44:54 but is just configuration, like names, etc.. 14:44:58 and for things like alpha and beta and final we likely do not want to use includes so we have a record of exactly what was used 14:45:16 dgilmore: personally, i think that's what git is for 14:45:29 but i don't have a problem with that 14:45:33 dustymabe: that only helps whjen you know the commit used 14:45:38 dustymabe: which we do not know 14:46:04 dgilmore: probably the last commit that edited the file 14:46:05 wasn't there a proposal to build composes in koji? 14:46:16 for exactly this reason? 14:46:29 dustymabe: are you proposing that we have a snipped for each thing and include them all 14:46:32 I don't know any specifics, just heard something like that 14:46:36 so there would be a Atomic host snippet 14:46:39 workstation 14:46:41 Server 14:46:43 Cloud 14:46:51 spinad and labs etc? 14:46:57 dgilmore: no I don't think so 14:47:12 dustymabe: so you need to be explicitly clear 14:47:16 dgilmore: basically what I want is all the config at the top that is common for them all to be in a global config file 14:47:24 because I do not understand what change you are trying to make 14:47:30 other than use includes 14:47:37 I am not sure what you mean by that 14:47:57 dustymabe: only osme of it is common 14:48:00 ok, if you diff the config files in say fedora 25 branch 14:48:10 you'll see mostly common configuration and then you'll see some tweaks 14:48:26 i'm proposing that the common configuration be somewhere in a common config file 14:48:29 that is included 14:48:34 dustymabe, I thinking that right now the atomic kickstart configs need to be separate 14:48:49 mboddu: they are 14:49:05 opps sorry mboddu 14:49:14 masta: the kickstarts are seperate 14:49:19 dgilmore: :) 14:49:22 words seem to be failing us 14:49:45 because I read what masta said as the kickstarts have to be seperate 14:49:53 which they already are 14:50:15 yes 14:50:21 ok from my last set of statements, do you get what I'm saying now? 14:50:46 * masta goes to read the kickstarts for Fedora Atomic 14:50:59 masta: this really has nothing to do with kickstarts 14:51:25 okay, my bad... pls help me understand? 14:51:37 pungi configs are separate from kickstarts 14:51:54 yep 14:51:55 a pungi config might define an image build and specify a kickstart to use 14:53:26 ok - so from my previous set of statements 14:53:37 i would propose that we take what we can from the top of the fedora.conf file 14:53:47 and make it into a common config file for the others to #include 14:54:05 here is an example of the parts of the file I would like to do that with: https://da.gd/FCDg 14:54:14 dustymabe: kinda 14:54:24 dustymabe: I think showing us what you mean might be easier 14:54:49 so basically nothing that actually tells pungi to do an image-build or installer build or any build really 14:55:05 just all the nitty gritty config 14:56:22 dgilmore: see the fpaste for an example 14:56:56 dustymabe: we should discuss it out of the meeting 14:57:07 dgilmore: i tried that on the mailing list 14:57:12 Oh! this is about using %include in pungi, we do that all the time... so long as it validates via pungi-config-validate.. I'm +1 14:57:30 masta: thanks - please add comments to the issue 14:57:41 * masta does 14:57:41 masta: we do not do it at all 14:57:48 masta: in Fedora 14:57:59 anyway lets move on 14:58:05 dgilmore, oh! so I stand corrected. my bad 14:58:05 dgilmore: well that's not true, there is at least one case where we already do 14:58:15 let's talk about Xinclude in variants files ;) 14:58:23 dgilmore: lsedlar said that they are doing it internally 14:58:42 Okay, lets move on 14:58:45 i don't know why we have to move on already - there's no resolution to this? 14:58:58 are we saying "no" are we saying "maybe" 14:59:15 dustymabe: we are not going to dolve it in the meeting and we have other things to discuss 14:59:23 I think we should look at making things better 14:59:32 well i tried to talk about this outside of the meeting 14:59:35 but spending the whole meeting trying to do so is not productive 14:59:55 dustymabe: also, we need the documentation before we make any decision 14:59:58 dustymabe, the it has to validate pungi-config-validate or else nothing, I can say that with truth.. and that is trivial. so lets move on 15:00:32 mboddu: thanks for bringing this up 15:00:36 let's move on 15:00:49 #info masta will update the ticket and lsedlar will try to update the documentation on how to use %include 15:02:15 #topic #6791 Create module-bootstrap-master tag similar to f26-modularity 15:02:23 #link https://pagure.io/releng/issue/6791 15:02:56 this one's been implemented, although the tag name is different than originally requested 15:02:59 that's not a problem 15:03:32 not a problem 15:03:47 contyk: rawhide seemed better to me that master 15:03:48 we've also populated it with some content, with mboddu's help 15:03:50 contyk: okay, I just wanted to know if any more requests will come along on this issue? Like the secure-boot pkgs tagging and any others 15:04:10 mboddu: yes, it might happen, over time 15:04:25 mboddu: but if it has to be done, I'll open a new ticket 15:04:39 as of now there's nothing else to be done 15:04:51 I think this can be closed now 15:04:54 +1 15:05:11 contyk: okay, just wanted to check, thanks 15:05:49 #info Nothing else can be done on this ticket as of now, if anything else pops up modularity-wg will open a new ticket. The ticket can be closed. 15:06:31 #topic #6775 Please Review Arbitrary Branching Change Proposal and Provide Feedback 15:06:38 #link https://pagure.io/releng/issue/6775 15:06:54 dgilmore: would you like to share any updates from FESCo? 15:09:00 * mboddu checks whats the new timeline for this 15:09:08 FESCo acked it 15:09:22 and said that the removal of pkgdb needs to be handled carefully 15:09:35 it has been delayed a couple of weeks 15:10:17 dgilmore: so, is it still removing pkgdb and replacing it with new system, both being done at the same time? 15:11:48 mboddu: "both being done at the same time" ... what is "both" here? 15:12:06 maxamillion: removing pkgdb and implementing new system 15:12:41 maxamillion: last time when we talked about it, I suggested using both like pkgdb for rpms and new system for modules and stuff 15:13:16 mboddu: ohhh ok 15:13:24 mboddu: the claim is that it can not be phased in 15:13:26 maxamillion: my suggestion was to use both of them for sometime and slowly move to new system when we feel like its good enough 15:13:34 I suggested phasing in also 15:13:46 I worry about consistency across systems 15:13:56 lets assume that removing pkgdb will not happen this cycle. hope for best, assume the worst. 15:14:07 I need to follow up to some of the thread on devel@ about the packager group 15:14:32 masta: its scheduled for remoaval in about 4-5 weeks 15:14:54 dgilmore: thats what scares me a lot 15:15:26 mboddu: you and me both 15:15:52 but all we can do is be engaged and make sure its a featureful as possible 15:16:00 and raise concerns over issues we see 15:16:08 dgilmore: sure 15:16:31 then make sure when its done we report issues and brokenees to the people working on it who are on the hook to fix broken things 15:16:56 #info FESCo acked the change and said that the removal of pkgdb needs to be handled carefully 15:16:56 wow 15:17:12 thanks dgilmore 15:17:26 dgilmore, understood. 15:17:40 moving on 15:17:43 #topic #6365 "Broken dependencies" report does not understand rich dependencies 15:17:50 #link https://pagure.io/releng/issue/6365 15:18:27 dgilmore: correct me if I am wrong, I thought we are planning on supporting dnf for f27 but not rich dependencies, am I right? 15:19:04 dgilmore: or are we going to support both? 15:21:14 uh... 15:21:39 so creterepo_s in mash, or koji dist-repos? 15:21:53 err... createrepo_c, even 15:22:12 masta: the plan was to port mash since koji dist-repos has some issues 15:22:37 masta: I was going to ask what createrepo_s was, but was trying to google around first :) 15:22:54 masta: I switched back to irc and noticed it was a fools errand 15:22:57 S is for speed 15:23:04 it's a trivial fix, and I've had a patch in paguer for ages... 15:23:18 masta: oh? is there a PR? 15:23:28 yes 15:23:39 masta: correct 15:24:25 masta: using the API is prefered 15:24:31 i'm guessing the issues with dist-repos are not easily overcome 15:24:50 dustymabe: dist-repos as is, is not functional 15:25:14 main issue is that the debuginfo rpms are mixed in with the regular rpms 15:26:24 k 15:27:02 Okay, lets move on 15:27:15 #topic Open Floor 15:27:58 #info Fedora 26 Beta got delayed by a week, current proposed release date is June 13 2017 15:28:13 maxamillion, https://pagure.io/mash/pull-request/1 15:28:14 Anybody got anything else? 15:28:16 masta: +1 15:28:25 no I 15:28:47 * mboddu got another meeting in 2 min 15:29:18 Okay, lets end the meeting 15:29:20 mboddu: 15:29:31 mboddu: ooops 15:29:32 already? :( 15:29:32 dustymabe: you got anything? 15:29:33 sorry 15:29:35 nope 15:29:38 dustymabe: okay 15:29:45 could I get one more topic in? 15:30:04 https://pagure.io/releng/issue/6815 15:30:32 the only releng task associated with this change has been implemented 15:30:45 I was wondering if I could get a releng ack on the change so I can push it forward 15:30:49 contyk: we are over our time and I got another meeting now, can we take this to the #fedora-releng channel 15:31:04 contyk: sorry about it 15:31:26 contyk: been meaning to do that, I need to coordinate with katec to make sure we get any work needed in our backlog 15:31:44 dgilmore: thanks 15:31:55 so, we got everything 15:32:01 Thanks everyone for joining 15:32:05 #endmeeting