#fedora-neuro log

13:00:14 <FranciscoD_> #startmeeting NeuroFedora - 2022-09-12
13:00:15 <zodbot> Meeting started Mon Sep 12 13:00:14 2022 UTC.
13:00:15 <zodbot> This meeting is logged and archived in a public location.
13:00:15 <zodbot> The chair is FranciscoD_. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
13:00:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:00:15 <zodbot> The meeting name has been set to 'neurofedora_-_2022-09-12'
13:00:18 <FranciscoD_> #meetingname neurofedora
13:00:18 <zodbot> The meeting name has been set to 'neurofedora'
13:01:02 <FranciscoD_> #info Agenda, with links, on the blog post: https://neuroblog.fedoraproject.org/2022/09/12/next-open-neurofedora-meeting-12-September-1300-utc.html
13:01:14 <FranciscoD_> #topic New intros and roll call
13:01:25 <FranciscoD_> let's wait ~5 minutes here for everyone to join in
13:01:30 <FranciscoD_> .hello ankursinha
13:01:31 <zodbot> FranciscoD_: Something blew up, please try again
13:01:34 <zodbot> FranciscoD_: An error has occurred and has been logged. Please contact this bot's administrator for more information.
13:01:48 <FranciscoD_> aww, no worries zodbot
13:02:15 <FranciscoD_> #info FAS: ankursinha (FranciscoD on chat/irc); UTC +1 ; packaging, fedora-join, neuro-fedora etc.
13:02:26 <FranciscoD_> if you're here for the meeting, please let me know so I also chair you
13:02:51 <FranciscoD_> #chair music vanessa_kris mairacanal Alessio aekoroglu
13:02:51 <zodbot> Current chairs: Alessio FranciscoD_ aekoroglu mairacanal music vanessa_kris
13:02:56 <music[m]> hello
13:03:05 <FranciscoD_> hi music o/
13:04:29 <FranciscoD_> #chair davdunc lbazan zbyszek[m] Josh Santos omnidapps[m] mhough
13:04:29 <zodbot> Current chairs: Alessio FranciscoD_ Josh Santos aekoroglu davdunc lbazan mairacanal mhough music omnidapps[m] vanessa_kris zbyszek[m]
13:04:34 <FranciscoD_> .members neuro-sig
13:04:35 <zodbot> FranciscoD_: Something blew up, please try again
13:04:39 <zodbot> FranciscoD_: An error has occurred and has been logged. Please contact this bot's administrator for more information.
13:04:43 <FranciscoD_> .members neuro-sig
13:04:44 <zodbot> FranciscoD_: Something blew up, please try again
13:04:47 <zodbot> FranciscoD_: An error has occurred and has been logged. Please contact this bot's administrator for more information.
13:04:57 <FranciscoD_> hrm, that's odd..
13:05:09 <FranciscoD_> anyway, doesn't matter I guess
13:05:13 <FranciscoD_> let's proceed with the agenda
13:05:28 <FranciscoD_> #topic Tasks from last meeting
13:05:35 <FranciscoD_> #info Last meeting logs here: https://meetbot.fedoraproject.org/fedora-neuro/2022-08-29/neurofedora.2022-08-29-13.00.html
13:05:51 <FranciscoD_> #info FranciscoD fix arbor and genesis FTBFS bugs: DONE
13:06:04 <FranciscoD_> - vanessa_kris import python-pyABF and build/push updates
13:06:57 <FranciscoD_> imported, but not built/updates not pushed yet
13:07:00 <FranciscoD_> https://src.fedoraproject.org/rpms/python-pyABF/tree/rawhide
13:07:09 <vanessa_kris[m]> FranciscoD_: On it the build failed no idea why
13:07:26 <FranciscoD_> ah?
13:07:37 <FranciscoD_> was this a scratch build? I'm not seeing any failed builds listed here: https://koji.fedoraproject.org/koji/packageinfo?packageID=35977
13:08:05 <FranciscoD_> do you remember what error you go?
13:08:07 <FranciscoD_> *got?
13:08:47 * vanessa_kris[m] uploaded an image: (3868KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/KNckMMOFjSRyabslrdDxkJvl/ima_49c1612.jpeg >
13:09:06 <vanessa_kris[m]> https://koji.fedoraproject.org/koji/taskinfo?taskID=91937865
13:09:59 <FranciscoD_> hrm, let's have a look at the checkout.log
13:10:43 <FranciscoD_> try again vanessa_kris : could be a transient infra issue
13:10:48 <FranciscoD_> (everything looks fine in your repo)
13:11:01 <vanessa_kris[m]> Alright
13:11:34 <FranciscoD_> 504 is a server timeout error, so maybe the server was down or unresponsive
13:12:19 <music[m]> The git history has some `.src.rpm` files and such checked in
13:12:40 <music[m]> A `fedpkg co` takes a long time for me (minutes).
13:13:18 <FranciscoD_> ah, hrm, maybe it should only do a shallow copy of the latest commit..
13:13:18 <music[m]> `Receiving objects:  45% (17/37), 244.81 MiB | 4.82 MiB/s`
13:13:24 <vanessa_kris[m]> music[m]: mine? I think i deleted that
13:13:42 <FranciscoD_> yeh, but even if you delete it, if it's been committed once, it'll stay in the git history.
13:13:56 <vanessa_kris[m]> ohhh
13:14:04 <FranciscoD_> Not sure if there's a way of "cleaning" that up now. music any ideas?
13:14:41 <mairacanal[m]> FranciscoD_: i believe only with a rebase
13:14:52 <FranciscoD_> vanessa_kris: it's fine and should not be a problem tbh
13:15:02 <FranciscoD_> mairacanal: can't do rebases and force pushes on repos from what I know
13:15:22 <music[m]> Yeah, rewriting dist-git history isn’t normally possible. It would require administrative help (releng, I think?)
13:15:35 <mairacanal[m]> FranciscoD_: yep, so I guess it wouldn't be possible to remove this from history
13:16:03 <music[m]> But the shallow clone is a good idea if there isn’t some obscure reason not to.
13:16:11 <FranciscoD_> I can file an issue with infra/releng about this. Ideally, it should only do a shallow clone if possible, which should help.
13:16:16 <music[m]> Could save time across many builds.
13:16:27 <FranciscoD_> yeh, should be doable, unless rpmautospec requires a deep clone etc.
13:16:48 <music[m]> Hmm, that might be the case.
13:17:07 <FranciscoD_> #action FranciscoD_ file ticket with releng about python-pyABF repo: request cleaning, and ask if shallow clones can be used
13:17:17 <music[m]> Thanks!
13:17:25 <music[m]> `Receiving objects: 100% (37/37), 545.81 MiB | 3.29 MiB/s, done.`
13:17:34 <FranciscoD_> yeh, that's largeish
13:17:45 <FranciscoD_> (should still be fine for infra IMO)
13:18:47 <vanessa_kris[m]> Failed again... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/eb6fbed2ac214cfc189270602047aef775866e6d)
13:19:13 <FranciscoD_> music: shallow clone doesn't keep the complete git history, so we can't use that with rpmautospec. (just tested it out)
13:19:34 <FranciscoD_> > <@vanessa_khris:matrix.org> Failed again... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5d5cc5340468c6aade5748ecd667e7f9db6f076d)
13:19:49 <vanessa_kris[m]> FranciscoD_: Okay, thanks.
13:20:21 <FranciscoD_> vanessa_kris: here's something we can do to prevent it happening in the future: ignore src.rpm files in all git repos so they're not normally committed
13:21:00 <vanessa_kris[m]> FranciscoD_: noted.
13:21:03 <FranciscoD_> create a `~/.gitignore_global` file if you don't have one already, and add: `*.rpm` there
13:21:30 <FranciscoD_> this is a "global gitignore" file, so it'll apply to all repos
13:21:50 <FranciscoD_> if you want to limit it to src.rpms but allow rpms, you can use `*.src.rpm` instead
13:22:40 <FranciscoD_> and I think one can still use `git add --force ..` to add files that are in the ignore list (will have to double check the man pages on that)
13:23:20 <FranciscoD_> No other action items from last meeting, moving to next topic
13:23:30 <FranciscoD_> #topic Open Pagure tickets
13:23:45 <music[m]> Another useful practice is to explicitly list the files you want to add (`git add python-pyABF.spec`) rather than something like `git add .`; in RPM packaging, there are usually few enough files tracked that this isn’t tedious.
13:24:08 <FranciscoD_> #info Any tickets tagged "next meeting" are discussed here: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting
13:24:39 <music[m]> When making changes `git add -p` is sometimes also useful.
13:24:42 <FranciscoD_> #info No tickets to discuss (reading list discussed in separate topic)
13:25:18 <FranciscoD_> yeh, I use `git add -i` and `git add -p` quite a bit 👍️
13:25:54 <FranciscoD_> #topic Package health check
13:26:33 <FranciscoD_> #info Please head over to the neuro-sig packager dashboard: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
13:27:11 <FranciscoD_> note that I took over a few packages that Igor was previously managing. These were orphaned (https://pagure.io/fesco/issue/2858)
13:27:56 <FranciscoD_> we're up to 238 packages now :D
13:28:22 <FranciscoD_> As usual, we focus on FTI and FTBFS bugs first, then on other bugs, then updates etc.
13:28:36 <FranciscoD_> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install
13:29:49 <FranciscoD_> dlib is still FTI, but I think the primary maintainer is looking into it
13:30:37 <FranciscoD_> Updating python-mne to 1.1.1 should hopefully fix that one
13:30:57 <FranciscoD_> #action FranciscoD update python-mne: https://bugzilla.redhat.com/show_bug.cgi?id=2115503
13:32:13 <FranciscoD_> I think neatdend is also broken because of the matplotlib update. Koschei: https://koschei.fedoraproject.org/package/python-neatdend?collection=f38
13:32:26 <FranciscoD_> click on the build.log to see the error
13:33:09 <FranciscoD_> music: why are FTBFS bugs not filed for all issues that koschei shows? Would you know?
13:33:30 <music[m]> dlib upstream issue: https://github.com/davisking/dlib/issues/2659
13:33:44 <FranciscoD_> is it a question of the FTBFS script that creates bugs not having being run?
13:33:45 <music[m]> I don’t know.
13:34:16 <music[m]> It does seem to be a manual script invocation where a bunch get filed at once.
13:34:37 <FranciscoD_> Must be. I often see koschei report them, but no corresponding bugs. Have wondered about that for a while now..
13:34:56 <music[m]> There’s a “File new FTBFS bug” link on the Koschei page that’s helpful when you want a bug for tracking.
13:36:25 <FranciscoD_> Yeh, but that doesn't include the failed build log/trace, I don't think. It'll be good to have a tracker bug in any case. I'll see if maybe there's a setting in koschei that we've not enabled to automatically file bugs
13:37:26 <FranciscoD_> Doesn't look like it. Here's the documentation anyway: https://fedoraproject.org/wiki/Koschei#Reporting_FTBFS_bugs_through_Koschei
13:38:28 <FranciscoD_> maybe we can find out where the manual Fedora wide script is, and I can run it once every two weeks to make sure bugs are filed
13:39:19 <FranciscoD_> i'll take a look (but we want to make sure we don't get in the way of FESCO's FTBFS workflow etc.)
13:40:25 <FranciscoD_> https://bugzilla.redhat.com/show_bug.cgi?id=2113639 -> needs attention
13:41:11 <tg-fedneuro> <sanjay_ankur> @MeWjOr heya, you around? How's it going? I see a couple of bugs in your packages—-any chance you'll be able to look at them sometime?
13:41:31 <FranciscoD_> ^pinged major who is the primary maintainer for python-odml
13:42:28 <FranciscoD_> https://bugzilla.redhat.com/show_bug.cgi?id=2113646 -> new version requires a few new deps
13:42:34 <FranciscoD_> I should prioritise this I guess
13:42:47 <FranciscoD_> #action FranciscoD package up deps for python-pybids update
13:44:11 <FranciscoD_> A few other packages have new versions out, so please do update them and open PRs if you can. A lot of them should be simple Python packages
13:44:26 <FranciscoD_> #info A few packages have new versions out---please update them and open PRs
13:46:14 <FranciscoD_> Any more notes/comments/action items about our packages?
13:46:14 <FranciscoD_> (please action yourself if you want to work on a bug/package update etc.)
13:46:52 <FranciscoD_> #topic Open package reviews check
13:47:26 <FranciscoD_> #info Please head to the neuro-sig package review tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro ; click "show advanced fields", and then look for any bugs blocking this tracker bug
13:48:04 <FranciscoD_> #info No pending review tickets. both python-pyABF and python-pep440 have been approved
13:48:36 <mairacanal[m]> Can I close the ticket? Sorry I'm not sure what the procedure is.
13:49:07 <FranciscoD_> mairacanal[m]: if you mentioned the bug when you created the updates, the bug will automatically be closed when the update goes "stable"
13:49:27 <FranciscoD_> otherwise you'll have to close the bug manually---you can do that now, that's fine too
13:49:37 <mairacanal[m]> FranciscoD_: ah okay. thanks for answer!
13:50:03 <FranciscoD_> no worries, it's awesome that you've been sponsored to the packager group! ✨
13:50:16 <FranciscoD_> please do ping us if you run into issues or if the docs are unclear etc
13:50:26 <FranciscoD_> #topic CompNeuro lab compose status check for Fedora 36/37
13:50:50 <FranciscoD_> #info Please head over to koji to see if the comp-neuro OS image is being generated correctly: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
13:50:58 <FranciscoD_> green tick = all good
13:51:13 <FranciscoD_> #info both f37 and rawhide (f38) OS images are being built fine
13:51:35 <FranciscoD_> (this is the image that will end up on https://labs.fedoraproject.org/comp-neuro/)
13:51:50 <FranciscoD_> #topic Neuroscience query of the week
13:52:13 <FranciscoD_> #info if you have any interesting science/neuroscience to share with the community, this is the topic for it
13:52:41 <FranciscoD_> you can also note these on the reading list ticket: https://pagure.io/neuro-sig/NeuroFedora/issue/318
13:52:53 <FranciscoD_> I see I had one to share a week ago:
13:52:53 <FranciscoD_> https://www.sciencenews.org/article/covid-infection-471-days-coronavirus-evolution-variants
13:53:38 <FranciscoD_> I don't have anything else at the moment, haven't gone through the planets this week
13:53:49 <FranciscoD_> #topic Next meeting day, and chair
13:54:05 <FranciscoD_> same time in 2 weeks?
13:54:20 <FranciscoD_> any takers for chair?
13:56:04 <FranciscoD_> #action FranciscoD chair next meeting
13:56:13 <FranciscoD_> #topic Open floor
13:56:22 <FranciscoD_> #info Anything that wasn't covered in the agenda can go here
13:56:30 <FranciscoD_> we have ~4 minutes left for this :)
14:00:53 <FranciscoD_> OK, closing the meeting then.
14:01:05 <FranciscoD_> #info thanks all for coming: see you in 2 weeks (if not before!)
14:01:11 <FranciscoD_> #endmeeting