16:00:18 <jednorozec> #startmeeting RELENG (2021-12-07)
16:00:18 <zodbot> Meeting started Tue Dec  7 16:00:18 2021 UTC.
16:00:18 <zodbot> This meeting is logged and archived in a public location.
16:00:18 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:18 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:18 <zodbot> The meeting name has been set to 'releng_(2021-12-07)'
16:00:18 <jednorozec> #meetingname releng
16:00:18 <jednorozec> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
16:00:18 <zodbot> The meeting name has been set to 'releng'
16:00:18 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
16:00:27 <nirik> morning
16:00:27 <jednorozec> #topic init process
16:00:51 <jednorozec> morning nirik
16:01:47 <nirik> how's things?
16:04:05 <jednorozec> Snow, some more snow. Sometimes in the evening we get more snow.
16:04:19 <jednorozec> Sometimes the snow is there in the morning
16:05:08 <nirik> ha
16:05:15 <nirik> just fog and rain here.
16:05:40 <jednorozec> Oh we got frozen fog last week :D
16:05:43 * sharkcz is here today
16:07:23 <jednorozec> #topic tickets
16:07:38 <jednorozec> .releng 10414
16:07:39 <zodbot> jednorozec: Issue #10414: F36: System wide change: LLVM-14 - releng - Pagure.io - https://pagure.io/releng/issue/10414
16:08:01 <jednorozec> this got my attention, I checked previous change requests and they never asked for this
16:10:09 <nirik> wow... yeah, that sounds poor to me.
16:10:56 <nirik> make me 20,000 branches I will use for a few weeks...
16:11:16 <nirik> sorry, 34,000
16:11:16 <jednorozec> that
16:12:02 <nirik> oh, it's less than everything
16:12:18 <nirik> 15
16:12:24 <nirik> whew. Glad I misread it. ;)
16:13:15 <nirik> so they could just do this themselves right? but the branches can never be deleted.
16:13:25 <jednorozec> right
16:13:45 <jednorozec> do we want them to do that?
16:14:28 <jednorozec> Isn't the purpose of rawhide to break things?
16:14:37 <nirik> I guess it sounds ok...
16:14:48 <nirik> well, no. it's to integrate things...
16:15:01 <nirik> but if you know something is going to be broken for a while, you shouldn't normally land it...
16:16:17 * nirik reads the change
16:17:31 <sharkcz> I think they can create private branches and use copr with builds from the private branches
16:17:35 <nirik> so, I have questions...
16:18:06 <nirik> well, I am not sure what good the llvm-14 branches and sidetag does them... it's not merged until after the rc.
16:19:08 <nirik> so, I guess lets comment with our concerns/ideas on the ticket then?
16:19:27 <sharkcz> ack
16:24:06 <jednorozec> Ok
16:25:00 <jednorozec> I need to get through the changes. There seems to be some interesting ones, but at first glance most of them are no-releng
16:25:47 * nirik nods
16:26:42 <mboddu> Sorry, a bit side tracked, but need couple more min
16:30:11 <jednorozec> .releng 10394
16:30:12 <zodbot> jednorozec: Issue #10394: Unretire script doesn't properly unretire packages - releng - Pagure.io - https://pagure.io/releng/issue/10394
16:31:07 <jednorozec> I have an update here. There seem to be failing tests in pagure when I run them as part of pagure-distgit
16:32:30 <jednorozec> and it brought the idea of automating unretirement using toddlers.
16:33:06 <nirik> how would that workflow work?
16:33:47 <jednorozec> Toddler will listen to the new unretirement ticket in releng repo. Try to parse it based on a template.
16:34:21 <nirik> hum... possibly workable
16:34:28 <jednorozec> Comment on the ticket in correct format unless users input matches the template
16:34:57 <jednorozec> than it is just about calling the right api endpoints
16:35:12 <jednorozec> and git revert HEAD && git push
16:35:44 <mboddu> Rather than a toddler, we can make use of pagure-dist-git thing, just like the unorphan thing
16:35:55 <jednorozec> hmmm
16:36:28 <nirik> well, the problem is that unretire needs to check for the re-review (sometimes)
16:36:46 <jednorozec> that we can get from git log
16:37:31 <jednorozec> but having a ticket seems good, for tracking purposes.
16:37:35 <nirik> the amount of time? yeah...
16:37:54 <mboddu> https://pagure.io/pagure-dist-git/blob/master/f/pagure_distgit/plugin.py#_339
16:38:01 <nirik> I suppose a unretire pagure-dist-git button could work... it would be more complex than the unorphan one...
16:38:30 <jednorozec> yes but orphan is just a field in db
16:38:35 <nirik> if the retirement is less than 8 weeks or whatever, just do it, if not, ask the user for a review bug number, check bug is Package Review and approved
16:40:31 <nirik> it would definitely be nice to automate out of releng needing to do anything. ;)
16:41:11 <jednorozec> Well we should at least get the report
16:41:51 <jednorozec> anyway that it all i got
16:41:59 <jednorozec> #topic Open Floor
16:42:38 <pmoura> well I have something to share
16:42:39 <nirik> So, we setup a releng time mondays to go over old backlog, but I missed yesterday and the one before...
16:42:50 <nirik> should we cancel that? or reschedule?
16:43:05 * nirik had another thing after pmoura
16:43:20 <jednorozec> pmoura, go on
16:43:38 <pmoura> thanks nirik.. Im having a hard time with grokmirror, I still dont understand how the manifest have branches from repos in it... soo if someone here could help...
16:44:43 <pmoura> .releng 10270
16:44:44 <zodbot> pmoura: Issue #10270: Refresh Grokmirror manifest - releng - Pagure.io - https://pagure.io/releng/issue/10270
16:45:54 <nirik> well, I think it's supposed to have everything... but not sure on the branch handling either.
16:48:06 <nirik> I can try and look at it later this week... or someone else could. ;)
16:49:06 <pmoura> thanks :)
16:49:29 <jednorozec> I have 0 experience with grokmirror, but can look into it after I am done with changes in current unretirement
16:50:19 <jednorozec> as it goes for the cleanup meeting, Mondays and Fridays are not really good days for meetings...
16:50:35 <nirik> For the last things: I upgraded builders in stg, but hit the koji fedmsg plugin being broken ( https://pagure.io/koji-fedmsg-plugin/issue/16 ). Once that gets fixed we can move on to prod... Also, I am out till Jan 4th after this week, so please catch me if you need something from me.
16:50:55 <nirik> jednorozec: I setup grokmirror so long ago, I don't remember it any either. ;(
16:53:21 <jednorozec> if we do the cleanup by-weekly I dont mind having it 16 or 17:00 UTC
16:53:49 <nirik> we could also try and use 1/2 the meeting for that or something...
16:54:03 <mboddu> pmoura: Can you take a look at https://pagure.io/fedora-infra/ansible/pull-request/900#comment-162823 ?
16:54:05 <jednorozec> we did that couple of times
16:55:31 <nirik> yeah. I might also get bored on PTO and cull through them again.
16:56:07 <pmoura> yes mboddu, I just replied it before joining here
16:56:24 <mboddu> pmoura: Sorry, I didn't check
16:56:56 <nirik> pmoura: oh, I don't know if you saw, I also updated the reinstall builders with f35 ticket with a bunch of info. If you could look at starting a SOP with that we can add to it as we go...
16:57:01 <jednorozec> nirik, you should try tinkering with electronics, to have some other computer hobby than fedora
16:57:05 <nirik> or we can just do the sop after too. :)
16:57:31 <nirik> I also still need to setup my jetson aarch64 board and also a riscv box.
16:57:38 <pmoura> mboddu: no worries, but Ishould say.. dont understand what carl said in the issue
16:58:44 * jednorozec is REALLY patiently waiting for his riscv HW
16:59:40 <pmoura> nirik: yes, put that in my todo list. Didnt started because I was checking grokmirror and epel symlink issue this morining. Probably Ill start it after lunch
17:00:32 <nirik> no worries. Just wanted to make sure you saw the message... no great rush
17:01:47 <jednorozec> and the time is up
17:01:50 <jednorozec> #endmeeting