16:00:11 #startmeeting Infrastructure (2020-01-07) 16:00:11 Meeting started Thu Jan 7 16:00:11 2021 UTC. 16:00:11 This meeting is logged and archived in a public location. 16:00:11 The chair is siddharthvipul. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:11 The meeting name has been set to 'infrastructure_(2020-01-07)' 16:00:11 #meetingname infrastructure 16:00:11 The meeting name has been set to 'infrastructure' 16:00:11 #chair nirik pingou smooge cverna mizdebsk mkonecny abompard siddharthvipul mobrien 16:00:11 Current chairs: abompard cverna mizdebsk mkonecny mobrien nirik pingou siddharthvipul smooge 16:00:11 #info Agenda is at: https://board.net/p/fedora-infra 16:00:11 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:00:12 #topic aloha 16:00:31 morning. 16:00:33 hello everyone :D welcome! 16:00:39 .hi 16:00:39 and Happy New year :) 16:00:39 darknao: darknao 'Francois Andrieu' 16:00:44 nirik, \o 16:00:48 Hope everyone had a nice holiday! 16:00:58 .hello siddharthvipul1 16:00:59 siddharthvipul: siddharthvipul1 'Vipul Siddharth' 16:01:04 o/ everyone, and happy new year 16:01:41 .hi 16:01:42 mobrien: mobrien 'Mark O'Brien' 16:01:48 happy new year all 16:01:50 nirik, it was great for me.. did you do anything exciting? 16:01:56 mobrien, helloow 16:02:27 .hello zlopez 16:02:28 mkonecny: zlopez 'Michal Konečný' 16:02:29 nope, nothing exciting at all. Slept a lot, read a number of books, watched a bunch of shows. ;) 16:02:55 the better version of holiday then :P 16:03:08 I started a new project, wrote one blog post, so nothing unusual :-D 16:03:20 right, let's start with next topic to see if there is anyone new here 16:03:22 nirik, sounds similar to the time I had 16:03:26 mkonecny, that's full of activity :P 16:03:52 my christmas to new year is a blur and I have no idea what happened XD 16:03:54 too fast 16:03:59 Not really, it's one of those projects, you write the design for and then forgot about it :-D 16:04:29 #topic New folks introductions 16:04:29 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:04:29 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:04:36 soo, anyone new today? 16:04:51 we love having new people in this meeting 16:05:04 * pingou late 16:05:21 pingou, welcome :D 16:06:07 seems like we don't have any new members today :) let's move 16:06:50 #info 2020-12-31 - canceled 16:06:50 #info 2021-01-07 - siddharthvipul 16:06:50 #info 2021-01-14 - mobrien 16:07:10 we are looking a volunteer to chair 2021-01-21's meeting 16:07:12 do we have any? 16:07:37 I can do it 16:07:42 #info 2021-01-21 - mkonecny 16:07:46 thank you mkonecny :) 16:08:15 2 weeks ahead is enough, let's move to next topic 16:08:19 #topic announcements and information 16:08:20 #info CPE Infra&Releng EU-hours team has a Monday through Friday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:08:20 #info CPE Infra&Releng NA-hours team has a Monday through Friday 30 minute meeting going through tickets at 1800 UTC in #fedora-admin 16:08:20 #info Datacenter move is over, but some items still need to be done: see https://fedoraproject.org/wiki/Infrastructure/2020-post-datacenter-move-known-issues 16:08:38 I don't see a lot of new announcements.. I will wait for 3-5 minutes in case someone wants to add something :) 16:09:04 * siddharthvipul also realizes that it was a holiday season and nothing exciting would have heppened 16:09:09 s/heppened/happened 16:09:19 yeah, not much to announce... yet! 16:09:31 #info With the new quarter, we start working on new initiatives 16:10:43 #info mass rebuild for f34 coming up on 2021-01-20 16:10:50 \o/ 16:11:25 f33 mass rebuild seems like it was only last week 16:11:54 time flies when you are having fun! 16:12:01 :) 16:12:05 :) 16:12:54 thank you to everyone who added infos 16:13:07 #topic Oncall 16:13:08 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:13:08 #info noone was oncall for 2020-12-10 to 2021-01-07 16:13:30 we are looking for someone to be on call from today i.e 2021-01-07 to 2021-01-14 16:14:06 do we have a volunteer? I can take it if no one is interested 16:14:08 You can put me down for that 16:14:13 mobrien, nice 16:14:20 thanks mobrien 16:14:22 let's do both of us, I will take next week 16:14:43 #info mobrien is oncall for 2021-01-07 to 2021-01-14 16:14:44 #info siddharthvipul1 is oncall for 2021-01-14 to 2021-01-21 16:15:01 mobrien, want to go ahead and take the responsibility? 16:15:11 ## .oncalltakeeu or .oncalltakeus 16:15:16 .oncalltakeeu 16:15:16 mobrien: Kneel before zod! 16:15:23 mobrien++ 16:15:25 thanks siddharthvipul 16:15:29 thank you, you are the best 16:15:30 siddharthvipul++ 16:15:42 we are good people, out of cookies way too soon haha 16:15:55 #info Summary of last week: (from current oncall ) 16:16:03 #info invalid, as no one was on call 16:16:19 nirik, mobrien are we good with this? 16:16:27 yep 16:16:31 #topic Monitoring discussion [nirik] 16:16:31 #info https://nagios.fedoraproject.org/nagios 16:16:31 #info Go over existing out items and fix 16:16:45 ok, lets see 16:17:20 there's a aarch64 bvmhost down... it died over the holidays. ;( 16:17:27 need to get new drives for it. 16:17:49 siddharthvipul++ 16:17:51 I really must get you to show me how to diagnose/power cycle those boxes 16:18:07 otherwise there's only about 4 things left 16:18:14 pingou, ^.^ 16:18:17 we got a few toddlers notifications this week, sorry about those 16:18:33 missing faf messages... we should/could ping the retrace people about that and see if it's supposed to be sending them again... 16:18:46 low swap on a host (no biggie) 16:19:06 retrace-stg (which I never think was fully setup, so perhaps can be removed?) 16:19:21 and sign-bridge01.stg isn't running. that needs some debugging. 16:19:46 otherwise it looks pretty good. :) 16:20:33 so, move on I think. ;) 16:20:41 mobrien: yes! we should schedule a time to do that. 16:20:43 .thank nirik 16:20:45 siddharthvipul thinks nirik is awesome and is happy they are helping! (Please also type nirik++ since that is what gives them a cookie) 16:20:50 nirik++ 16:20:50 siddharthvipul: Karma for kevin changed to 22 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:20:57 nirik++ 16:21:03 * pingou is all out of cookie :( 16:21:06 oh wow, I hadn't given nirik a cookie, that's weird 16:21:08 mobrien++ 16:21:10 pingou++ 16:21:10 siddharthvipul: Karma for pingou changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:21:13 nirik++ 16:21:18 wth, where have I been? 16:21:23 mkonecny++ 16:21:23 siddharthvipul: Karma for zlopez changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:21:26 am I all out of cookie or is zodbot ignoring me, hm... 16:21:27 whaooo 16:21:33 okay, sorry to spam 16:21:40 pingou: same here 16:21:40 you all are just too good to not do this 16:21:47 we also need new release now haha 16:21:59 siddharthvipul++ 16:21:59 nirik: Karma for siddharthvipul1 changed to 13 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:22:11 mkonecny++ 16:22:11 nirik: Karma for zlopez changed to 6 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:22:17 nirik++ 16:22:24 cookie party. ;) 16:22:33 darknao++ 16:22:33 nirik: Karma for darknao changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:22:38 nirik, I was secretly conspiring to start one :P 16:22:44 darknao++ 16:22:47 siddharthvipul: Karma for darknao changed to 6 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:23:02 siddharthvipul++ darknao++ 16:23:02 mobrien: Karma for darknao changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:23:12 right, before someone decides I don't get to do this again, let's move haha 16:23:14 mobrien++ 16:23:22 mobrien++ 16:23:22 nirik: Karma for mobrien changed to 6 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:23:26 darknao++ 16:23:26 pingou: Karma for darknao changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:23:37 zodbot is nog ignoring me \ó/ 16:23:56 zodbot, c'mon.. do something (pokes with a stick) 16:24:16 It used to say when you already gave someone a cookie, but we dropped it for some reason, so it just doesn't do anything. :) 16:24:31 :P 16:24:48 that would have been nice though 16:25:42 #topic Learning topic 16:25:50 nirik, agenda says we are doing packager workflow 16:25:54 are we? :P 16:26:00 There is talk about re-implementing our bots on matrix at some point... we can revisit how it works then. ;) 16:26:08 sure! I can. 16:26:15 #info packager workflow [nirik] 16:26:56 So, this is a pretty broad topic, so I thought I would just go thru what I ususally do when upgrading a package for a new version in rawhide first, then we can go to other topics as people like... 16:27:43 Usually I get a bug from the-new-hotness once anitya has detected a new version of a package I maintain. Sometimes I know about it already, sometimes not. Depends on how involved with the package upstream I am. 16:28:00 The bug is nice as a place to discuss things too if needed. 16:28:50 Sometimes a bug will be filed and I don't want to update to the new version. It has requirements we can't meet yet, needs new things packaged, or... sometimes it's a alpha or beta or rc and it might not be stable enough. 16:29:06 but I try and record this in the bug for co-maintainers/interested folks. 16:29:27 Next I check out the package if I don't already have it checked out. Or update the git repo if I do. 16:29:40 (this pulls in any automated things people did, or co-maintainers, etc) 16:30:02 Next Update the version in the spec and add a changelog entry. 16:30:37 Bodhi now looks for bugs in changelogs, so I have been writing things as 'fixes rhbz#123456' in the changelog 16:30:56 this allows bodhi to close the update bug for you after you build it. 16:31:34 Then, I use 'spectool -g *spec' to get the new sources... if your Source line is right, this should just work. There are times when it won't, but they would be corner cases. 16:31:58 Then, check the sources if upstream has any checksums or signed files, etc... make sure you got the correct sources. 16:32:37 then a 'fedpkg prep' (this unpacks sources and applies all patches). THis tells me if patches need rebasing or dropping or otherwise something is wrong unpacking. 16:33:16 if that looks good, next I look at what depends on that package and how it changed. 16:33:50 I usually read NEWS/Changelog files, etc... if this is a library file and it's changing the library soname you need to rebuild everything that depends on it. 16:34:06 if it's just a python module or standalone app, you likely don't need to. 16:34:42 If it doesn't seem like anything else will need rebuilding, you can move on to test building. 16:35:04 I usually these days do a mock on my laptop first... it's a lot faster than koji, but it only does x86_64. ;) 16:35:29 if that builds fine I often install the package locally and test it. You could do this in a container, vm, etc. 16:35:49 Then I usually do a scratch build (this gets all the arches and the koji env). 16:36:37 If that looks good, time to do the real update. 'fedpkg new-sources ...' to upload the sources to lookaside cache. Then I usually do 'fedpkg commit -c -p' 16:36:50 that does a commit with your changelog entry and pushes it. 16:37:01 then 'fedpkg build' fires the official build. 16:37:42 I often do 'fedpkg build --nowait' which just fires off the build and returns. I get notificiation when the build is done anyhow, don't need to take up a teminal. 16:38:13 In rawhide, thats it, the build will finish, bodhi makes an update and tests it then pushes it stable and closes the bug. 16:38:50 If you have to rebuild other packages, you will need a side tag... 16:39:23 'fedpkg request-side-tag' will get one. 16:40:03 then you build like above, but you build into the side tag instead of the main build tag... and then get all the other dependent packages built in there too. 16:40:21 Then you make an update with bodhi and it bundles them all up and pushes them into rawhide. 16:40:46 For finding all dependent packages, I found a nice script the stewardship sig made... 16:41:08 https://github.com/fedora-stewardship/fedora-stewardship.github.io/blob/master/scripts/review_pr.py 16:41:45 if you make a PR against the packages (fork it, push changes to a branch on your fork, make pr) you can use that script to rebuild all dependent packages in copr for you. 16:42:21 for example... 16:42:31 there is a python-jwt update pending. 16:43:16 I made a commit for the update and then ran that script 16:43:26 https://copr.fedorainfracloud.org/coprs/kevin/python-jwt-2.0.0/builds/ 16:43:41 and those are all the packages that require it... and if they rebuilt with the new one or not. 16:44:15 https://bugzilla.redhat.com/show_bug.cgi?id=1909440 is the bug about the new version. 16:44:33 which I used to cc maintainers of the things that failed to coordinate with them. ;) 16:45:19 https://src.fedoraproject.org/fork/kevin/rpms/python-jwt/c/a1c4f8440a1d450cd79e48f881d54356d3e76161?branch=2.0.0 is the commit on my fork. I guess I never made a real PR yet on it, but the script just needs to know fork and branch. 16:45:30 hi 16:45:43 So, thats a lot of stuff there... any questions/areas to go over mode? 16:45:53 nirik, wow, what a detailed explanation 16:45:55 thanks a lot 16:46:06 especially the fedora-stewardship script, I didn't know about it 16:46:09 This looks like a plenty of work for each package 16:46:26 I am going to bookmark and share this with others.. 16:46:49 * siddharthvipul back in a minute, sorry 16:46:51 mkonecny: yeah, it can be... the simple case isn't too bad... but when you have dependent packages it can be complex/take a while 16:47:25 it also depends a lot on upstreams... some do lots of testing and are conservative. Others drop things right and left and move faster than the things that use them. ;( 16:47:42 hi dtometzki 16:48:26 thats a lot and great nirik, didn't realise just how much was involved 16:48:43 I have one news for you, the Anitya 1.0 should recognize nonstable versions from stable ones 16:48:54 mkonecny: oh nice! 16:49:25 nirik, I have a question.. maybe not "super" related 16:49:25 how i can support or help you ? 16:50:01 siddharthvipul: fire away. 16:50:18 dtometzki: are you looking for the fedora infrastructure meeting? if so, this is it. :) 16:50:22 I have been thinking of doing a survey around packagers workflow (have been talking to Adam Saleh about it who did some work on it last quarter).. my goal is to find pain points in the workflow 16:50:37 not all the things in workflow are touched by packagers directly 16:50:48 (say resultdb, greenwave for example) 16:51:18 nirik: yes i am little bit late sorry for that :-( 16:51:30 dist-git, bodhi, Fedora CI and gating and builders (koji) 16:51:54 are there anything else that works in frontend where we may want to take some feedback on? 16:51:57 nirik ^ 16:52:17 sure, might be a good idea. :) Note that there is a group of packagers that maintain.... a lot of packages (like the glang folks, or nodejs) and then a bunch of packagers that maintain much fewer. I think they have different workflows/needs, so you should be sure to try and get people from both groups 16:53:10 I think those are the highlights. ;) 16:53:36 dtometzki, welcome 16:53:36 nirik, fair enough.. what would be a nice way to gather ~100 packagers to get feedback from (I don't want to make it very wide.. that will make the result very hard to evaluate and generic surveys are also taken a bit less serious :P 16:54:09 dtometzki, heyy, no issues at all. Glad you joined! hopefully in next meeting we can discuss more :) 16:54:52 siddharthvipul: I guess ask on the devel list? or mail active packagers directly? 16:54:52 siddharthvipul: Ok perfekt :-) 16:55:17 nirik, later is what I had in mind.. but first option is not bad either.. 16:55:18 well anyway 16:55:28 if we don't have any question.. we can move to open floor :D 16:55:35 not a lot of time left 16:56:10 #topic Open Floor 16:56:31 Is this floor FOSS? 16:57:07 mkonecny, of course! anything else would be unacceptable 16:57:18 floss dance? https://en.wikipedia.org/wiki/Floss_(dance) 16:57:20 maybe it's not a software :P 16:57:43 now I have a favorite dance.. nice 16:57:45 :V 16:58:03 send us a video of your attempts nirik, siddharthvipul 16:58:21 What is the purpose of this dance? :-D 16:58:24 mobrien, oh you don't want to see me dance.. trust me 16:58:33 I think it came from fortnite 16:58:37 mkonecny, sharing happiness and innovation I presume 16:58:42 haha 16:58:59 sorry to hurry up this part people, we don't have a lot of time and next meeting in this channel is in 2 minutes 16:59:05 let's end the meeting? 16:59:16 Let's end this then 16:59:21 awesome 16:59:25 thank you all for joining, it was a good one 16:59:36 siddharthvipul++ 16:59:40 thanks 16:59:42 siddharthvipul: thanks for chairing 16:59:43 nirik, thanks again for explaining packagers workflow and answering the questions 16:59:48 siddharthvipul++ 16:59:48 mkonecny: Karma for siddharthvipul1 changed to 14 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:59:49 mkonecny, my pleasure :D 16:59:49 thanks fo chairing siddharthvipul 17:00:01 siddharthvipul++ 17:00:01 darknao: Karma for siddharthvipul1 changed to 15 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:00:06 #endmeeting