15:05:46 <jednorozec> #startmeeting RELENG (2022-03-15)
15:05:46 <zodbot> Meeting started Tue Mar 15 15:05:46 2022 UTC.
15:05:46 <zodbot> This meeting is logged and archived in a public location.
15:05:46 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:05:46 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:05:46 <zodbot> The meeting name has been set to 'releng_(2022-03-15)'
15:05:46 <jednorozec> #meetingname releng
15:05:46 <zodbot> The meeting name has been set to 'releng'
15:05:46 <jednorozec> #chair nirik sharkcz pbrobinson pingou phsmoura mboddu dustymabe ksinny jednorozec
15:05:46 <jednorozec> #topic init process
15:05:46 <jednorozec> #topic #NNNN TICKET TITLE
15:05:46 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson phsmoura pingou sharkcz
15:06:10 <jednorozec> sorry for the late start forget about the day light savings
15:06:24 <nirik> we all wish we could. ;)
15:06:31 <mboddu> I hope I got the timing right
15:06:39 * mboddu totally trusting google calendar
15:06:47 <jednorozec> well it will get here in a week or so
15:06:55 <mboddu> Also, I am in another meeting, so I will be a bit late in replys
15:07:51 <jednorozec> yeah it is in my calendar as well. I just ignored the notification
15:08:54 <jednorozec> so
15:09:10 <jednorozec> there is one ticket that landed today and I am not sure what to do.
15:09:15 <jednorozec> .releng 10696
15:09:16 <zodbot> jednorozec: Issue #10696: F36 buildroot broken on armv7hl - releng - Pagure.io - https://pagure.io/releng/issue/10696
15:09:39 <jednorozec> so it seems there is already a new build that fixes this issue. But it is in testing
15:09:58 <jednorozec> should I tag it into f36 or just wait until it get there?
15:10:04 <nirik> might be an override causing the problem?
15:10:16 <jednorozec> since it is blocking builds, but only on one arch
15:10:52 <jednorozec> the new build is ~ 1day old
15:10:53 <nirik> well, normally when this happens we untag the offending package(s)
15:12:16 <nirik> which build?
15:12:19 <mboddu> jednorozec: Yeah, either untag the old bad build or if a new build fixes it then create an override in bodhi
15:14:04 <jednorozec> Ack. thanks
15:15:35 <nirik> I'm not sure what package is causing it...
15:17:29 <mboddu> This is odd `nothing provides /bin/sh needed by dnf-4.10.0-2.fc36.noarch`, bash should be there
15:17:31 * mboddu checks
15:17:58 <jednorozec> yeah
15:18:02 <jednorozec> this is weird
15:20:43 <nirik> ah...
15:20:47 <nirik> I think this is my bad.
15:22:01 <nirik> note the host. ;( I added buildhw-a64-06.iad2.fedoraproject.org into the image channel to have another armhfp image builder... but those cannot do normal build tasks... but it's still in the default channel.
15:22:25 <nirik> koji remove-host-from-channel buildhw-a64-06.iad2.fedoraproject.org default
15:22:39 <nirik> that should fix it I think
15:23:16 <mboddu> Ahhh, okay
15:23:21 <mboddu> Good catch nirik
15:25:45 <jednorozec> ok
15:27:23 <nirik> updated it and closed it.
15:28:10 <jednorozec> thanks
15:28:45 <jednorozec> so
15:28:47 <jednorozec> moving on
15:28:50 <jednorozec> .releng 10679
15:28:51 <zodbot> jednorozec: Issue #10679: Cannot install python38-pytest into EPEL8 buildroot - releng - Pagure.io - https://pagure.io/releng/issue/10679
15:29:24 <jednorozec> so they want python38
15:29:34 <jednorozec> but rhel8 is python36 i think
15:29:48 <nirik> it's a modular one...
15:30:01 <nirik> it should be there, but isn't... and I am not sure why. :(
15:30:14 <jednorozec> I missed the modular in the ticket
15:30:58 <nirik> if you do:
15:31:01 <nirik> sudo dnf repoquery 'python38-pytest' --disablerepo=\* --repofrompath=c8s,https://infrastructure.fedoraproject.org/repo/centos/stream8-kojitarget/latest/x86_64/CS-8-001/ --enablerepo=c8s
15:31:05 <nirik> you can see it's there.
15:31:17 <nirik> well, we flattten out all the rhel8 modules for the epel8 buildroot.
15:32:45 <nirik> has to be something with rhel8 dnf somehow...
15:34:02 <mboddu> File a bz against dnf and close this?
15:34:19 <nirik> well, I am sure they will ask for more info...
15:35:34 <nirik> I think perhaps we should try and duplicate it in a rhel8 mock chroot and run with more debugging...
15:38:25 <nirik> it could be koji not setting that modular hotfixes thing, but it's always been set before.
15:39:16 <mboddu> It is set `mock.yum.module_hotfixes : 1 [epel8]`
15:42:37 <nirik> so, I thiink we should investigate more... but out of meeting. ;)
15:42:43 <jednorozec> ack
15:43:28 <jednorozec> next one
15:43:31 <jednorozec> .releng 10513
15:43:32 <zodbot> jednorozec: Issue #10513: Disk images have significantly increased in size with Fedora 35 - releng - Pagure.io - https://pagure.io/releng/issue/10513
15:43:35 <jednorozec> can we close this?
15:45:31 <nirik> hum
15:46:10 <jednorozec> there is this https://bugzilla.redhat.com/show_bug.cgi?id=1971186
15:46:25 <jednorozec> but it is quiet there
15:47:10 <jednorozec> hm there is this as well https://bugzilla.redhat.com/show_bug.cgi?id=2031215
15:48:06 <jednorozec> ok, so this is still an issue
15:48:24 <jednorozec> But I am not sure how much we can do here
15:48:27 <nirik> well, that lorax patch was merged late last year
15:48:40 <nirik> so, I think we are already using it?
15:49:29 <jednorozec> there is QA comment from feb https://bugzilla.redhat.com/show_bug.cgi?id=2031215#c17
15:50:36 <jednorozec> so yeah we should be using the patch
15:51:16 <nirik> I guess we should check f34 vs f36 sizes?
15:52:14 <jednorozec> hmm
15:52:31 <jednorozec> so there is not much of a difference between f34 aarch image size and f36 one
15:54:32 <mboddu> They are still higher in F35, but close to F35
15:54:36 <nirik> yeah, so we are back to I think we can close it..
15:54:42 <jednorozec> something like 90MB if I am correct
15:54:51 <jednorozec> that can be explained by SW updates
15:54:55 <jednorozec> ack closing
15:56:40 <jednorozec> oh we are almost at the end
15:56:42 <jednorozec> #topic Open Floor
15:56:50 <jednorozec> Anything for the open floor?
15:57:24 <jednorozec> And I will answer myself
15:57:25 <jednorozec> yes
15:57:44 <jednorozec> so nirik mboddu are you ok if I reschedule this meeting in CPE calendar to be in UTC time?
15:58:37 <nirik> what utc time?
15:58:45 <jednorozec> the same but UTC
15:58:48 <jednorozec> so it wont float
15:59:03 <nirik> 15UTC?
15:59:03 <jednorozec> in the calendar
15:59:15 <jednorozec> yeah I think that is the tiem it should be in
15:59:38 <nirik> I'm fine with that... I might be less fine with it in the fall. ;)
15:59:42 <mboddu> jednorozec: Its your meeting now (or in 2 weeks :) ), so its up to you all
16:00:18 <jednorozec> w8 no other meeting I have scheduled in UTC are not floating around
16:01:21 <jednorozec> anyway that is it for today
16:01:27 <jednorozec> #endmeeting