Bug 1150493

Summary: mksh-50d is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: mkshAssignee: Robert Scheck <redhat-bugzilla>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fweimer, mhlavink, redhat-bugzilla
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mksh-50d-1.el5 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-16 01:59:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2014-10-08 11:28:04 UTC
Latest upstream release: 50d
Current version/release in Fedora Rawhide: 50c-1.fc22
URL: https://www.mirbsd.org/MirOS/dist/mir/mksh/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service will be implemented by a new system: https://github.com/fedora-infra/anitya/
It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.

Comment 1 Robert Scheck 2014-10-08 11:40:40 UTC
Florian, seeing you on Cc makes me assuming that this is security relevant?

Comment 2 Florian Weimer 2014-10-08 12:01:12 UTC
(In reply to Robert Scheck from comment #1)
> Florian, seeing you on Cc makes me assuming that this is security relevant?

50c was the release with the security fixes.

Comment 3 Robert Scheck 2014-10-08 12:04:09 UTC
(In reply to Florian Weimer from comment #2)
> 50c was the release with the security fixes.

Okay, so nothing hidden in 50d (aside of the regression fix from 50c). And 50c
is anyway in testing repositories for Fedora and EPEL.

Comment 4 Fedora Update System 2014-10-08 12:06:20 UTC
mksh-50d-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/mksh-50d-1.fc21

Comment 5 Fedora Update System 2014-10-08 12:58:32 UTC
mksh-50d-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/mksh-50d-1.fc20

Comment 6 Fedora Update System 2014-10-08 12:58:48 UTC
mksh-50d-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mksh-50d-1.fc19

Comment 7 Fedora Update System 2014-10-10 16:02:14 UTC
Package mksh-50d-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mksh-50d-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12497/mksh-50d-1.fc19
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-10-16 01:59:43 UTC
mksh-50d-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-10-18 20:31:41 UTC
mksh-50d-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/mksh-50d-1.el5

Comment 10 Fedora Update System 2014-10-19 13:21:05 UTC
mksh-50d-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2014-10-19 13:22:48 UTC
mksh-50d-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2014-11-02 21:08:35 UTC
mksh-50d-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.