15:03:38 <mboddu> #startmeeting RELENG (2020-04-07)
15:03:38 <zodbot> Meeting started Tue Apr  7 15:03:38 2020 UTC.
15:03:38 <zodbot> This meeting is logged and archived in a public location.
15:03:38 <zodbot> The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:03:38 <zodbot> The meeting name has been set to 'releng_(2020-04-07)'
15:03:39 <mboddu> #meetingname releng
15:03:39 <zodbot> The meeting name has been set to 'releng'
15:03:39 <mboddu> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:03:39 <mboddu> #topic init process
15:03:39 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:04:34 <nirik> morning
15:04:51 <mboddu> Morning nirik and thanks for reminding, I wasn't paying attention to time
15:05:04 <nirik> easy to do.
15:05:08 <nirik> or not do
15:05:11 <nirik> or something
15:05:34 <mboddu> Haha :)
15:05:39 <mboddu> Okay, lets get started
15:05:58 <mboddu> #topic #9384 releng check for: Removal of the glibc-headers package
15:06:04 <mboddu> #link https://pagure.io/releng/issue/9384
15:06:22 <nirik> I think this will hopefully work fine.
15:06:30 <nirik> nothing we need do that I can think of
15:06:55 <mboddu> I had a question about it which I wanted to ask you, but I couldn't remember, bahh.... :(
15:09:05 <nirik> happens to me all the time. :)
15:10:16 <mboddu> nirik: "We cannot remove the glibc-headers.i686 package from the build because the i686 buildroot needs it. The current solution is to provide a glibc-headers-x86.noarch package on i686 and x86_64. Since it is a noarch package, the existing compose tool is no longer a problem."
15:10:23 <mboddu> ^ from the change request
15:10:32 <mboddu> I am not sure I was able to follow it
15:10:35 <nirik> yeah
15:10:59 <nirik> so right now we have glibc-headers as a archfull subpackage... ie, it has a version on all arches.
15:11:28 <nirik> we can't just nuke the i686 one completely, because on i686 installs (which we don't support, but in theory could exist) it needs it.
15:11:47 <mboddu> Does that mean they are combing glibc-headers.x86_64 and glibc-headers.i686 into glibc-headers-x86.noarch?
15:11:51 <nirik> but if we change that to a noarch subpackage, we can only include it on x86_64 and i686
15:11:56 <nirik> yeah.
15:12:16 <mboddu> Oh okay, that made sense now
15:12:36 <mboddu> Well, I will update the ticket and there is no work needed from releng
15:12:38 <mboddu> Thanks nirik
15:13:05 <nirik> yeah, unless we missed something that should work
15:13:11 <nirik> and be easier than messing with pungi
15:15:27 <mboddu> Agreed
15:15:48 <mboddu> #info No releng work is need on this change
15:15:58 <mboddu> #topic #9359 F33 system wide change: Introduce module Obsoletes and EOL
15:16:04 <mboddu> #link https://pagure.io/releng/issue/9359
15:16:27 <mboddu> "have a central place for managing the new modulemd documents" not sure how they will look like
15:16:37 <mboddu> So, I suggested modules/ namespace in dist-git
15:16:56 <mboddu> We also have fedora-module-defaults repo, but thats not something we should use for this
15:17:31 <nirik> ok. I think there's still discussion on the devel list on this one too
15:18:50 <mboddu> Yes
15:18:58 <mboddu> Not very positive about the change
15:19:05 <nirik> I haven't followed it much
15:19:34 <nirik> do chime in on it if you have thoughts. ;)
15:20:23 <mboddu> Yeah, I need to look into it throughly (since its modularity, its not always as I think it is)
15:21:37 * nirik nods
15:22:12 <mboddu> #topic #9240 Update published Fedora 31 cloud images
15:22:19 <mboddu> #link https://pagure.io/releng/issue/9240
15:24:16 <nirik> no idea here, but it seems like a great thing to do.
15:25:11 <mboddu> Yeah, no idea for me as well
15:25:27 * mboddu looks for Dusty
15:25:28 <nirik> this is something we can do in freeze? perhaps we should schedule a time next week and see if we can get it done? not sure what dusty's schedule is like...
15:26:59 <mboddu> Hey dustymabe
15:27:29 <dustymabe> \o
15:27:32 <mboddu> dustymabe: We are talking about https://pagure.io/releng/issue/9240
15:28:09 <dustymabe> mboddu: cool
15:28:19 <mboddu> nirik suggested to schedule a time next week during freeze to work on this
15:28:53 <mboddu> dustymabe: How hard is it? How much time does it require and are you free next week?
15:29:19 <dustymabe> I think basically what we need is something very similar to what we had for Atomic Host
15:29:35 <dustymabe> i.e. something like pushtwoweekatomic.py
15:30:11 <dustymabe> and the website code updated to source information from fedmsgs or something
15:30:40 <dustymabe> automated tests would be nice, but not strictly required if we have some volunteers that would be willing to run some things
15:30:53 <nirik> I wish we could do something to make the newest fedora cloud image on aws appear better, but thats likely beyond the scope here. ;(
15:31:14 <dustymabe> the thing is I can't drive this whole effort - i just don't have the cycles to do much more than help
15:31:31 <dustymabe> if it makes anyone feel any better we've started holding cloud WG meetings again every two weeks
15:31:34 <mboddu> dustymabe: Sure, we can understand
15:32:03 <mboddu> dustymabe: Awesome, can you help us run the manual process once and we can take of the automation process?
15:32:10 <dustymabe> so it would be nice to collect interested people/parties and invite them to come to the WG meetings
15:32:29 <dustymabe> mboddu: yeah let's schedule some time next week to talk about it
15:32:30 <mboddu> Ack
15:32:35 <nirik> perhaps we could split it out into several parts...
15:32:44 <mboddu> dustymabe: Awesome
15:32:44 <dustymabe> actually we could use the cloud WG meeting time
15:32:48 <nirik> for different people to work on (if we have different people willing)
15:33:07 <mboddu> nirik: How do you wanna split them?
15:33:27 <dustymabe> https://apps.fedoraproject.org/calendar/cloud/2020/4/14/
15:33:36 <nirik> well, someone writes the playbook/py script, someone updates websites code, some testing?
15:33:37 <dustymabe> there is the cloud meeting schedule for next week
15:34:11 <mboddu> My plan is, look at the publishing part, ^^ playbook/py script part and updating websites part for now
15:34:32 <mboddu> And let the Cloud WG do manual testing until we figure out automated testing
15:35:02 <nirik> well, openqa is actually testing them I think.
15:35:16 <dustymabe> regarding manual testing.. we can reduce release cadence until we automated
15:35:16 <mboddu> I am only expecting to learn how its manually published to write playbook/py script later and what pieces are updated on websites side
15:35:28 <dustymabe> i.e. once very two months would still be better than what we have
15:35:33 <mboddu> dustymabe: Sure
15:35:53 <dustymabe> we would have 0, 2, 4, 6 (next fedora release), 8, 10, etc
15:35:59 <mboddu> .time
15:36:00 <zodbot> mboddu: 03:35 PM, April 07, 2020
15:36:27 <mboddu> Oh that is great, the cloud wg meeting is clashing with this meeting :(
15:36:40 <dustymabe> :) - assuming it's weekly, yes
15:37:03 <mboddu> Well, not entirely, we can meet in the second half of the cloud meeting
15:37:04 <dustymabe> we could look at moving it
15:37:37 <nirik> or we could combine. ;)
15:37:37 <mboddu> Lets leave it for now
15:38:54 <mboddu> well, I am not sure about that
15:39:29 <mboddu> Anyway, thanks dustymabe, I will schedule a meeting for the second half of the Cloud wg meeting to go over this
15:39:51 <dustymabe> +1
15:40:11 <dustymabe> if you've got some downtime this week - there is the ostree import and prune stuff we need to finish off :)
15:40:17 <mboddu> #info We will go over it next week Tue at 16:00 UTC
15:40:21 <dustymabe> would love to run the first prune this weekend if we could
15:41:06 <nirik> downtime? whats that?
15:41:30 <dustymabe> :) - a mythical notion
15:41:33 <nirik> dustymabe: I might be able to work on it tomorrow afternoon? are you free then?
15:42:21 * mboddu can join
15:45:10 <dustymabe> let me check
15:45:23 <dustymabe> i should be after 1:30 eastern
15:45:25 <dustymabe> so yes
15:45:33 <dustymabe> can you pop something on my calendar ?
15:46:57 <nirik> I could do 2:30 to 3:30 or after 4
15:47:17 <nirik> (If I have converted timezones right)
15:47:21 <dustymabe> It's possible I'll have a meeting pop up on my calendar for 5 eastern, but it should be short
15:47:56 <dustymabe> so 2:30 to 3 pacific should work
15:48:03 <dustymabe> i'll have to leave after 3 pacific
15:48:04 <nirik> lets try that... mboddu ?
15:48:31 <mboddu> That should work for me
15:48:58 <nirik> cool. can someone add it? or I can after a bit
15:49:08 <mboddu> I can send an invite
15:50:07 <mboddu> So, 5:30 to 6:00 Eastern tomorrow
15:50:55 <nirik> no. 2:30 to 3 eastern
15:51:08 <nirik> right after the infra ops standup
15:51:23 <dustymabe> haha, I was referring to 5:30 to 6 eastern
15:51:25 <mboddu> [11:47:56] <dustymabe> so 2:30 to 3 pacific should work ?
15:51:29 <dustymabe> but 2:30 eastern works better
15:51:30 <nirik> I was converting to eastern.
15:51:35 <nirik> but I guess that confused everyone
15:51:47 <mboddu> Okay, 2:30 eastern it is, sorry for the first invite
15:51:48 <dustymabe> because then I can go longer than 3 (so more than 30 minutes)
15:51:53 <dustymabe> +1
15:51:56 <dustymabe> TZ=jarc
15:52:01 <dustymabe> TZ=hard
15:52:28 <nirik> but I have something at 12:30 my time... ie, 3:30 eastern...
15:52:40 <nirik> but we could do an hour then and hopefully get it working
15:52:55 <mboddu> I scheduled it for 1 hour, we will see then
15:53:32 <mboddu> Sorry dustymabe, I asked for 5 min but we got you for almost 30 min
15:53:34 <mboddu> Anyway
15:53:38 <mboddu> #topic Open Floor
15:53:53 <mboddu> #info Fedora 32 Final Freeze moved to Thu, Apr 09th 2020
15:55:19 <mboddu> Anything else to share?
15:55:48 <nirik> not much. I continue to poke at the kojira / newrepo issues...
15:56:51 <mboddu> Let me know if you need any help nirik
15:56:55 <mboddu> Thanks everyone for joining
15:57:04 <mboddu> #endmeeting