releng
LOGS
17:00:15 <jednorozec> #startmeeting RELENG (2023-11-14)
17:00:15 <zodbot> Meeting started Tue Nov 14 17:00:15 2023 UTC.
17:00:15 <zodbot> This meeting is logged and archived in a public location.
17:00:15 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
17:00:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:15 <zodbot> The meeting name has been set to 'releng_(2023-11-14)'
17:00:19 <jednorozec> #meetingname releng
17:00:19 <zodbot> The meeting name has been set to 'releng'
17:00:21 <jednorozec> #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
17:00:21 <zodbot> Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz
17:00:23 <jednorozec> #topic init process
17:00:28 <nirik> morning
17:00:32 <pcreech> .hello pcreech17
17:00:34 <zodbot> pcreech: pcreech17 'Patrick Creech' <pcreech@redhat.com>
17:00:40 <patrikp> .hi
17:00:41 <zodbot> patrikp: patrikp 'Patrik Polakovič' <ppolakov@redhat.com>
17:02:45 <jednorozec> hello everyone
17:05:00 <jednorozec> I dont have any specific topic to discuss today, just few updates on things
17:06:01 <jednorozec> .releng 11723
17:06:02 <zodbot> jednorozec: Issue #11723: Remove PDC from package retirement process - releng - Pagure.io - https://pagure.io/releng/issue/11723
17:06:22 <jednorozec> I tried to run the script on prod pkgs today
17:06:29 <jednorozec> around 7:00 UTC
17:06:56 <nirik> cool. thats much faster than I thought it would be
17:07:11 <nirik> how often would it run? daily?
17:07:20 <jednorozec> so
17:07:28 <jednorozec> I am not sure if that will be needed
17:08:02 <jednorozec> We are catching all manipulation with dead.package in toddlers
17:08:23 <jednorozec> so newly retired and unretired packages can be just updated on that list
17:09:24 <nirik> yeah, in the past with services that updated with messages, we also had a regular job that could generate the list in case messages were lost...
17:09:27 <jednorozec> btw I think its not that slow/greedy because git operations tend to be pretty optimized
17:09:51 <nirik> ie, the koji sync thing runs on messages, but once a day the scriupt runs to make sure it didn't miss any
17:10:19 <jednorozec> right
17:10:35 <nirik> so I think it would be good to generate entire on some cadience... but it could be weekly even probibly
17:11:33 <jednorozec> at least lenka can continue now she just needed some endpoint to point to.
17:12:24 * nirik nods
17:13:00 <jednorozec> we will add it to ansible tmrw but deploy it only to staging to see if somethings unexpected comes up
17:13:37 <nirik> great!
17:15:00 <jednorozec> .releng 11773
17:15:01 <zodbot> jednorozec: Issue #11773: No new stable Silverblue/Kinoite/Sericea/Onyx compose since 39.20231103.n.0 - releng - Pagure.io - https://pagure.io/releng/issue/11773
17:15:27 <jednorozec> so
17:15:46 <nirik> yeah, there is history here.
17:16:11 <nirik> oh, this is the ref thing
17:16:18 <jednorozec> yes the ref thing
17:16:24 <jednorozec> its back in the SOP
17:16:35 <nirik> +1... can close
17:17:00 <nirik> but...
17:17:07 <jednorozec> also there is last comment not relevant for the issue itself but was also a miss in the scripts
17:17:54 <nirik> ok, thats where I am getting mixed up
17:18:23 <nirik> the updating containers post ga thing
17:18:46 <jednorozec> yes, it was missing in the container-nightly
17:18:53 <nirik> for ostree ones we should do this... base/minimal we haven't in the past
17:20:16 <nirik> and that looks like whats proposed... so +1 ;)
17:20:16 <jednorozec> there are PRs in pungi-fedora so closing
17:20:50 <nirik> we have talked about updating the base/minimal ones too... orig the containers sig was supposed to test and release some from time to time...
17:21:39 <jednorozec> its probably good idea to have some sanity check
17:22:32 <nirik> yeah. we can discuss with QE...
17:24:27 <jednorozec> .releng 11780
17:24:28 <zodbot> jednorozec: Issue #11780: I cannot create an epel9 branch for perl-HTML-Scrubber - releng - Pagure.io - https://pagure.io/releng/issue/11780
17:24:31 <jednorozec> just closing it
17:24:54 <nirik> +1
17:25:23 <jednorozec> this is ne
17:25:28 <jednorozec> .releng 11781
17:25:29 <zodbot> jednorozec: Issue #11781: Special buildroot-only tagging for glibc32 - releng - Pagure.io - https://pagure.io/releng/issue/11781
17:27:13 <jednorozec> should I just tag them there?
17:27:16 <nirik> yep
17:27:22 <nirik> it's a weird corner case thing.
17:27:35 <jednorozec> let me do that right now
17:31:03 <jednorozec> .releng 11782
17:31:04 <zodbot> jednorozec: Issue #11782: Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration - releng - Pagure.io - https://pagure.io/releng/issue/11782
17:31:14 <jednorozec> releng@fp.o user should be able to do this?
17:31:42 <nirik> no.
17:32:23 <nirik> because if we just change it, our sync will change it back. it needs to be changed right... ie, a group made with that address, then the packages main admin changed to group
17:33:12 <nirik> at least thats my first thought on it. ;)
17:33:22 <jednorozec> ha
17:33:55 <jednorozec> and it will be synced by the bz sync toddler
17:34:06 <nirik> yeah
17:36:09 <nirik> I can try and do this later in the week...
17:37:03 <jednorozec> or I can with samyak he should be back later this week, and I think he has the ACLs to change package assignee's
17:37:19 <jednorozec> I can create the group
17:37:42 <jednorozec> .releng 11768
17:37:43 <zodbot> jednorozec: Issue #11768: Update IoT signing keys - releng - Pagure.io - https://pagure.io/releng/issue/11768
17:37:55 <jednorozec> do we have any process for this or just wait for the ticket?
17:38:10 <jednorozec> there was couple of request the day before the release got live...
17:38:21 <jednorozec> but can be closed
17:39:37 <nirik> there's a howto on it. you have to do a number of steps... zlopez also has done them
17:39:46 <nirik> (this is about the group)
17:40:06 <jednorozec> I mean more like can we make them to request it sooner that day before things go live?
17:40:08 <nirik> the iot signing is all done, can be closed
17:40:33 <jednorozec> I can do that and did for previous releases its just unfortunate to do this the day before...
17:40:35 <nirik> I'm not sure... we can ask them?
17:41:29 <jednorozec> right close and ask
17:41:41 <jednorozec> .releng 11761
17:41:42 <zodbot> jednorozec: Issue #11761: missing artifacts from f39-rc-1.5 (final release) - releng - Pagure.io - https://pagure.io/releng/issue/11761
17:42:09 <jednorozec> so about the torrents
17:42:38 <jednorozec> my idea is to drop the missing torrent folders/files in place and regenerate the torrent.ini
17:42:48 <jednorozec> restart tracker and it should pick them up?
17:43:40 <jednorozec> basically just do the steps from 11. https://docs.fedoraproject.org/en-US/infra/release_guide/torrentrelease/
17:44:15 <nirik> I guess. I don't like the fact that the respin ones would then just look like the same as the release ones, but I guess that could just be me. ;)
17:44:19 * jednorozec jsut want to make sure the tracker will not break
17:44:41 <jednorozec> they have -respin in name
17:44:44 <nirik> I need to move that vm to rhel9 I guess. People keep using torrents...
17:44:58 <jednorozec> torrents never die
17:46:06 <nirik> they are a lot less popular than they used to be....
17:46:21 <nirik> I guess I could gather some stats and ask about killing them again...
17:46:25 <jednorozec> internet connections got much better
17:46:56 <jednorozec> that is all i had
17:47:31 <nirik> yep. most people just direct download from a mirror anymore.
17:48:02 <nirik> so, I am still planning/hoping to get time to write up a 'reinstall builders' thing... will submit a PR and you can do stg based on it.
17:48:14 <nirik> I have a mass update/reboot outage scheduled for tomorrow.
17:48:19 <nirik> going to do staging today.
17:49:10 <nirik> .releng 11751
17:49:11 <zodbot> nirik: Issue #11751: libssh2-devel seems to be missing from the EPEL7 x86_64 buildroot - releng - Pagure.io - https://pagure.io/releng/issue/11751
17:49:18 <nirik> I think I can close this one
17:49:37 <jednorozec> I think I am able to do the reinstall, but it would be much less stress full to have some reference document
17:50:09 <nirik> yeah. I hope to work on it this afternoon if people will stop pinging me. ;)
17:50:26 <nirik> .releng 11680
17:50:26 <zodbot> nirik: Issue #11680: EPEL9 not listed in MDAPI branches - releng - Pagure.io - https://pagure.io/releng/issue/11680
17:50:29 <nirik> where was this one?
17:50:47 <jednorozec> github
17:50:49 <jednorozec> let me find it
17:51:25 <jednorozec> https://github.com/fedora-infra/mdapi/pull/225
17:51:28 <jednorozec> got merged
17:51:37 <jednorozec> mdapi needs new release and it should be working
17:52:14 <nirik> I think it's done actually.
17:52:29 <jednorozec> deploy from master :)
17:52:42 <nirik> hum, or perhaps not?
17:52:54 <jednorozec> nope
17:52:57 <jednorozec> its not there
17:53:09 <pcreech> (insert obligatory 'one does not simply deploy from master' joke)
17:53:32 <nirik> yeah, it's not. so, still needs deployment
17:54:03 <jednorozec> yeah guys have holidays over there
17:54:29 <jednorozec> they should be back tmrw I will ping around
17:56:38 <nirik> no worries.
17:56:43 * nirik has nothing more off hand.
17:57:21 <jednorozec> Any other topics?
17:57:28 <jednorozec> #topic Open floor
17:58:00 * jednorozec needs to take a photo of his opened floor in one of the rooms for this occasion
17:58:40 <Southern_Gentlem> jednorozec, did you ever get that blog post on how to create updated server isos
17:58:51 <jednorozec> Southern_Gentlem, Yes!
17:59:00 <Southern_Gentlem> link please
17:59:26 <jednorozec> but my build jobs failed, and now alma 6.3 autoupdated on me and zfs didnt load
17:59:54 <jednorozec> give me few minutes
17:59:58 <Southern_Gentlem> ok
18:00:13 <jednorozec> #endmeeting