Bug 1749058 - Unresponsive maintainers (achernya)
Summary: Unresponsive maintainers (achernya@mit.edu)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mosh
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alex Chernyakhovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-04 19:02 UTC by Robbie Harwood
Modified: 2021-04-29 16:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-29 16:26:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robbie Harwood 2019-09-04 19:02:41 UTC
Hi, the maintainer of mosh (and rubygems-mysql2, and possibly other things) is unresponsive on bugzilla.  Since I'm worried about the FTBFS bug at [1], I'm starting the non-responsive maintainer process.  Alex, if you're still around and want to keep maintaining your packages, please respond, close this bug, and fix [1][2].  While not a requirement, I present as further evidence that new upstream releases aren't getting packaged [2] (mosh 1.3.2 was released back in July 2017).

1: https://bugzilla.redhat.com/show_bug.cgi?id=1604884
2: https://bugzilla.redhat.com/show_bug.cgi?id=1749054

Comment 1 Ben Cotton 2020-02-11 17:57:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 2 Fedora Program Management 2021-04-29 15:57:22 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Alex Chernyakhovsky 2021-04-29 16:26:34 UTC
Not sure why this is still open...I'm very much responsive and active.


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