<html><head><meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /></head><body text="#000099" bgcolor="#FFFFFF">Add:<br>
<br>
exclude=gluster*<br>
<br>
to base and updates.<br><br><div class="gmail_quote">On June 9, 2014 3:23:17 AM PDT, "Kurian @ GnuHack" <kurian@gnuhack.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br />
<br />
We have been using gluster in our 2 node webserver. Where glusterd
and gluster-client both on the same servers. This is configured in
Replicate mode. OS is centos 6. Gluster was installed using
glusterfs-epel repo which was version was at that time version 3.3.<br />
<br />
There were few minor updates which we missed to perform on the
servers. Now when I do yum update, I get dependency conflict as new
version of gluster 3.4 is available in system-updates / system-base
repo.<br />
<br />
To resolve this, should I disable system-update / system-base repo,
proceed with minor update 3.3 first and then enable system-updates /
system-base repo back and upgrade to 3.4?<br />
<br />
Or should I disable gluster-repo permanently and upgrade to 3.4
directly?<br />
<br />
How will I proceed further now.<br />
<br />
<b>Error: Package: glusterfs-server-3.3.1-15.el6.x86_64
(glusterfs-epel)</b><b><br />
</b><b> Requires: glusterfs-fuse = 3.3.1-15.el6</b><b><br />
</b><b> Removing: glusterfs-fuse-3.3.1-1.el6.x86_64
(@glusterfs-epel)</b><b><br />
</b><b> glusterfs-fuse = 3.3.1-1.el6</b><b><br />
</b><b> Updated By:
glusterfs-fuse-3.4.0.57rhs-1.el6_5.x86_64 (system-updates)</b><b><br />
</b><b> glusterfs-fuse = 3.4.0.57rhs-1.el6_5</b><b><br />
</b><b> Available: glusterfs-fuse-3.3.1-15.el6.x86_64
(glusterfs-epel)</b><b><br />
</b><b> glusterfs-fuse = 3.3.1-15.el6</b><b><br />
</b><b> Available: glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64
(system-base)</b><b><br />
</b><b> glusterfs-fuse = 3.4.0.36rhs-1.el6</b><b><br />
</b><b>Error: Package: glusterfs-server-3.3.1-15.el6.x86_64
(glusterfs-epel)</b><b><br />
</b><b> Requires: glusterfs = 3.3.1-15.el6</b><b><br />
</b><b> Removing: glusterfs-3.3.1-1.el6.x86_64
(@glusterfs-epel)</b><b><br />
</b><b> glusterfs = 3.3.1-1.el6</b><b><br />
</b><b> Updated By: glusterfs-3.4.0.57rhs-1.el6_5.x86_64
(system-updates)</b><b><br />
</b><b> glusterfs = 3.4.0.57rhs-1.el6_5</b><b><br />
</b><b> Available: glusterfs-3.3.1-15.el6.x86_64
(glusterfs-epel)</b><b><br />
</b><b> glusterfs = 3.3.1-15.el6</b><b><br />
</b><b> Available: glusterfs-3.4.0.36rhs-1.el6.x86_64
(system-base)</b><b><br />
</b><b> glusterfs = 3.4.0.36rhs-1.el6</b><b><br />
</b><b></b><br />
I should have done the update in a regular basis. Now I need your
suggestions to resolve this mess.<br />
<br />
Regards,<br />
Kurian.<br />
<br />
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Gluster-users mailing list<br />Gluster-users@gluster.org<br /><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>