Bug 2393777 - Please remove me from the gajim package in dist-git
Summary: Please remove me from the gajim package in dist-git
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: gajim
Version: 45
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Kuhn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-07 21:57 UTC by Robert Scheck
Modified: 2026-08-24 10:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-08-24 10:28:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2025-09-07 21:57:02 UTC
Please remove me (FAS: robert) from the gajim package in dist-git (see: https://src.fedoraproject.org/rpms/gajim). I aimed for gajim in EPEL, but gajim's development doesn't seem to target LTS distributions and I also did not have success with my tickets at Red Hat for updating some libraries in RHEL.

I am currently listed in dist-git as default "Bugzilla Assignee" for EPEL and as collaborator. There are no gajim packages in any active EPEL branch.

Additionally, it could make sense to remove @epel-packagers-sig as well, because the group was emptied (see: https://pagure.io/epel/issue/345).

Thank you.

Comment 1 Robert Scheck 2025-09-07 22:00:04 UTC
For python-nbxmpp (https://src.fedoraproject.org/rpms/python-nbxmpp), it could make sense to remove @epel-packagers-sig at both places (bugzilla assignee, collaborator) as well, given it also was initiated by me (and you are the package maintainer in Fedora for both packages).

Comment 2 Aoife Moloney 2026-08-17 13:59:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

Comment 3 Michael Kuhn 2026-08-24 10:28:17 UTC
Sorry for the late reply, I somehow missed this. I've just removed you and @epel-packagers-sig from both packages, as requested.


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