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