<div dir="ltr"><div>> Why is this preferable to what's in the README.txt (i.e. "wget -O - <a href="https://download.gluster.org/pub/gluster/glusterfs/5/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/5/rsa.pub</a> | apt-key add -") ?<br></div><div><br></div><div>> You import the key once, and it works for every update after that? That's what Louis Zuckerman (a.k.a. semiosis), the original gluster debian packager suggested. I don't know enough to know why your deb cmd is better than semiosis' apt-key add cmd?</div><div><br></div><div>> Also the fact that the key hasn't actually changed since glusterfs-5 means, among other things, you only need to change the /etc/apt/sources.list.d/gluster.list and updates to -6 or -7 will just keep working with the key you already imported.<br></div><span class="gmail-im" style="color:rgb(80,0,80)"><div><br></div><div>These things might be fine if you're manually maintaining a handful of servers (pets), but they're detrimental when maintaining large amounts of servers/VMs/Docker images/etc which need to be provisioned from scratch with reliable, repeatable recipes (cattle). Users shouldn't have to know or care that they need to install rsa.pub from version 5, 6, or 7 to install the LATEST client, nor should they need to know that rsa.pub hasn't changed since version 5. They should know that they can always install LATEST with a key available at a stable URL (e.g. <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub</a>), even when new versions are released.</div><div><br></div><div><div style="color:rgb(34,34,34)">> I have the possibly mistaken impression that not everyone wants to always use .../glusterfs/LATEST. Some people want to install glusterfs-6 and stay on -6, i.e. .../glusterfs/6/LATEST. And they'd be really upset if they came in one morning to find that an automatic update (however good or bad an idea that is) had updated them to glusterfs-7 when they weren't ready for it. (And worse, if it broke their system.)</div><div style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)">Absolutely, that's why both <a href="https://download.gluster.org/pub/gluster/glusterfs/7/LATEST/">https://download.gluster.org/pub/gluster/glusterfs/7/LATEST/</a> and <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/">https://download.gluster.org/pub/gluster/glusterfs/LATEST/</a> exist, right? I'm not suggesting that anything within the major version folders change, I'm suggesting that in addition to the <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/">https://download.gluster.org/pub/gluster/glusterfs/LATEST/</a> repo we also have a LATEST rsa.pub at a URL which doesn't change. If internally <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/">https://download.gluster.org/pub/gluster/glusterfs/LATEST/</a> is just a symlink and it doensn't make sense to put said LATEST rsa.pub inside that dir, maybe it could be top level (<a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST_rsa.pub">https://download.gluster.org/pub/gluster/glusterfs/LATEST_rsa.pub</a> or similar). It really doesn't matter where it is, as long as it doesn't move and always matches <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/">https://download.gluster.org/pub/gluster/glusterfs/LATEST/</a>.</div><div style="color:rgb(34,34,34)"> </div><div style="color:rgb(34,34,34)">> And apropos of nothing in particular, perhaps we should create a new key for glusterfs-8 when that time comes; it's probably time.</div><div style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)">+1<br></div><div class="gmail-yj6qo gmail-ajU" style="outline:none;padding:10px 0px;width:22px;margin:2px 0px 0px;color:rgb(34,34,34)"><br class="gmail-Apple-interchange-newline"></div></div></span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 29, 2019 at 12:22 PM Kaleb Keithley <<a href="mailto:kkeithle@redhat.com">kkeithle@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 28, 2019 at 1:03 PM Shane St Savage <<a href="mailto:shane@axiomdatascience.com" target="_blank">shane@axiomdatascience.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Adding rsa.pub at <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub</a> would allow bootstrapping Debian servers with the following repo/key:<div><br></div><div><div>deb <a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/$%7BRELEASE%7D/amd64/apt" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/${RELEASE}/amd64/apt</a> ${RELEASE} main<br></div><div><a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub</a><br></div><div><br></div><div>In other words, only LATEST would have to be referenced instead of LATEST and some specific version for the key.</div></div></div></blockquote><div><br></div><div>I'm not a Debian packaging expert. (Even if sometimes I play one on TV.) Why is this preferable to what's in the README.txt (i.e. "wget -O - <a href="https://download.gluster.org/pub/gluster/glusterfs/5/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/5/rsa.pub</a> | apt-key add -") ?</div><div><br></div><div>You import the key once, and it works for every update after that? That's what Louis Zuckerman (a.k.a. semiosis), the original gluster debian packager suggested. I don't know enough to know why your deb cmd is better than semiosis' apt-key add cmd?</div><div><br></div><div>Also the fact that the key hasn't actually changed since glusterfs-5 means, among other things, you only need to change the /etc/apt/sources.list.d/gluster.list and updates to -6 or -7 will just keep working with the key you already imported.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>As an example of why this is useful, Gluster 7 has been released since my original mail, so now the key for LATEST is at <a href="https://download.gluster.org/pub/gluster/glusterfs/7/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/7/rsa.pub</a> instead of <a href="https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub</a>. Every time a new verison of Gluster is released the recipe for installing the latest Gluster client has to be updated.</div></div></div></blockquote><div><br></div><div>I have the possibly mistaken impression that not everyone wants to always use .../glusterfs/LATEST. Some people want to install glusterfs-6 and stay on -6, i.e. .../glusterfs/6/LATEST. And they'd be really upset if they came in one morning to find that an automatic update (however good or bad an idea that is) had updated them to glusterfs-7 when they weren't ready for it. (And worse, if it broke their system.)</div><div> </div><div>And apropos of nothing in particular, perhaps we should create a new key for glusterfs-8 when that time comes; it's probably time.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 11:42 PM Kaleb Keithley <<a href="mailto:kkeithle@redhat.com" target="_blank">kkeithle@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>What is the issue that this would solve?</div><div><br></div><div>The Debian README.txt files and RPM repo files for 6.x all say the rsa.pub is at <a href="https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub</a> and have since day one.</div><div><br></div><div>(Likewise the rsa.pub for 5.x is at <a href="https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/5/rsa.pub)<br></a></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 10:29 PM Shane St Savage <<a href="mailto:shane@axiomdatascience.com" target="_blank">shane@axiomdatascience.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>Any chance of getting an rsa.pub available in</div><div><br></div><div><a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/</a><br></div><div><br></div><div>at</div><div><br></div><div><a href="https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub</a><br></div><div><br></div><div>?</div><div><br></div><div>(in this case, it should be <a href="https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub</a>).</div><div><br></div><div>Thanks,</div><div>Shane</div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>