Bug 1246855

Summary:	gromacs-5.0.6 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	gromacs	Assignee:	Dominik 'Rathann' Mierzejewski <dominik>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dakingun, dominik
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gromacs-5.0.6-4.fc22	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-19 08:17:18 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 2015-07-26 12:12:59 UTC

Latest upstream release: 5.0.6
Current version/release in rawhide: 5.0.5-3.fc23
URL: ftp://ftp.gromacs.org/pub/gromacs/

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-07-26 12:24:50 UTC

Failed to kick off scratch build.

cmd:  sha256sum /var/tmp/thn-g6s1Gb/100.0%
return code:  1
stdout:

stderr:
sha256sum: /var/tmp/thn-g6s1Gb/100.0%: No such file or directory

Comment 2 Upstream Release Monitoring 2015-07-27 01:07:06 UTC

rathann's gromacs-5.0.6-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=672281

Comment 3 Fedora Update System 2015-07-28 08:09:44 UTC

gromacs-5.0.6-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/gromacs-5.0.6-1.fc22

Comment 4 Fedora Update System 2015-07-30 00:38:37 UTC

Package gromacs-5.0.6-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gromacs-5.0.6-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-12063/gromacs-5.0.6-1.fc22
then log in and leave karma (feedback).

Comment 5 Upstream Release Monitoring 2015-08-04 18:31:25 UTC

zbyszek's gromacs-5.0.6-2.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=673611

Comment 6 Upstream Release Monitoring 2015-08-06 02:32:13 UTC

jwakely's gromacs-5.0.6-3.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=675690

Comment 7 Upstream Release Monitoring 2015-08-06 14:29:58 UTC

rathann's gromacs-5.0.6-4.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=675817

Comment 8 Fedora Update System 2015-08-07 17:03:49 UTC

gromacs-5.0.6-4.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/gromacs-5.0.6-4.fc23

Comment 9 Fedora Update System 2015-08-07 17:03:57 UTC

gromacs-5.0.6-4.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/gromacs-5.0.6-4.fc22

Comment 10 Upstream Release Monitoring 2015-08-11 07:43:46 UTC

zbyszek's gromacs-5.0.6-5.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=676637

Comment 11 Upstream Release Monitoring 2015-08-15 21:37:04 UTC

zbyszek's gromacs-5.0.6-6.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=677585

Comment 12 Fedora Update System 2015-08-19 08:17:18 UTC

gromacs-5.0.6-4.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.