2024-03-11 13:01:28 <@ankursinha:fedora.im> !startmeeting NeuroFedora - 2024-03-11
2024-03-11 13:01:29 <@meetbot:fedora.im> Meeting started at 2024-03-11 13:01:28 UTC
2024-03-11 13:01:29 <@meetbot:fedora.im> The Meeting name is 'NeuroFedora - 2024-03-11'
2024-03-11 13:01:33 <@ankursinha:fedora.im> !meetingname neurofedora
2024-03-11 13:01:59 <@ankursinha:fedora.im> !link agenda is here: https://neuroblog.fedoraproject.org/2024/03/09/next-open-neurofedora-meeting-11-march-1300-utc.html
2024-03-11 13:02:08 <@ankursinha:fedora.im> !topic Introductions and roll call
2024-03-11 13:02:17 <@ankursinha:fedora.im> If you're here for the meeting, please say hello!
2024-03-11 13:02:19 <@ankursinha:fedora.im> !hi
2024-03-11 13:02:20 <@zodbot:fedora.im> Ankur Sinha (ankursinha) - he / him / his
2024-03-11 13:05:12 <@gui1ty:fedora.im> !hi
2024-03-11 13:05:13 <@zodbot:fedora.im> Sandro . (gui1ty)
2024-03-11 13:06:36 <@ankursinha:fedora.im> let's wait a couple of minutes and start 
2024-03-11 13:11:32 <@ankursinha:fedora.im> !topic Tasks from last meeting
2024-03-11 13:11:44 <@ankursinha:fedora.im> !link last meeting logs are here: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-26/neurofedora.2024-02-26-13.02.html
2024-03-11 13:12:32 <@ankursinha:fedora.im> Ankur: file ticket with fesco about nodejs etc. (related to https://pagure.io/neuro-sig/NeuroFedora/issue/563) -> DONE
2024-03-11 13:12:33 <@ankursinha:fedora.im> https://pagure.io/fesco/issue/3177
2024-03-11 13:13:06 <@ankursinha:fedora.im> !info Ankur: file ticket with fesco about nodejs etc. (related to https://pagure.io/neuro-sig/NeuroFedora/issue/563) -> DONE -> https://pagure.io/fesco/issue/3177
2024-03-11 13:13:11 <@ankursinha:fedora.im> let's see how that goes
2024-03-11 13:13:23 <@ankursinha:fedora.im> Ankur file issue against dashboard about FTBFS issues---python-lsp-server as example
2024-03-11 13:14:00 <@ankursinha:fedora.im> So, I was looking at this Penguinpee and saw that you've already been in conversation with folks here: 
2024-03-11 13:14:09 <@ankursinha:fedora.im> https://pagure.io/fedora-qa/packager_dashboard/issue/71#comment-891515
2024-03-11 13:14:14 <@ankursinha:fedora.im> so, do we need a fresh ticket?
2024-03-11 13:15:01 <@gui1ty:fedora.im> Probably not. I need to refresh my memory on that. 
2024-03-11 13:16:02 <@ankursinha:fedora.im> it looks like if the version that ended up in the fedora repo had issues, it'll always be flagged
2024-03-11 13:16:18 <@gui1ty:fedora.im> Honestly, I thought that discussion had been taking place elsewhere. So much information, so many channels ...
2024-03-11 13:16:24 <@ankursinha:fedora.im> at least that's my understanding of "Note that it's possible that this issue has been fixed in the meantime, but the packages were just broken at GA and the broken versions remain in the "fedora" repo while fixed versions are in the "updates" repo."
2024-03-11 13:16:45 <@ankursinha:fedora.im> yeh, i went through quite a few issues before i ran into that bit
2024-03-11 13:17:15 <@gui1ty:fedora.im> Yeah, but that doesn't feel right. Staring at non-issues  for an entire release cycle ...
2024-03-11 13:17:36 <@ankursinha:fedora.im> I know. If it's been fixed, it should be indicated somewhere
2024-03-11 13:18:27 <@ankursinha:fedora.im> but I guess the automation looks at each build in each repo, and it doesn't currently include intelligence to only look at latest builds
2024-03-11 13:19:13 <@ankursinha:fedora.im> this is the "fedora-health-check" bit. I wonder what else it reports, and if we can just disable it in the dashboard and rely on koschei instead?
2024-03-11 13:19:27 <@gui1ty:fedora.im> Ideally, it should combine GA and testing.
2024-03-11 13:19:30 <@ankursinha:fedora.im> there's a setting to toggle it on/off, and turning it off removes the issue
2024-03-11 13:20:40 <@ankursinha:fedora.im> what else does fedora-health-check tell us? 
2024-03-11 13:20:51 <@ankursinha:fedora.im> I can't seem to find a lot of info on it on the wiki or in the dashboard repo..
2024-03-11 13:21:31 <@ankursinha:fedora.im> Ah, well, there's also this: https://pagure.io/ironthree/repochecker/issue/3
2024-03-11 13:22:32 <@gui1ty:fedora.im> `spyder` being on the dashboard makes me all nervous, since there were issues with it. But I'm always going to double check, keeping my fingers crossed. In the end it's a fluke.
2024-03-11 13:23:22 <@ankursinha:fedora.im> I could ping this issue to see if there's anything that can be done about  it?
2024-03-11 13:23:40 <@ankursinha:fedora.im> it's 3 years old and repochecker has moved to github since then, so it's possible it's just fallen off the radar?
2024-03-11 13:24:34 <@gui1ty:fedora.im> That's a Fabio issue. I'd be surprised if that feel off _his_ radar.
2024-03-11 13:24:47 <@gui1ty:fedora.im> That's a Fabio issue. I'd be surprised if that fell off _his_ radar.
2024-03-11 13:24:52 <@decathorpe:fedora.im> what did?
2024-03-11 13:25:13 <@ankursinha:fedora.im> hello: this issue: https://pagure.io/ironthree/repochecker/issue/3
2024-03-11 13:25:21 <@zodbot:fedora.im> ankursinha has already given cookies to decathorpe during the F39 timeframe
2024-03-11 13:25:43 <@decathorpe:fedora.im> it's still on my radar, but I'm unsure how to fix it. it would likely need a bit of rearchitecting of the code base 
2024-03-11 13:25:56 <@decathorpe:fedora.im> no, just completely accidentally saw your message :)
2024-03-11 13:26:28 <@ankursinha:fedora.im> looks like everyone moving their meetings to the 3 channels does work to improve communication :)
2024-03-11 13:26:39 <@ankursinha:fedora.im> that makes sense, it's what I suspected :)
2024-03-11 13:26:47 <@gui1ty:fedora.im> No problem. Glad to have confirmation that issue is still on someone's radar.
2024-03-11 13:26:53 <@ankursinha:fedora.im> we'll just keep this in mind and check what build the issues is related to
2024-03-11 13:27:45 <@gui1ty:fedora.im> Do we have some documentation on Packager Dashboard? Maybe me getting lost is a result of not fully understanding.
2024-03-11 13:28:27 <@ankursinha:fedora.im> !info For issues on the dashboard, check what build the issue is referring to since health-check will also report issues on package builds that are in the fedora repo but may have been fixed in updates: https://pagure.io/ironthree/repochecker/issue/3
2024-03-11 13:28:42 <@gui1ty:fedora.im> ❓️
2024-03-11 13:28:58 <@gui1ty:fedora.im> Thhere's help hiding behind the ❓️
2024-03-11 13:29:19 <@ankursinha:fedora.im> Yeh, that's all I see: https://packager-dashboard.fedoraproject.org/helpmepls
2024-03-11 13:29:43 <@ankursinha:fedora.im> I mean we could open a PR noting what fedora-health-check reports I guess?
2024-03-11 13:30:08 <@gui1ty:fedora.im> It's very concise indeed.
2024-03-11 13:30:35 <@ankursinha:fedora.im> yeh, the idea of the dashboard is probably to be concise :)
2024-03-11 13:30:48 <@ankursinha:fedora.im> let's just remember this, and as long as one of us remembers, we'll be fine ;)
2024-03-11 13:30:53 <@gui1ty:fedora.im> Nihilism!
2024-03-11 13:31:19 <@gui1ty:fedora.im> Indeed. Let's move on.
2024-03-11 13:31:43 <@ankursinha:fedora.im> Ankur patch out imp import in netpyne to fix FTBFS -> WIP
2024-03-11 13:31:54 <@ankursinha:fedora.im> I have the fix, but I need to test it, send it upstream, fix our package
2024-03-11 13:31:56 <@ankursinha:fedora.im> reassigning
2024-03-11 13:31:59 <@ankursinha:fedora.im> !action Ankur patch out imp import in netpyne to fix FTBFS
2024-03-11 13:32:21 <@ankursinha:fedora.im> Ankur ping raptor co-maintainer to see if they'd take it over -> PENDING
2024-03-11 13:32:27 <@ankursinha:fedora.im> sorry, that fell off my radar
2024-03-11 13:32:31 <@ankursinha:fedora.im> !action Ankur ping raptor co-maintainer to see if they'd take it over
2024-03-11 13:32:41 <@ankursinha:fedora.im> Ankur review sandia-omega-h -> WIP
2024-03-11 13:32:57 <@ankursinha:fedora.im> we've got one round of review done, I've got to do the next one now that you've made some tweaks
2024-03-11 13:33:12 <@ankursinha:fedora.im> !info Ankur review sandia-omega-h -> WIP (first round of reviews is done, next round coming soon)
2024-03-11 13:33:28 <@ankursinha:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2252229
2024-03-11 13:33:40 <@ankursinha:fedora.im> everyone please look at https://pagure.io/neuro-sig/NeuroFedora/issue/566 and see if you can help out with the compilation issue
2024-03-11 13:34:05 <@gui1ty:fedora.im> Sure. Let's keep it going. I noticed it took me some time to get into that package again after it had been resting for so long.
2024-03-11 13:34:30 <@ankursinha:fedora.im> this is a WIP, upstream has updated the code to work with the new sundials versions. As soon as we have sandia-omega-h in the repos, I can continue tinkering with this
2024-03-11 13:34:50 <@ankursinha:fedora.im> !info updating STEPS to latest release: WIP here: https://src.fedoraproject.org/rpms/python-steps/pull-request/6
2024-03-11 13:34:53 <@gui1ty:fedora.im> There's a preliminary version available in Copr.
2024-03-11 13:35:07 <@ankursinha:fedora.im> yeh, I'll use that in the meantime and see how far I get
2024-03-11 13:35:29 <@ankursinha:fedora.im> !topic Open Pagure tickets
2024-03-11 13:35:37 <@ankursinha:fedora.im> !link https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting
2024-03-11 13:35:59 <@ankursinha:fedora.im> !info A few tickets, but they're all in WIP, so not much to discuss about them at the  moment
2024-03-11 13:36:44 <@gui1ty:fedora.im> Ticket #567 deserves to be looked at in cadence with our meetings.
2024-03-11 13:37:08 <@gui1ty:fedora.im> I don't see an automated fix coming soon.
2024-03-11 13:37:15 <@ankursinha:fedora.im> oo, new packages there
2024-03-11 13:37:29 <@ankursinha:fedora.im> pagure doesn't send notifications for issue description edits from the looks of it
2024-03-11 13:37:41 <@ankursinha:fedora.im> !action Ankur update monitoring on all packages mentioned in https://pagure.io/neuro-sig/NeuroFedora/issue/567
2024-03-11 13:37:48 <@gui1ty:fedora.im> Since I keep editing, no notifications go out, I believe.
2024-03-11 13:38:19 <@ankursinha:fedora.im> Yeh, I'll go update all them packages after the meeting
2024-03-11 13:38:38 <@gui1ty:fedora.im> Sure. Nothing urgent. Just a chore.
2024-03-11 13:38:50 <@ankursinha:fedora.im> Also: https://pagure.io/neuro-sig/NeuroFedora/issue/563 -> https://pagure.io/fesco/issue/3177
2024-03-11 13:39:14 <@ankursinha:fedora.im> this issue relates to sphinx generated docs too, right? I remember there was a bug about it that music would reference in specs
2024-03-11 13:40:14 <@ankursinha:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2006555
2024-03-11 13:43:56 <@ankursinha:fedora.im> oo, we only have ~15 minutes!
2024-03-11 13:44:01 <@ankursinha:fedora.im> !topic Package health check
2024-03-11 13:44:22 <@ankursinha:fedora.im> !link https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
2024-03-11 13:45:19 <@ankursinha:fedora.im> hrm, python-limits has been orphaned but still shows up---perhaps it'll go away when the data is re-generated
2024-03-11 13:46:50 <@gui1ty:fedora.im> It's been orphaned two days ago. It should disappear once retired, I believe.
2024-03-11 13:47:36 <@gui1ty:fedora.im> Or maybe some toddler needs to come along waving a magic wand 🪄
2024-03-11 13:47:49 <@ankursinha:fedora.im> packages look healthy enough---a few new releases to be updated to, a few FTBFS/FTI bugs (including python 3.13 related ones)
2024-03-11 13:47:59 <@ankursinha:fedora.im> anything urgent there that we need to work on Penguinpee ?
2024-03-11 13:48:04 <@ankursinha:fedora.im> (or prioritise)?
2024-03-11 13:48:34 <@gui1ty:fedora.im> Not to my knowledge. I know `appstream` broke a few packages. 
2024-03-11 13:48:49 <@ankursinha:fedora.im> testing for py3.13 still isn't straightforward. I'm not even sure providers like GitHub Actions include it as an environment
2024-03-11 13:49:02 <@ankursinha:fedora.im> oh? how come? stricter checks?
2024-03-11 13:49:15 <@gui1ty:fedora.im> You can use Python SIG's Copr. That's what I do.
2024-03-11 13:49:38 <@ankursinha:fedora.im> yeh, but that's not the easiest for upstreams to work with etc
2024-03-11 13:49:40 <@gui1ty:fedora.im> Warnings turned into errors basically.
2024-03-11 13:49:50 <@ankursinha:fedora.im> ah, right, good to know
2024-03-11 13:49:59 <@ankursinha:fedora.im> !info appstream turned warnings to errors which may break some builds
2024-03-11 13:50:10 <@gui1ty:fedora.im> https://bugzilla.redhat.com/show_bug.cgi?id=2267575
2024-03-11 13:50:54 <@ankursinha:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2267575
2024-03-11 13:51:39 <@ankursinha:fedora.im> !info packages look healthy enough---a few new releases to be updated to, a few FTBFS/FTI bugs (including python 3.13 related ones)
2024-03-11 13:52:02 <@ankursinha:fedora.im> !topic Open package reviews
2024-03-11 13:52:04 <@ankursinha:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro
2024-03-11 13:52:26 <@ankursinha:fedora.im> !info 4 reviews in progress
2024-03-11 13:52:38 <@ankursinha:fedora.im> !info 3 reviews (simple ones for snakemake plugins) requiring review
2024-03-11 13:52:58 <@gui1ty:fedora.im> I posted a couple of reviews, which are needed should Spyder 6 ever be released. Should block those on NeuroFedora?
2024-03-11 13:53:16 <@ankursinha:fedora.im> yeh, sure, at least that way everyone is notified that they're in the pipeline
2024-03-11 13:53:37 <@gui1ty:fedora.im> I'll do that after the meeting.
2024-03-11 13:54:02 <@gui1ty:fedora.im> I'm working on 6.0.0a4 still hoping it will come out before F40.
2024-03-11 13:54:31 <@gui1ty:fedora.im> `pyuca` should be solved. Just waiting on upstream and the reviewer.
2024-03-11 13:54:49 <@gui1ty:fedora.im> 👍️
2024-03-11 13:54:50 <@ankursinha:fedora.im> !topic CompNeuro ISO image build check
2024-03-11 13:54:52 <@ankursinha:fedora.im> !link https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
2024-03-11 13:55:11 <@ankursinha:fedora.im> !info All green ticks, all good ✅
2024-03-11 13:55:23 <@ankursinha:fedora.im> !topic Neuroscience query of the week
2024-03-11 13:56:05 <@gui1ty:fedora.im> Not NeuroScience. But UCL caused some stir dismissing black matter.
2024-03-11 13:56:30 <@ankursinha:fedora.im> Oo? I haven't heard of this somehow---what's up?
2024-03-11 13:56:52 <@ankursinha:fedora.im> Oh hold on, dark matter you mean?
2024-03-11 13:56:54 <@ankursinha:fedora.im> :D
2024-03-11 13:57:07 <@gui1ty:fedora.im> https://www.theguardian.com/science/2024/mar/09/controversial-new-theory-of-gravity-rules-out-need-for-dark-matter
2024-03-11 13:57:40 <@gui1ty:fedora.im> Not your field, but colleagues of you, right?
2024-03-11 13:58:46 <@ankursinha:fedora.im> sort of, folks I know did astrophysics but didn't focus on this sort of theoretical work
2024-03-11 13:59:26 <@ankursinha:fedora.im> all of this is great for sci-fi :D
2024-03-11 14:00:34 <@ankursinha:fedora.im> https://ramblingreaders.org/book/125342/s/leviathan-falls 
2024-03-11 14:00:58 <@ankursinha:fedora.im> it's the easter break around the next meeting, so I won't be around
2024-03-11 14:01:28 <@gui1ty:fedora.im> Look who gave it five stars ...
2024-03-11 14:01:32 <@ankursinha:fedora.im> Penguinpee: do you want to do a meeting for a quick status check, or should we skip it perhaps?
2024-03-11 14:02:01 <@ankursinha:fedora.im> it did win the Hugo awards, so it's not just me :P
2024-03-11 14:02:12 <@gui1ty:fedora.im> I can do it. But if it's just me, myself and I, I'll shortcut to `!endmeeting`.
2024-03-11 14:02:53 <@ankursinha:fedora.im> !info Ankur on PTO from 22nd March to 8th April
2024-03-11 14:03:10 <@ankursinha:fedora.im> !topic Next meeting
2024-03-11 14:03:22 <@gui1ty:fedora.im> I heard of The Expanse before. I should read it eventually.
2024-03-11 14:03:31 <@ankursinha:fedora.im> !info Penguinpee will chair next meeting, but shortcut to endmeeting if we don't have quorum
2024-03-11 14:03:50 <@ankursinha:fedora.im> cool, let's stop there and release the channel. We can keep going in #neuro:fedoraproject.org 
2024-03-11 14:03:52 <@ankursinha:fedora.im> !endmeeting