18:01:05 #startmeeting FESCO (2022-01-25) 18:01:05 Meeting started Tue Jan 25 18:01:05 2022 UTC. 18:01:05 This meeting is logged and archived in a public location. 18:01:05 The chair is sgallagh. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:01:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:05 The meeting name has been set to 'fesco_(2022-01-25)' 18:01:05 #meetingname fesco 18:01:05 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, mboddu, tstellar, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 18:01:05 #topic init process 18:01:05 The meeting name has been set to 'fesco' 18:01:05 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mboddu mhroncok nirik sgallagh tstellar zbyszek 18:01:10 .hello2 18:01:11 sgallagh: sgallagh 'Stephen Gallagher' 18:01:13 .hello2 18:01:14 .hello ngompa 18:01:14 dcantrell: dcantrell 'David Cantrell' 18:01:17 Eighth_Doctor: ngompa 'Neal Gompa' 18:01:22 .hello2 18:01:23 bcotton: bcotton 'Ben Cotton' 18:01:42 .hello churchyard 18:01:43 .hello2 18:01:43 mhroncok: churchyard 'Miro Hrončok' 18:01:45 .hello tstellar 18:01:46 decathorpe: decathorpe 'Fabio Valentini' 18:01:49 tstellar: tstellar 'Tom Stellard' 18:02:12 .hello2 18:02:13 morning 18:02:13 zbyszek_: Sorry, but user 'zbyszek_' does not exist 18:02:21 .hello2 18:02:22 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 18:02:26 you exist! 18:02:39 Only 50% of the time 18:02:42 I may have to step away at some point here as I have some folks coming by the house to do some work and I have to talk to them about it first... 18:02:47 Don't worry, I believe in you 18:03:21 I believe in myself, therefore I exist. At other times, I don't, so I don't. 18:04:04 I think we have enough people to get started 18:04:12 #topic F36 Change: Enable fs-verity in RPM 18:04:12 .fesco 2711 18:04:13 sgallagh: Issue #2711: F36 Change: Enable fs-verity in RPM - fesco - Pagure.io - https://pagure.io/fesco/issue/2711 18:04:22 Has anything changed here since last week? 18:05:28 hi everyone 18:05:31 not too much 18:05:42 (from my side) 18:06:16 I actually enhanced rpmsign to produce PGP signatures 18:06:21 Hi Roberto 18:06:53 hi Zbyszek 18:06:59 https://github.com/robertosassu/rpm/commits/fsverity-gpg-v1 18:07:18 there are also some bug fixes (for memory leaks) 18:07:44 with this patch set you could use the same GPG key for both the RPM header and fsverity signatures 18:07:48 Have any of these changes been accepted by upstream projects yet? 18:07:52 doesn't this require the mass rebuild to be useful? 18:08:06 yes, it would require a mass rebuild 18:08:17 too late for F36 I guess 18:08:30 however, I cannot experiment with Copr 18:08:42 F36 was never realistic. 18:08:45 Copr uses OBS signer 18:08:54 That patch is surprisingly small. 18:09:08 I would probably need some access to the Fedora infrastructure, to use Sigul 18:09:12 yes, it is! 18:09:19 it is very simple 18:09:51 well, can you setup your own? I suppose we could look at testing in staging, but our stg signing is not very functional right now. 18:10:16 if possible yes, I don't know if I need additional permissions 18:10:42 our sigul package is broken 18:10:45 nobody can currently set it up 18:10:45 I was thinking that the impact of enabling this for executable content, kernel modules and firmware is not too much 18:10:59 no, it's working on epel8 18:11:05 it's broken in fedora 18:11:22 I basically need to replace the original rpmsign with my version 18:12:08 and provide some simple options 18:12:19 nirik: it's not in epel8 at all, iirc 18:12:53 yeah, you are right, it's in our epel8-infra tag. 18:12:57 .el8.infra 18:13:27 * mboddu is here 18:13:46 anyhow....I can try and help test this in stg, time permitting. But... I really wish we had some kind of plan or roadmap here aside from "lets enable all this stuff and perhaps our users will like to use it". 18:15:07 I would still like to use DIGLIM for integrity protection, but seeing also the alternative solution with file/fsverity signatures would be great 18:16:00 for the plan, probably the authors of this change can provide more details 18:16:06 I can help with implementation, testing 18:16:35 * nirik thinks of http://www.islinuxaboutchoice.com/ 18:17:02 nirik: Let me know if you need any help with testing in stg 18:17:18 I can post to the thread and yea, perhaps change owners cna expand on what they want to use it for? 18:17:27 I think we can do that 18:17:41 That'd be helpful. 18:17:48 https://src.fedoraproject.org/fork/robertosassu/rpms/rpm 18:18:10 this is the project with rpm modifications 18:18:37 f35 branch 18:20:09 (still need to test better) 18:21:46 should we formally reject this for f36? 18:21:47 I think so, yes 18:22:02 I'd prefer to punt it to F37 with the proviso it gets upstreamed first 18:22:03 It's too late for the mass rebuild in any case 18:22:13 we seem to spend a lot of time on this change during meetings 18:22:20 Yeah, I don't think we need to "reject" it. Just reassign. 18:22:28 mainly to make upstream folks consider prioritizing review 18:22:35 ok for me 18:22:45 I mean, saying "this will not happen in f36" without saying what will happen in f37 18:22:46 same for the fsverity one 18:23:14 mhroncok: I think we can just do it 18:23:40 yeah, moving to 37 seems better than rejecting, if we are still wanting to discuss more and get things upstreamed 18:23:56 +1 to move to f37 18:23:56 I agree 18:24:05 yes, also the kernel is not ready to enforce yet 18:24:26 Does "move to f37" mean we approve this change for f37 or does it mean we will reconsider it for f37? 18:24:27 +1 to move this to f37, if that does not mean actually approving it for f37 18:24:39 Reconsider in F37 18:24:40 reconsider +1, approve -1 18:24:44 Reconsider for f37 18:25:28 Reconsider for f37 18:25:40 right. just move it to pending for 37... still under discussion 18:25:41 reconsider for F37 18:26:01 Reconsider for f37 bandwagon 18:26:10 +1 To reconsider this for f37. 18:26:22 +1 18:27:16 #agreed FESCo will reconsider this Change for F37 at a later date. (+9, 0, -0) 18:27:24 #topic F36 Change: DIGLIM 18:27:24 .fesco 2721 18:27:25 sgallagh: Issue #2721: F36 Change: DIGLIM - fesco - Pagure.io - https://pagure.io/fesco/issue/2721 18:27:28 Same here? 18:27:31 +1 18:27:46 Same here 18:27:59 Same 18:28:09 same 18:28:13 Same here. 18:28:21 yeah. +1 18:28:26 same 18:28:44 #agreed FESCo will reconsider this Change for F37 at a later date. (+8, 0, -0) 18:28:59 On to new business: 18:29:00 #topic F36 Change: No ifcfg by default 18:29:00 .fesco 2732 18:29:01 sgallagh: Issue #2732: F36 Change: No ifcfg by default - fesco - Pagure.io - https://pagure.io/fesco/issue/2732 18:29:26 Do we have any of the NM folks here? 18:29:58 Uh, I am inclined to say "same here" for this change as well. I don't think the cloud-init stuff can be ported in time for F36 18:30:40 decathorpe: good point 18:30:42 Yeah, my -1 on the ticket was not a blanket rejection, it's "Bring this back to us when it doesn't break cloud-init" 18:31:05 Wouldn't it be worthwhile to deprecate the functionality already in F36? Gives people more time to react. 18:31:34 deprecate, yes, remove, no. though the change proposal is kinda confusing wrt. that point after I read it again. 18:32:00 "Do not include NetworkManager support for legacy network configuration files by in new installations. " 18:32:06 cloud init could require that, no? 18:32:08 it's been deprecated for a few releases now 18:32:33 "Split the ifcfg plugin into a subpackage package. " 18:32:37 mhroncok: the problem is that if they remove it, the code is almost certainly getting deleted and not being maintained 18:32:40 we can include that package in cloud only for now 18:32:58 mhroncok: indeed, Requires: would be enough on cloud-init 18:33:08 "For the time being the ifcfg plugin is kept around, albeit in a sub-package that's not included in new installations." 18:33:25 Sure, it's reasonable not to install it by default. 18:33:30 this sound like a non-issue to me, but maybe I cherry-pick only some parts of the change 18:34:18 +1 providing that cloud-init requires this new package 18:34:22 that sounds like a nice solution. 18:34:28 +1 to mhroncok 18:34:30 unless we are missing something. 18:34:35 it's only nice as long as it doesn't go away 18:34:45 I'm happy to switch to a +1 if we're not breaking cloud-init 18:34:50 yeah, until it can. 18:34:54 Conan Kudo: Ever? 18:34:56 (I assume cloud-init is installed on the same system and not on some "host") 18:34:57 +1 mhroncok 18:35:03 Stephen Gallagher: until they port it 18:35:20 cloud-init maintainers can maintain this forever or port cloud-init 18:35:46 yeah, assuming we don't break cloud-init in F36, I'm fine with removing it from the default install everywhere that's not affected by that. 18:35:49 mhroncok: cloud-init maintainers are not maintainers in NM codebase 18:36:03 so they port it instead 18:36:18 I'm fine with that, there's a BZ asking for it 18:36:23 I am sure they can communicate iwth each other ert time frame 18:36:24 I think for something like this, we need to make a firm decission that we are goiong to do it in a future release, otherwise there is nothing motivating legacy users to update the code. 18:36:27 I want it to be a precondition for them deleting the package 18:36:33 s/ert/wrt/ 18:36:50 mhroncok: I am very doubtful that they can communicate with each other 18:37:02 well, than something is broken, isn't it? 18:37:08 *then 18:37:30 the bugzilla exists. if cloud-init maintainers don't respond... it si probably not that importan tot keep cloud-init 18:37:46 * Eighth_Doctor sighs 18:37:51 we cannot expect NM maintaers to port cloud-init themselves 18:38:11 this change is about spliting it to a subpackage that can be installed and can be required 18:38:17 +1 to that 18:38:20 Proposal: request that the Change is updated to include a specific Fedora release (F37?) that will drop the ifcfg support entirely. 18:38:32 if they plan to remove it entirely later, good for them, but that's another change 18:38:50 Yeah, I don't think we should be putting words in the Change owners' mouths 18:38:51 Stephen Gallagher: -1 18:39:28 they're the NM developers, we can definitely ask them to commit to that 18:39:29 we can recommend the change owners to approach cloud-init maintainers and communicate the time frame with them 18:39:32 yeah, I'd hope someone could port it... and that NM folks will keep the old one around until that happens 18:39:41 let's not kid ourselves here 18:40:13 once network-scripts and ifcfg-rh are both dropped, there is no backend for us to configure with 18:40:20 Eighth_Doctor: I expect that a person knowlegable in both projects could do it a day or two, including tests. 18:40:27 (I am not comfortable telling them to ditch it in f37 if that was not their plan) 18:41:16 (I'd support them if that's what they want) 18:41:17 Sorry, the F37 piece was a suggestion, not a demand. 18:41:33 The important part of that proposal was the definitive timeframe 18:41:36 What exactly does "Not included in new installs mean" ? Can an f36 install the package if they want to ? 18:41:52 *f36 user 18:41:53 tstellar: comps 18:41:55 I interpret that as "no we can't" 18:41:59 yes, they can 18:42:05 as in, we're not supposed to as Fedora composes 18:42:12 yes, they can. It's split out to a subpackage so that you can install it on demand. 18:42:13 yes, just none of our composed images will use it except the cloud image 18:42:31 Proposal: ... 18:42:50 Except the cloud images, it wont be shipped in another images, but the users can install it if they want to 18:43:01 nirik: the change states we shouldn't 18:43:18 change is approved. cloud-init will gain requires for the new subpackage, change owners to communicate in https://bugzilla.redhat.com/show_bug.cgi?id=2014701 wrt complete removal time frame 18:43:46 .bug 2014701 18:43:48 zbyszek: 2014701 – cloud-init cannot configure networking using NM keyfiles - https://bugzilla.redhat.com/2014701 18:43:55 mhroncok: +1 18:44:32 mhroncok: +0 (leaning -1) 18:45:02 perhaps we should add ... and will not break cloud-init until it's ported? 18:45:14 mhroncok: +1 18:45:16 nirik: adding that would make me +1 18:45:30 nirik: that gives cloud-init a get out of jail free card 18:45:38 nirik: I'm opposed to that. 18:46:08 We would be essentially telling the NM folks that they have to retain ancient and crufty code indefinitely to avoid inconveniencing one package. 18:46:08 mhroncok: the people removing the implementation should be responsible for making it not needed anymore, that's generally how these things have gone 18:46:11 nirik: yeah, I don't think we ask for "communication", so let's not try to predict the outcome. 18:46:34 Stephen Gallagher: it's the package that makes cloud images work for Fedora, RHEL, and everyone else 18:46:38 nirik: sorry, we *ask* for communication, so let's not try to predict the outcome 18:46:42 sgallagh: But this proposal as written does not allow them to drop old code. 18:46:45 well, we would be telling them to get it ported... convince them to do it, hire someone, find a person, etc? 18:46:57 Conan Kudo: I disagree. we would have never "removed" python2 if that was true 18:47:35 I'm very much with mhroncok here. This feet-dragging on part of cloud-init is their problem, not NMs. 18:47:37 I don'T expect the change owners to silently drop the subpackage in F36 after they split it 18:47:39 well, I do want them to communicate... I just don't want us to be in a position where cloud images break and the two sides point at each other... if we say 'don't break this, but we don't care how you fix it' isn't that enough? 18:47:46 mhroncok: you _did_ help with porting hundreds of Python packages 18:47:47 if that was their intention, they would say so 18:48:03 as did I and several others in the SIG 18:48:19 I think they either need to update the proposal with a long-term removal plan for us to vote on or plan to submit another proposal when they want to completely remove the old functionality. 18:48:35 I helped, but I would not be very happy if fesco demanded I port everything 18:48:44 tstellar: I agree with that 18:49:10 I am completely Ok if we say "removal will be coordinated by another change" 18:49:24 Yeah. 18:49:31 it feels unnecessary to me, but I am OK with that 18:49:51 let me put a full proposal... 18:49:55 A removal is honestly the only part of this that would justify a Change 18:50:05 Otherwise, it's just basic package maintenance 18:50:20 sgallagh: a Change is very good for visibility and announcing intent. 18:50:22 change is approved. cloud-init will gain requires for the new subpackage, change owners to communicate in https://bugzilla.redhat.com/show_bug.cgi?id=2014701 wrt complete removal time frame. complete removal of the subpackage/code will be coordinated by another change in the future 18:50:32 mhroncok: +1 18:50:34 +1 18:50:34 mhroncok: +1 18:50:44 sgallagh: Yeah, it took me a few times of reading the proposal to understand that it's just package maintenance. 18:51:05 mhroncok: +1 18:51:11 it also changes the defaults, so not just package maintanence 18:51:27 mhroncok: Ok, I can get on board with that. +1 18:51:39 +1 myself FTR 18:51:48 mhroncok: +1 18:52:24 +1 18:52:43 I count +8... mboddu ? 18:53:21 mhroncok: Which default, you mean the comps? 18:53:42 tstellar: yes, basically "won't be installed by default" 18:54:03 (which is spelled out in the name and summary) 18:55:04 #agreed change is approved. cloud-init will gain requires for the new subpackage, change owners to communicate in https://bugzilla.redhat.com/show_bug.cgi?id=2014701 wrt complete removal time frame. complete removal of the subpackage/code will be coordinated by another change in the future (+8, 0, -0) 18:55:05 mhroncok: Yeah Ok. 18:55:17 #topic Next week's chair 18:55:25 * sgallagh lobs the grenade 18:55:34 Who's going to jump on it? 18:56:13 * zbyszek has the school spring break and is not sure if he'll be there. 18:57:18 I'll be in the middle of exam season, but I can run more meetings again after that's done :/ 18:57:33 * mhroncok can do it 18:57:50 I can do it, but I would need someone to walk me through the process. 18:58:15 tstellar: https://fedoraproject.org/wiki/FESCo_meeting_process is pretty helpful 18:58:39 * mhroncok can walk tstellar through the process 18:59:25 #action tstellar to chair next week with mhroncok 's guidance 18:59:32 #topic Open Floor 18:59:37 Thanks, mhroncok , tstellar 19:00:05 Q for nirik: 19:00:18 what about the mass rebuild and the ppc64le issues? 19:00:29 Is another mini-rebuild planned after gcc is updated? 19:00:41 yes, I sent an email with status before the fesco meeting. :) 19:00:44 yes, see devel-announce 19:00:46 we plan another pass on failed ones. 19:00:56 hopefully that will fix the ppc64le ones. 19:01:01 when can we expect the bugzillas? 19:01:34 sgallagh: Sorry, need to step out for a bit, but yeah, +1 19:01:59 mhroncok: I think the bugzillas are already being filed, I got at least one. 19:02:15 it stopped 19:02:17 nirik: thanks. I somehow missed the second page of your announcement. 19:02:19 I think jednorozec was working on fixing the filing script today, so tomorrow? 19:02:19 I hope signing will be done by then. ;( 19:02:47 yeah, it hit the bz 20 limit thing... needs fixing for that 19:03:24 * mhroncok is happy to help fixing that thing, done it several times already 19:03:31 (but not today) 19:03:46 nirik: Is there a page that lists all the current failing packages? 19:04:06 tstellar: https://kojipkgs.fedoraproject.org/mass-rebuild/f36-failures.html 19:04:49 yep. ^ 19:06:41 Anything else for today? 19:06:44 nope 19:09:29 ? 19:09:42 None from me 19:11:32 * nirik has nothing 19:11:35 #endmeeting