[Gluster-users] GlusterFS repo versioning

[Atin Mukherjee]

Looks like the was cached and when I opened it in a private session, I
could see that link is pointing to 3.6.

Apologies Humble!

~Atin

On 08/18/2015 11:37 AM, Atin Mukherjee wrote:
> Here is the content of
> http://download.gluster.org/pub/gluster/glusterfs/3.6/3.6.3/EPEL.repo/glusterfs-epel.repo
> 
> # Place this file in your /etc/yum.repos.d/ directory
> 
> [glusterfs-epel]
> name=GlusterFS is a clustered file-system capable of scaling to several
> petabytes.
> baseurl=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-$releasever/$basearch/
> enabled=1
> skip_if_unavailable=1
> gpgcheck=1
> gpgkey=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/pub.key
> 
> [glusterfs-noarch-epel]
> name=GlusterFS is a clustered file-system capable of scaling to several
> petabytes.
> baseurl=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-$releasever/noarch
> enabled=1
> skip_if_unavailable=1
> gpgcheck=1
> gpgkey=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/pub.key
> 
> [glusterfs-source-epel]
> name=GlusterFS is a clustered file-system capable of scaling to several
> petabytes. - Source
> baseurl=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-$releasever/SRPMS
> enabled=0
> skip_if_unavailable=1
> gpgcheck=1
> gpgkey=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/pub.key
> 
> All of these base urls are pointing to the latest glusterfs where as I
> expect it should refer to 3.6 repos.
> 
> http://download.gluster.org/pub/gluster/glusterfs/3.6/LATEST/.... should
> be the right path instead of
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/...
> 
> Let me know if you think otherwise.
> 
> ~Atin
> 
> 
> On 08/18/2015 11:15 AM, Humble Devassy Chirammal wrote:
>> Hi Jeremy & Atin,
>>
>>
>>> I noticed the urls all point to LATEST. Shouldn't it read 3.6/3.6.3/?
>>>> Yes, its pointing to latest 3.7.3 bits and it needs a correction. Thanks
>>>> for pointing this out.
>>
>>
>> I *dont* think it should be the case, that said, when 3.6.1 is released you
>> pull the repo file  which  points to '3.6/LATEST'  as its the LATEST
>> version of GlusterFS 3.6.
>>
>> Then after a specific period, the next minor release of 3.6  ( 3.6.2 ,
>> 3.6.3, 3.6.4..etc) comes in, whenever it happens the 'subscribed system'
>> will get 'LATEST' release of 3.6.
>>
>> If you really want to stick with one specific version of 3.6 release, you
>> could edit the repo file and stick with that.
>>
>>
>> --Humble
>>
> 

-- 
~Atin