18:00:09 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:09 <nirik> #chair cverna mboddu nirik smooge
18:00:09 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:09 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:09 <zodbot> Meeting started Tue Mar 10 18:00:09 2020 UTC.
18:00:09 <zodbot> This meeting is logged and archived in a public location.
18:00:09 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:09 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:09 <zodbot> Current chairs: cverna mboddu nirik smooge
18:00:09 <nirik> #topic Tickets needing review
18:00:10 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:16 <nirik> anyone around today to stand up?
18:00:37 * mboddu is here
18:00:48 <nirik> .ticket 8735
18:00:49 <cverna[m]> Hello
18:00:49 <zodbot> nirik: Issue #8735: Update default CC list for pcp package bugs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8735
18:01:06 <nirik> this should be all doable via the pagure users/groups no?
18:01:16 <smooge> woops.. sorry
18:01:34 <nirik> I'll ask them to use that and see if it doesn't work
18:02:11 <smooge> i was wondering if the problem was that these people were getting cc'd from old bugzilla permissions
18:02:45 <smooge> aka these people are listed as watching these packages so get cc'd on every new ticket
18:03:00 <smooge> I didn't think this was something we controlled
18:03:17 <fm-admin> pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8735 https://pagure.io/fedora-infrastructure/issue/8735
18:03:18 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8735: "Update default CC list for pcp package bugs" https://pagure.io/fedora-infrastructure/issue/8735#comment-632132
18:03:42 <nirik> yeah, they could be watching, but then it's up to them to remove themselves no?
18:04:09 <smooge> like i said.. i wasn't sure this was a problem we could solve
18:04:24 <smooge> but will see from clarification
18:05:05 <nirik> I think there's an api endpoint to change / show watchers
18:05:31 <cverna[m]> Yes I think so too
18:05:32 <nirik> https://src.fedoraproject.org/api/0/rpms/pcp/watchers
18:05:56 <nirik> but I don't think there's a way to change watchers as the admin of a project
18:06:26 <nirik> anyhow, that was the only needsreview.
18:06:34 <nirik> any other tickets we want to discuss today?
18:07:05 <mboddu> Yes, I have one for cverna[m]
18:07:12 <mboddu> .releng 9308
18:07:13 <zodbot> mboddu: Issue #9308: F33 system wide change: Sqlite Rpmdb - releng - Pagure.io - https://pagure.io/releng/issue/9308
18:07:36 * cverna[m] hides
18:07:51 <mboddu> I dont think it will affect any of the container building
18:08:11 <mboddu> But just wanted to check if it has any other impacts before I close the ticket
18:08:22 <nirik> oh I have one too for mboddu and cverna[m]... https://bugzilla.redhat.com/show_bug.cgi?id=1807679 (any issues you can see with openh264 being enabled in containers?)
18:09:26 <cverna[m]> the only downside is that it will take longer to build the dnf metadata cache
18:09:27 <nirik> so we need to carry a newer rpm for builders. again. ;(
18:09:46 <cverna[m]> but other than that I don't see any problem
18:10:03 <mboddu> cverna[m]: Okay
18:10:26 <cverna[m]> for the sqlite I guess we just need to make a new release when the change lands
18:10:29 <nirik> or override things to use the old db format until builders are upgraded to the new one
18:10:31 <fm-admin> pagure.issue.comment.added -- nathans commented on ticket fedora-infrastructure#8735: "Update default CC list for pcp package bugs" https://pagure.io/fedora-infrastructure/issue/8735#comment-632135
18:10:32 <cverna[m]> with the new version of rpm
18:11:23 <mboddu> nirik: Right that is a problem
18:12:58 <nirik> we could/should ask how to override the sqlite choice... if we can do that in mock/koji that would be much easier than carrying a rpm in infra tags
18:13:20 <mboddu> I will update the ticket
18:13:49 <nirik> +1
18:14:31 <mboddu> And going back to openh264 thing, I am not sure if there is a way to solve it
18:15:23 <fm-admin> pagure.issue.edit -- mymindstorm edited the close_status and status fields of ticket fedora-infrastructure#8734 https://pagure.io/fedora-infrastructure/issue/8734
18:15:24 <fm-admin> pagure.issue.comment.added -- mymindstorm commented on ticket fedora-infrastructure#8734: "[PATCH] Fix mixed content on fedorapeople user pages" https://pagure.io/fedora-infrastructure/issue/8734#comment-632136
18:15:27 <smooge> is that going to cause problems with building for el6->7 packages?
18:16:37 <cverna[m]> mboddu: which package is installing the default repos ?
18:16:51 <cverna[m]> for the openh264 bit
18:16:55 <mboddu> cverna[m]: fedora-repos package
18:16:56 <nirik> smooge: if we can't override it wanting to do sqlite, then possibly ye
18:17:43 <mboddu> I guess we can create a subpackage
18:17:54 <cverna[m]> could we have a subpackage for the openh264 that is a weak dep
18:17:58 <cverna[m]> ha yes :)
18:18:14 <mboddu> Yes, thats what what I am thinking
18:18:33 <Eighth_Doctor> wait, what's going on?
18:19:19 <smooge> multiple things
18:19:37 <Eighth_Doctor> nirik: koji builders can have %_db_backend set in koji tag to set back to bdb
18:19:50 <Eighth_Doctor> that will export back out as an rpm macro to override everything
18:20:16 <nirik> cool, as long as there's something and old db keeps working.
18:20:17 <Eighth_Doctor> not that it matters, since we don't use bootstrap chroots in koji yet, so the setting on the host is what matters regardless
18:21:12 <nirik> ok, anything more on either of those? or other tickets?
18:21:21 <Eighth_Doctor> I'm not sure why we need to care, from a koji perspective, the setting in the target environment doesn't matter
18:21:28 <Eighth_Doctor> we never use in-chroot rpm for anything
18:21:41 <Eighth_Doctor> we even pass --nodeps to avoid using the inevitably broken rpmdb
18:22:07 <Eighth_Doctor> mboddu: what's wrong with openh264?
18:22:36 <mboddu> Eighth_Doctor: https://bugzilla.redhat.com/show_bug.cgi?id=1807679#c9
18:22:41 <nirik> because it will cause problems for epel potentially.
18:23:20 <Pharaoh_Atem> it _shouldn't_
18:23:50 <mboddu> Eighth_Doctor: Concern about having openh264 repos enabled in container images which might pull the openh264 stuff because of some weak deps
18:24:07 <Pharaoh_Atem> mboddu: aren't our container base images built via ks?
18:24:14 <Pharaoh_Atem> everything built through ks can't get openh264
18:24:23 <nirik> well, I don't really want to argue about it in a meeting...
18:24:32 <Pharaoh_Atem> only the stuff that uses raw pungi gather might be an issue, but you mentioned that pungi handles this specially anyway
18:24:52 <Pharaoh_Atem> nirik: insofar as epel incompat, I can test this with regular mock and see
18:24:56 * nirik notes again we are just discussing blockers and next steps, we aren't actually doing the work on all these. or else this 30min standup will be 45 hours long
18:25:03 <cverna[m]> I think we can close the meeting and then continue the convo :)
18:25:16 <Pharaoh_Atem> worst case, we need to make koji people make bootstrap work or get rhel to backport :)
18:25:16 <mboddu> Yeah
18:25:24 <nirik> sure, as long as there are no other tickets people want to discuss...
18:25:38 <cverna[m]> I am fine :)
18:26:27 <nirik> ok then... thanks all
18:26:29 <nirik> #endmeeting