17:01:54 #startmeeting RELENG (2018-06-28) 17:01:54 Meeting started Thu Jun 28 17:01:54 2018 UTC. 17:01:54 This meeting is logged and archived in a public location. 17:01:54 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:54 The meeting name has been set to 'releng_(2018-06-28)' 17:01:54 #meetingname releng 17:01:54 The meeting name has been set to 'releng' 17:01:54 #chair nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin dustymabe 17:01:54 #topic init process 17:01:54 Current chairs: Kellin dustymabe masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 17:02:05 morning 17:02:25 morning nirik 17:05:18 Okay, lets get started 17:05:44 #topic #7589 Bug 1575762: Installation of F28 fails on systems using RAID 17:05:53 #link https://pagure.io/releng/issue/7589 17:06:10 So, we briefly discussed about this yesterday on releng channel 17:06:30 Should we take it to FESCo or just say its not doable? 17:06:55 I haven't looked at the bug much yet... let me see. we may also want adamw's thoughts on it. 17:07:54 we really don't redo media... so I would likely think more a common bug / make sure it's fixed in f29 17:08:21 Okay, let me ping adamw on the ticket 17:11:42 I asked adamw to join this meeting, so that we can get his final thoughts and close the ticket 17:12:00 they're requesting an ISO respin? 17:12:48 Yes 17:13:16 adamw: we really don't redo media... so I would likely think more a common bug / make sure it's fixed in f29 (few min back) 17:13:35 yeah, we've not-respun for more serious things in the past, i don't see how this is a respin. 17:13:45 it would be good to figure out a documentable workaround for common bugs, i guess. 17:13:55 so it's seeing the raid + each disk in the raid as duplicates? 17:14:22 it's not really clear to me the case here... I have several raid machines and have had no problems with f28. (but they were upgrades) 17:15:20 ah, it's in vmware? 17:15:49 [ 2.358531] fedora-test3.local.nonet kernel: scsi 2:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2 17:16:41 nirik: huh 17:16:56 Seems like a special case 17:18:13 adamw: Now that its under your radar, I will close the ticket, thanks for joining 17:18:28 thanks nirik 17:18:32 perhaps mark it common-bug to write up? 17:18:35 nirik: https://bugzilla.redhat.com/show_bug.cgi?id=1575762#c12 seems intstructive 17:19:32 yeah... wonder how long ago those older raid metadata would be from tho... 17:19:45 and lvmetad comes up by default normally 17:22:01 my raid is using 1.0 and I made it apparently 5 years ago. 17:25:02 anyhow, yeah, document and move on. if they want to escalate it, they can take it to fesco 17:25:38 #info Closing the ticket as we generally wont respin the images and mark is as common-bug to document it. 17:25:42 nirik: Thanks 17:27:03 #topic #7553 Arch-Specific Runtime Dependencies in sub-packages 17:27:11 #link https://pagure.io/releng/issue/7553 17:27:40 So, we discussed this last time and we thought of asking koji team 17:28:21 Now that we got their response, what is the best thing to do here 17:32:03 perhaps ask reporter if that answers the question and we can close, or if there's something further they wanted. 17:32:07 I prefer making the main and sub package arch specifc for now 17:32:45 So, that we dont have to remember to block certain things on certain arches 17:33:01 * nirik nods 17:33:26 Okay, I will ask the reporter in the ticket 17:36:41 #info mboddu will ask the reporter in the ticket if the proposals answers his question. 17:37:40 #topic #7445 [RFE][PATCH] make $releasever return "rawhide" on Rawhide 17:37:46 #link https://pagure.io/releng/issue/7445 17:39:55 Its been a long time we discussed about this 17:40:39 might be worth bringing up on devel/qa lists... 17:42:02 I guess I can try and write something up for that. 17:42:08 Okay 17:42:27 * mboddu is skeptical about changing repo files 17:42:40 That will definitely will break something somewhere 17:43:44 well.. without changing things too much... 17:43:57 we can count on mirrormanager to map rawhide to the right number. 17:44:15 I like that idea 17:44:25 the only way we could do better I guess is to drop the 'rawhide' name... always use the number. 17:44:38 but that also would be disruptive. 17:44:58 nirik: I think that might start a big war 17:45:03 :) 17:45:12 not sure... 17:45:48 I can write something up and we can get a nice long feedback from everyone. ;) 17:46:02 #info nirik will write up something and will take it to devel/qa lists 17:46:11 Thanks nirik 17:46:48 * mboddu got to run early, so I will take up the open floor and alt arch updates now 17:47:04 #info Alternate arch updates 17:47:15 sharkcz: If you are around, any updates? 17:47:33 nirik: Also, whats the status on moving s390 koji builders to primary koji 17:47:35 ? 17:47:52 Have you heard anything from the people who is working on it? 17:47:53 the same as it has been. There's a ticket. No movement on it yet 17:47:55 no 17:48:03 Okay 17:48:30 nirik: Is it sysops who has to work on it? 17:48:55 it's one of the folks that admins that mainframe... not sure how many of them there are. 17:49:06 Okay 17:49:29 #info we are still waiting on moving s390 koji builders to primary koji 17:49:39 #topic Open Floor 17:50:10 I guess everyone submitted their talks for FLOCK 17:50:28 yep. ;) 17:50:37 oh, I had just a few quick things for open floor.. 17:50:38 * mboddu is really interested in nirik's talk about compose failures/debugging 17:50:44 Sure 17:51:14 * next monday/tuesday infrastructure is doing a mass update/reboot outage(s)... so we may want to not push updates those days to avoid problems. 17:52:14 Kellin: ^ FYI, as you are on push duty next week 17:52:39 * nirik tries to recall the other thing... what was it. 17:53:24 I can't recall. Oh well, it will come to me. 17:53:52 mboddu: nod 17:54:09 nirik: You just have to search it in the pile of sticky notes that occupied your desk :P 17:54:24 s/desk/brain/ :) 17:54:38 Hehe 17:55:10 #info nirik has one more update which is currently a suspense 17:55:27 SUSPENSE 17:55:37 ha. 17:55:47 I'll bug you all on #fedora-releng if I can think of it. 17:55:49 Hehe, anything else guys? 17:55:54 nirik: Sure 17:56:26 Okay, I have to go, thanks guys for joining 17:56:34 #endmeeting