13:00:18 #startmeeting NeuroFedora - 2023-01-30 13:00:19 Meeting started Mon Jan 30 13:00:18 2023 UTC. 13:00:19 This meeting is logged and archived in a public location. 13:00:19 The chair is FranciscoD_. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 13:00:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:19 The meeting name has been set to 'neurofedora_-_2023-01-30' 13:00:27 #meetingname neurofedora 13:00:27 The meeting name has been set to 'neurofedora' 13:01:18 #chair music Penguinpee 13:01:18 Current chairs: FranciscoD_ Penguinpee music 13:01:26 #topic Agenda 13:01:46 #info Agenda is here in the announcement post: https://neuroblog.fedoraproject.org/2023/01/30/next-open-neurofedora-meeting-30-january-1300-utc.html 13:02:03 #topic Introductions and roll call 13:02:12 I'll wait here for ~5 minutes for folks to join in 13:02:25 @room ^ 13:02:26 .members neuro-sig 13:02:27 FranciscoD_: Something blew up, please try again 13:02:30 FranciscoD_: An error has occurred and has been logged. Please contact this bot's administrator for more information. 13:02:42 .members neuro-sig 13:02:43 FranciscoD_: Something blew up, please try again 13:02:46 FranciscoD_: An error has occurred and has been logged. Please contact this bot's administrator for more information. 13:02:48 :( 13:03:50 .hello gui1ty 13:03:50 Penguinpee: Something blew up, please try again 13:03:53 Penguinpee: An error has occurred and has been logged. Please contact this bot's administrator for more information. 13:04:35 zodbot doesn't seem well today :/ 13:04:49 hello Penguinpee o/ 13:06:05 It probably needs a kick, but admins are still asleep, I'm afraid. 13:08:24 yeh, doesn't matter, as long as it logs the meeting 13:08:29 lets proceed anyway 13:08:32 #topic Tasks from last meeting 13:08:53 #info Last meeting logs are here: https://meetbot.fedoraproject.org/fedora-neuro/2023-01-16/neurofedora.2023-01-16-13.00.html 13:09:12 There was only the one task about a package review, which is now complete 13:09:15 #info All tasks complete 13:09:43 #topic Open pagure tickets 13:10:20 #info Tickets marked as next-meeting: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting 13:10:23 #info No tickets to discuss 13:10:37 #topic Package health check 13:10:47 #info neuro-sig packages dashboard: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig 13:11:25 #info we prioritise FTBFS/FTI bugs, and then other bugs, then package updates etc. 13:11:58 Gosh, one of mine is in there and I haven't seen any notification or bug report, yet. 13:12:24 an FTBFS? Which one? 13:12:35 python-mizani 13:13:27 I don't see a bug for it---is koschei just marking it as FTBFS? It doesn't send notifications for that 13:13:28 Fall out from the mass rebuild? 13:14:11 Yeah, Koschei reports it as FTBFS. 13:14:25 yeh, notifications are only sent once a bug has been filed 13:14:54 for this package, it's for F37/F36 too, so not so important---because it was already built and unless there's an update, it's unlikely it'll be built again 13:15:35 I see. I think I looked at the list after the mass rebuild and it wasn't on there. Will need to investigate anyway. 13:15:55 it isn't marked for rawhide, so should be fine 13:16:11 I think tickets from the mass rebuild fall out have been filed now, so if we didn't get any notifications, it's all good 13:16:12 :D 13:16:32 there's also gcc13 in rawhide now, and that's caused a few issues 13:16:41 True. Anyway, I'll take a look when I find the time. 13:16:41 #info GCC 13 in rawhide may cause some packages to fail 13:16:59 +1 13:17:10 #info GCC 13 changes are here: https://gcc.gnu.org/gcc-13/porting_to.html 13:17:13 GCC in rawhide wouldn't cause the package to FTBFS in F36/37, though. 13:17:28 No, it wouldn't---that's usually indicates some dep changes 13:18:01 maybe a dep was updated etc., and that either breaks the dep chain or makes some tests fail 13:18:02 that sort of thing 13:18:35 but, the package version that was built (and is the one reaching users) should continue to work---if it doesn't install any more, the automated FTI checker will file a bug 13:18:42 Yeah. Will need to take a closer look. But flexiblas may be a candidate... 13:21:04 Not a lot of FTBFS bugs there then, we seem to have quite a few updates 13:22:27 #info Please open PRs to update all packages---quite a few "new version is available" bugs around 13:22:27 Didn't find the time to look at updates, but I reviewd one of yours. ;) 13:23:14 .members neuro-sig 13:23:15 Penguinpee: Members of neuro-sig: sagitter, ignatenkobrain, bt0dotninja, zbyszek, sergiopr, blackfile, ankursinha, lbazan, ilgrad, gicmo, alciregi, bizdelnick, nerdsville, mhough, victortyau, music, major, fangq, anilbey, iztokf, aekoroglu, gui1ty, shaneallcroft, hardeborlaa, mairacanal, vanessakris 13:23:32 yeh, me neither---working on gdcm now, only fails to build on i686 🤨 13:23:32 thanks for the review :) 13:23:43 oo, zodbot woke up! 13:23:56 #topic Open package reviews check 13:24:00 I had someone kick it. 13:24:08 #info Please see our review tracker here: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro 13:24:12 oo, awesome, thanks 13:25:39 #info two review tickets, both python type stub packages (one waiting on me for update). 13:26:15 #info music noted that if these are only required for linting during tests, the tests should be patched to not require them---this is also noted in the python packaging guidelines 13:26:34 so I need to check where they are used, and if they are only used for linting, we don't continue with the reviews 13:26:54 #action FranciscoD_ check if typing stub packages are required by packages for anything other than linting 13:28:11 #topic Comp neuro image compose check 13:28:24 #info https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 13:28:27 #info Rawhide comp-neuro compose is chugging along nicely 13:28:51 (Hello.) 13:29:31 o/ 13:30:03 since you're here---did we get an update from glymur upstream w.r.t https://src.fedoraproject.org/rpms/python-glymur/pull-request/10 ? 13:30:35 Hrm, no, I see the issue here, but no response: https://github.com/quintusdias/glymur/issues/604 13:32:29 Yeah, I had forgotten about that. They’ve been fairly responsive in the past, I helped them learn to use qemu-user-static emulation, and I think I saw someone offered them access to real hardware, so I guess they’ve just been busy. 13:32:52 Talking about upstream, I need to inquire about rdflib upstream for python-odml. 13:33:10 .bug 2113639 13:33:12 Penguinpee: 2113639 – python-odml: FTBFS in Fedora rawhide/f37 - https://bugzilla.redhat.com/2113639 13:34:10 music: yeh, also holiday period and all that. Maybe we can nudge them in a few weeks and see how it goes 13:34:55 Penguinpee: I thought you had spoken to them already, but I can't remember what they'd said 🤔 13:35:08 https://github.com/G-Node/python-odml/blob/v1.5.2/CHANGELOG.md#pinning-rdflib-version-to-500-until-further-notice 13:35:25 Ah, this? https://github.com/G-Node/python-odml/issues/417 13:35:46 I did. But there hasn't been any progress since. Thought I might inquire about the state of affairs. 13:35:59 yeh, worth a nudge 13:36:21 * Penguinpee is getting his elbows greased 13:36:25 #action music nudge glymur upstream about s390x failures some time 13:36:37 #action Penguinpee nudge odml upstream about rdflib dep progress some time 13:37:07 #topic Neuro/science query of the week 13:38:15 we're doing this next week if folks want to see what it's all about: https://ocns.github.io/SoftwareWG/2023/01/27/dev-session-michalis-pagkalos-dendrify.html 13:39:34 I don't see anything generally interesting on the planet# 13:40:43 Terminator anyone? https://www.sciencenews.org/article/robot-shape-shifting-gallium-melt-reform-magnetic-fields 13:41:17 That's more Odo from DS9 13:41:38 https://www.sciencenews.org/article/procrastination-harm-fix-resolution 13:42:00 Well, maybe it comes down to who screened it first. Dunno. 13:42:47 Can I enroll my son for any experiments on the procrastination? :P 13:42:53 LOL 13:43:07 https://www.sciencenews.org/article/earth-inner-core-reverse-rotation 13:43:30 Maybe sometime. 😛 13:44:10 You can always enroll him next year. 13:44:24 Or later! 13:44:32 Tomorrow Never Dies! 13:44:37 😆 13:44:50 that's all there is on the planet at the mo 13:45:12 #topic next meeting: day, time, chair 13:45:25 same time, 2 weeks? 13:45:32 i.e., 13 Feb 1300 UTC 13:45:45 Fine with me. 13:47:12 #info Next meeting on Feb 13 at 1300 UTC (same time in 2 weeks) 13:47:14 #topic Open floor 13:47:21 Anything else folks? 13:48:19 I'll be attending FOSDEM coming weekend for the first time. Looking forward to meeting some fellow Fedorians and other FOSS folk in Brussels. 13:48:25 Oo, jupyterlab is under review: https://bugzilla.redhat.com/show_bug.cgi?id=2161525 13:48:55 That'll be nice! I wish I could've come. Silly visas! 13:49:00 maybe next year 13:49:33 Procrastination? 13:49:39 Mañana, mañana... 13:49:55 yk 13:49:55 nah, visa queue in london for schengen visas is ~80 days 13:49:55 or was, when I checked in nov 13:50:27 Wow, that takes some planning ahead. Better apply for next year's visa now. 13:50:27 I've got a work conf in july, so that's my focus. Gotta get all my tix etc. and get a visa appointment for may/june hopefully 13:50:46 yeh, exactly---gotta plan all trips for the next year almost and then apply for a multiple entry visa 13:51:17 but then, my work visa expires in november and that'll need renewing, so more faffing about there 13:51:18 :D 13:52:49 Anyway, let's close the meeting and get back to other things 13:52:52 thanks for coming folks 13:52:56 I'll go send the logs out 13:52:58 #endmeeting