Bug 2443312 - Non-responsive maintainer check for neil
Summary: Non-responsive maintainer check for neil
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xastir
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Neil Hanlon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-27 13:43 UTC by Orion Poplawski
Modified: 2026-03-03 04:02 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-03-03 04:02:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2026-02-27 13:43:28 UTC
This bug is part of the non-responsive maintainer procedure for neil, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

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

Comment 1 Neil Hanlon 2026-02-27 17:35:11 UTC
Hi,

Thanks for opening this. I am around but must have missed this email. I'll admit I've been overloaded on professional duties so have not been giving my packages as much attention as they deserve.

I've granted you admin on xastir, if you would like to assist. Otherwise I will review, merge, and build the updates in the next day or so.

--Neil

Comment 2 Orion Poplawski 2026-02-28 00:29:13 UTC
I'm afraid I'm pretty swamped myself, so I may remove myself from xastir if it becomes annoying.  I hit it because it's a downstream dep of hdf5 which I maintain.  You might consider asking for co-maintainers on the devel or other related sig groups.

Thanks for taking a look.

Comment 3 Neil Hanlon 2026-03-02 16:47:43 UTC
Totally fair. I've merged & built your change in rawhide. Do you need it in other branches?

Comment 4 Orion Poplawski 2026-03-03 04:02:15 UTC
I don't particularly, but it is FTBFS in all active Fedora branches so it probably should be.  https://koschei.fedoraproject.org/package/xastir

Thanks.  Closing this now since you have responded.


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