Bug 961117 - glusterfs version went backwards in rawhide
Summary: glusterfs version went backwards in rawhide
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glusterfs
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-08 20:24 UTC by Bruno Wolff III
Modified: 2013-05-14 04:51 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0-0.4.beta1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-14 04:51:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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