Bug 961117

Summary: glusterfs version went backwards in rawhide
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: glusterfsAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: joe, jonathansteffan, kkeithle, silas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0-0.4.beta1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 04:51:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bruno Wolff III 2013-05-08 20:24:14 UTC
Description of problem:
gluster went from 3.4.0-0.3.alpha3 to 3.4.0-0.1.beta1 which results in people needing to do a downgrade to get a new version. The release should have gone to 3.4.0-0.4.beta1 which would have increased the release while still noting the switch from alpha to beta.

Comment 1 Fedora Update System 2013-05-09 13:38:08 UTC
glusterfs-3.4.0-0.4.beta1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/glusterfs-3.4.0-0.4.beta1.fc19

Comment 2 Fedora Update System 2013-05-09 17:56:47 UTC
Package glusterfs-3.4.0-0.4.beta1.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 glusterfs-3.4.0-0.4.beta1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7769/glusterfs-3.4.0-0.4.beta1.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-05-14 04:51:16 UTC
glusterfs-3.4.0-0.4.beta1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.