17:02:11 #startmeeting RELENG (2018-10-18) 17:02:11 Meeting started Thu Oct 18 17:02:11 2018 UTC. 17:02:11 This meeting is logged and archived in a public location. 17:02:11 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:11 The meeting name has been set to 'releng_(2018-10-18)' 17:02:12 #meetingname releng 17:02:12 The meeting name has been set to 'releng' 17:02:12 #chair nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin dustymabe 17:02:12 Current chairs: Kellin dustymabe masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 17:02:12 #topic init process 17:05:03 morning 17:06:09 nirik: How goes? 17:06:29 living the life. :) 17:07:00 nirik: I dont have anything in particular, but I have a question regarding https://pagure.io/releng/issue/7877 17:07:32 That particular requestor doesn't have any packages that he is maintaining https://src.fedoraproject.org/user/avigne 17:07:39 are they a packager? 17:07:40 But he is a part of packager group 17:07:56 * mboddu wondering how that happened 17:08:04 I sponsored him. 17:08:13 ah, ok... they could be added then... although if they are in contact with main maintainer they could add them ? 17:08:22 He has made his SCM request and I thought it was processed. 17:09:25 I guess not; I'll have to see why. 17:09:40 tibbs: Ahhh okay, well, that answers the question, it was a bit scary when I noticed it 17:10:42 There's always a lag between the sponsoring and the package import, so it doesn't always mean that something hs gone wrong. 17:13:07 tibbs: Sure, but this is first I have seen something like this. Anyway, thanks for the info :) 17:13:31 Ah, it's still pending for some reason. I'll process it when I get back to my office. 17:14:21 nirik: Also, I have something else to talk about - https://pagure.io/pungi-fedora/pull-request/665 17:14:23 tibbs: Thanks 17:15:39 nirik: Well, is there any reason why we should avoid it, rather than silverblue/atomic workstation should only be generated from a workstation tree? 17:17:46 well, I think I commented there... we can do it, but if we do, we should do it asap so we can figure out if it breaks anything in nightly composes 17:20:15 nirik: Okay, I wanted to know if there are any historic reasons for this, thanks 17:20:23 I will merge it now and will back out if needed 17:20:50 Well, those are the two things I have in mind 17:21:10 nirik: Anything you want to add or any updates? 17:21:29 not off hand... trying to do some installs and also the go/no-go meeting 17:22:50 nirik: Hehe, same here, for some reason netinstall is very slow (well the office network) 17:23:29 I will cut this meeting short then 17:26:02 Okay, thanks for joining everyone 17:26:37 I am not sure if short meetings are a good thing or a bad thing, oh well... 17:26:41 #endmeeting