[gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
srangana at redhat.com
Wed Mar 13 11:09:59 UTC 2019
We need to respin 5.4 with the 2 additional commits as follows,
commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
core: make compute_cksum function op_version compatible
dict: handle STR_OLD data type in xdr conversions
As the current build breaks rolling upgrades, we had held back on
announcing 5.4 and are now ready with the fixes that can be used to
Let me know if I need to do anything more from my end for help with the
Once the build is ready, we would be testing it out as usual.
NOTE: As some users have picked up 5.4 the announce would also carry a
notice, that they need to do a downserver upgrade to the latest bits
owing to the patches that have landed in addition to the existing content.
On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> On 2/27/19 5:19 AM, Niels de Vos wrote:
>> On Tue, Feb 26, 2019 at 02:47:30PM +0000, jenkins at build.gluster.org wrote:
>>> SRC: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>>> HASH: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>> Packages for the CentOS Storage SIG are now available for testing.
>> Please try them out and report test results on this list.
>> # yum install centos-release-gluster
>> # yum install --enablerepo=centos-gluster5-test glusterfs-server
> Due to patch  upgrades are broken, so we are awaiting a fix or revert
> of the same before requesting a new build of 5.4.
> The current RPMs should hence not be published.
> Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> are we expecting the fix to land in 5.4 (as in )?
>  Patch causing regression: https://review.gluster.org/c/glusterfs/+/22148
>  Proposed fix on master: https://review.gluster.org/c/glusterfs/+/22297/
> maintainers mailing list
> maintainers at gluster.org
More information about the packaging