15:00:03 #startmeeting FESCO (2019-07-29) 15:00:03 Meeting started Mon Jul 29 15:00:03 2019 UTC. 15:00:03 This meeting is logged and archived in a public location. 15:00:03 The chair is ignatenkobrain. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:03 The meeting name has been set to 'fesco_(2019-07-29)' 15:00:13 #meetingname fesco 15:00:13 The meeting name has been set to 'fesco' 15:00:14 #chair nirik, ignatenkobrain, jforbes, zbyszek, bookwar, sgallagh, contyk, mhroncok, otaylor 15:00:14 Current chairs: bookwar contyk ignatenkobrain jforbes mhroncok nirik otaylor sgallagh zbyszek 15:00:20 .hello2 15:00:21 jforbes: jforbes 'Justin M. Forbes' 15:00:24 #topic init process 15:00:27 hey 15:00:28 .hello psabata 15:00:29 contyk: psabata 'Petr Šabata' 15:00:41 .hello2 15:00:42 bcotton: bcotton 'Ben Cotton' 15:00:47 morning 15:01:39 .hello2 15:01:40 otaylor: otaylor 'Owen Taylor' 15:02:19 .hello2 15:02:19 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 15:03:26 let's give few more minutes for others 15:04:59 ok, I guess we can start. 15:05:06 #topic #2179 python27 exception request for ptxdist 15:05:08 .fesco 2179 15:05:09 ignatenkobrain: Issue #2179: python27 exception request for ptxdist - fesco - Pagure.io - https://pagure.io/fesco/issue/2179 15:05:36 still -1 15:05:45 I guess. 15:05:54 Too bad we don't have a reply from besser82. 15:06:36 yeah, it sounds like we could just wait... but not fully clear 15:06:38 I'm fine if we give him more tiem to reply 15:06:46 *time 15:06:54 I'm 0 here. it does not require any dependencies outside of stdlib and it is not just this package blocking python2 removal 15:07:06 OK, so wait one more week, deny if still no answer? 15:07:16 I would be good with one more week 15:07:17 zbyszek: +1 15:07:23 for my sake it can wait even a month 15:07:24 +1 15:07:29 but +1, why not 15:07:29 to zbyszek, that is 15:07:44 +1 to zbyszek 15:09:29 otaylor: jforbes are you +1 to zbyszek 's proposal? 15:10:35 I already answered that, _1 15:10:37 #agree Wait for one more week, deny if no answer from besser82 (+5, 0, -0) 15:10:37 sure, +1 15:10:37 err +1 15:10:45 #undo 15:10:45 Removing item from minutes: AGREED by ignatenkobrain at 15:10:37 : Wait for one more week, deny if no answer from besser82 (+5, 0, -0) 15:10:53 #agree Wait for one more week, deny if no answer from besser82 (+7, 0, -0) 15:11:05 #topic #2180 F31 System-Wide Change proposal (late): No i686 Repositories 15:11:21 .fesco 2180 15:11:22 ignatenkobrain: Issue #2180: F31 System-Wide Change proposal (late): No i686 Repositories - fesco - Pagure.io - https://pagure.io/fesco/issue/2180 15:11:46 Hmm, was the on the schedule? 15:11:51 *this 15:11:57 * nirik happy to try and answer any questions... 15:12:07 zbyszek: nirik asked me to bring it 15:12:08 I can also abstain unless there's a tie or something. 15:12:44 contyk, sgallagh, ignatenkobrain: any of you would eb abel to answer my 2 questions there? 15:12:46 Next time, please reply to the schedule. I'm not against, but I need to re-read the ticket. 15:12:55 looking 15:13:13 note modules do support multilib 15:13:24 for reference: 1) How does one locally debug a i686 modular build failure? 15:13:28 they do? Thats unfortunate. 15:13:29 contyk: noted 15:13:40 2) How does this collide with Modules in buildroot enablement? 15:14:20 if there are no repos, local builds and debugging will be complicated 15:14:36 there is the koji buildroot repo. 15:14:45 re:2) we could still compose the buildroot modules for the urse prime case 15:15:21 local module builds support two modes -- "online" and "offline" 15:15:38 the online mode pulls RPMs directly from koji tags and "composes" them locally, that would still work 15:15:49 the offline mode relies solely on repodata and repo content 15:15:53 that would not 15:16:18 note the offline mode is the default now, afaik; however, there would still be a way 15:16:46 contyk: so to confirm, if I had a i686 modular build failure, I would be able to debug it locally by using the online mode even if the modular repos ar enot composed 15:17:18 yes, the online mode + the koji repos for the non-modular content 15:17:45 can we get that documented? 15:17:58 it might need some tweaks to the tools, I'm not sure how exactly it's invoked 15:18:22 besides us not liking i686, what's the reason for the rush? 15:19:01 do we have somebody who would do the tweaks or is it one of those "this is possible but doesn't work now and nobody is going to work on it" situations? 15:19:08 composing and publishing i686 repos means: a) people can/will upgrade to it with old kernels and b) we waste time/bw composing and publishing them. 15:20:35 I suppose this will be both an MBS and fedpkg change; so it's all about getting their maintainers to identify what needs to be changed and then do it 15:20:51 chances are it could be all fixed within half an hour at Flock but you never know 15:20:56 no, there's no changes there... 15:21:05 we would still build i686, koji would still have it. 15:21:11 we would just not compose and mirror it out 15:21:13 for the local builds, nirik 15:21:44 ok... so that expects a local mirror ? 15:22:08 no, but it just needs to know where to look 15:22:25 and as for 2) the ursa prime document at https://docs.google.com/document/d/1NxBbTPVJ17Ax4k-NbtorzxYspJ_CsjQ9m3In2wqWqVU/edit?pli=1# now says: "Koji needs to be updated so that build tag repositories can be created from more than one source -- the tag contents and zero or more external repositories." will those "external repositories" work when we don't compose them? 15:22:27 ok, so could use koji buildroot.... 15:23:03 mhroncok: that's why I said we could still compose the buildroot modules for this case 15:23:12 it's supposed to be yet another compose anyway 15:23:30 as it might include modules not shipped in the normal repos and vice versa 15:23:56 "we could still compose the buildroot modules" for i686, while we don't compose classic "Modular Repository" or i686 15:24:07 yep 15:24:09 ack 15:24:26 so I'm OK with 2), but with 1) I'm still not sure 15:25:08 it might already work, I don't know :) 15:25:13 can somebody actually check how to build modules locally if the i686 Modular and Everything composes ar enot available? 15:25:34 I can play with it 15:26:25 nirik: there's no hurry dropping the composes, we could investigate first, correct? 15:26:51 sure... but we should decide before beta freeze. 15:27:57 end of aug... 15:27:59 That's 2019-08-29, still quite a bit of time. 15:28:25 Well, it would be better to decide before branch wouldn't it? 15:28:33 proposal: we try to get answer for the "modularity local build" question and we defer this decision until we know the answer or until 2 weeks before the beta freeze (whatever happens first) 15:28:47 ack 15:28:51 +1 15:29:18 +1 15:29:21 jforbes: yeah, possibly so... 15:29:36 just more work, but would be nice to do it once. 15:30:12 Though I would like that answer to be more in depth than "it doesn't work" if it doesn't, what would need to change to make it work? 15:30:16 "2 weeks" is exactly one day before the branch point. 15:31:13 sorry, had to disappear due to broken glass around me 15:32:09 ignatenkobrain: yikes. stay safe. 15:32:25 anyhow, +1 to waiting a bit more for more info. 15:32:31 contyk, ignatenkobrain, otaylor: vote on mhroncok's proposal to postpone? 15:32:47 s/ack/+1/ 15:32:54 +1 15:33:01 ignatenkobrain: I hope it's not the laptop screen ;) 15:33:04 mhroncok: +1 15:34:37 #agree Defer decision until we know answer for the "modularity local build" question or until 2 weeks before the beta freeze (whatever happens first) (+7, 0, -0) 15:34:49 #topic Next week's chair 15:35:10 sgallagh was volunteering last week ;) 15:35:13 I think sgallagh signed up for it? 15:35:14 yeah 15:36:14 I'll be out next week, but I can take the week after 15:36:19 From the 7/22 logs 15:36:29 zbyszek: no, just some glass after drinking wine in the office. Accidentally dropped it from the table :) 15:37:30 oh 15:39:23 ? 15:39:58 action and openfloor? 15:41:23 #action sgallagh to chair next week 15:41:34 #topic Open Floor 15:41:43 oh, so sgallagh will do it? 15:41:44 I'm blind 15:41:57 I thought that he can't do next meeting 15:41:59 sorry 15:42:11 it's this one 15:42:16 I don't have anything for the open flor 15:42:32 I have just a few quick things... 15:42:54 #info mass rebuild was started last week. Took about 3.5 days and is all done now. 15:43:12 #info single package rawhide gating is hooked up and ready for people who want to opt-in. 15:43:37 cool 15:43:47 #info after some builder tweaks, rawhide composes are taking now about 4.5 hours. Down from 8-12. 15:43:56 nirik: what are the failure stats? 15:44:05 \o/ 15:44:12 zbyszek: https://kojipkgs.fedoraproject.org/mass-rebuild/f31-failures.html 15:44:13 https://kojipkgs.fedoraproject.org/mass-rebuild/f31-failures.html 15:44:16 1469 failed 15:44:33 but half of failures I've seen in my packages were cpio failures on random arches 15:44:50 I resubmiited all the failed ones yesterday 15:45:01 nirik: does this page reflect that? 15:45:04 before that there was 1760 failures 15:45:12 nirik: cool! thanks 15:45:12 yes 15:45:23 where is this going to be merged to f31? 15:45:27 *when 15:45:35 later today. 15:46:11 One thing from me. The nonresponive policy is blcoked by https://bugzilla.redhat.com/show_bug.cgi?id=1731835 15:46:52 oh, can we add a link to the non responsive maintainer policy/process in tickets in the fesco tracker? 15:47:09 if you could 1) vote the severity up (not sure if it helps) and/or 2) give a friendly nudge to the bugzilla people if you know them personally? 15:47:09 ie, if someone just gets an email they don't know whats going on... a link might help there. 15:47:27 I'll add it to the template 15:48:30 mhroncok: thanks! 15:48:51 mhroncok: sure 15:49:20 something else? 15:50:45 nirik: added 15:50:57 then I'll close in 10 seconds if nobody has anything :) 15:51:41 #endmeeting