Bug 1396155 - Mutt 1.7.1 was released on October 8, 2016
Summary: Mutt 1.7.1 was released on October 8, 2016
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mutt
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matej Mužila
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-17 15:37 UTC by Don Pellegrino
Modified: 2018-07-25 07:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-25 07:06:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Don Pellegrino 2016-11-17 15:37:00 UTC
Description of problem:

There is a new 1.7.1 release upstream. It seems that RHEL could track upstream more closely with mutt as it is a pretty self-contained package.

Comment 2 Honza Horak 2016-11-23 14:25:01 UTC
Is there any specific feature or bug fixed that you would like to see update for?

Comment 3 Don Pellegrino 2016-11-23 15:22:19 UTC
I use the IMAP backend and the release notes indicate "Mutt 1.7.1 was released on October 8, 2016. This is a bug-fix release, fixing an imap segfault along with several other small issues." (http://www.mutt.org/). I would prefer to avoid IMAP segfaults that are avoidable. This would just be preventative maintenance for me and could be given prioritization as appropriate.

Comment 4 Honza Horak 2016-11-25 08:26:36 UTC
Thank you for providing that information, we'll consider updating, but I don't expect it will happen any time soon.

Comment 5 Don Pellegrino 2016-11-28 15:09:34 UTC
Fair enough. Thanks.

For reference, is there any documentation I could read to better understand the process flow and policies that effect upstream releases flowing into Red Hat updates?

Comment 6 Honza Horak 2018-02-21 07:02:10 UTC
(In reply to Don Pellegrino from comment #5)
> For reference, is there any documentation I could read to better understand
> the process flow and policies that effect upstream releases flowing into Red
> Hat updates?

(sorry for long delay, this question somehow got from my radar)

There are basically two points of view:

One is compatibility, that may block something newer from getting into the release (should not be too big problem here, but we didn't look closely yet).

Second is an official customer request through https://access.redhat.com/support/, because RHEL updates are customer-driven and only issues with high-enough priority can be addressed. The same site should also provide further info about the process.

Comment 7 Honza Horak 2018-07-25 07:06:53 UTC
Since we have no other requests for the rebase, it is not likely that mutt will be rebased in RHEL-7 timeframe, so I'm closing this for now. If this request has a reasonable business reasoning, please, open a case in the customer portal https://access.redhat.com/support/.


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