Bug 2523233 - Non-responsive maintainer check for loveshack
Summary: Non-responsive maintainer check for loveshack
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libxsmm
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dave Love
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-25 05:00 UTC by SY Wang
Modified: 2026-09-21 20:10 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-21 19:19:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description SY Wang 2026-08-25 05:00:29 UTC
This bug is part of the non-responsive maintainer procedure for Dave Love (FAS @loveshack, dave.love.uk), following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

I see they had activities on dist-git recent months (the last one is on rpms/opari2, Aug 12). However, the PR is opened early July and got no response from them so far. I also sent an email to dave.love.uk but didn't get reply.

Please respond if you are still active in Fedora and want to maintain libxsmm.

Comment 1 Peter Robinson 2026-08-25 08:18:09 UTC
I think this should be against the actual libxsmm package.

Comment 2 Dave Love 2026-08-27 17:13:18 UTC
I've been on holiday -- it's that time of year in Europe -- and ill since them (still am).  I've been attending to a few other packages as I've felt able but not that after starting work on an update, and it clearly wasn't stable initially.

I can't find any such email now I've trawled work email.  It wouldn't surprise me if it was junked by Proofpoint, or whatever it is.

Do you want to maintain libxsmm, or what?

Comment 3 SY Wang 2026-08-28 00:26:29 UTC
Dear Dave,

Many thanks for your reply, and hope you recover soon! Yeah, maybe that email ended up in your spam folder :(

I started the non-responsive maintainer procedure because the PR had been open since early July without a response, and I wasn't sure about the maintenance status of libxsmm. Since you've responded here, that concern is resolved.

The reason why I was concerned about this is that we are currently working on re-integrating the CP2K and DBCSR packages in Fedora with the new libxs/libxsmm workflow. The libxs side is already fully prepared (https://src.fedoraproject.org/rpms/libxs/), so once the libxsmm update is available in Fedora, we should be able to complete the downstream re-integration right away.

On a related note, there's also some good news worth sharing: we've integrated Packit into the upstream repository (https://github.com/libxsmm/libxsmm/pull/1084), and Packit builds are now running for every PR and push, so I expect the update workflow to be easier going forward. That daid, I'd also be very happy to be involved with the Fedora libxsmm package if you'd like.

Best,
SY Wang

Comment 4 SY Wang 2026-08-28 05:15:08 UTC
> That daid, ...

It should be "that said". Sorry for typo.

Comment 5 Cristian Le 2026-09-14 11:57:30 UTC
Hi Dave, hope you are feeling better. Just a gentle ping if you could let @uwsy1059 or the scitech_sig share maintenance of libxsmm since cp2k is currently the only consumer of this. If you know other consumers do let us know.

Comment 6 Dave Love 2026-09-18 22:09:27 UTC
I don't have time or energy to deal with this and stuff I wanted to check when I started on the update.  I'll hand it over, but as far as I know it needs a FAS maintainer name for that, not email.

Comment 7 SY Wang 2026-09-19 03:11:05 UTC
Hi Dave,

My FAS username is "growl"(https://src.fedoraproject.org/user/growl), and here is scitech_sig group info (https://src.fedoraproject.org/group/scitech_sig).

Best,
SY

Comment 8 Dave Love 2026-09-21 19:19:06 UTC
I'll transfer it shortly.

Comment 9 SY Wang 2026-09-21 20:10:31 UTC
Many thinks for sharing maintenance! I've also added `scitech_sig` to members list.


Note You need to log in before you can comment on or make changes to this bug.