<div dir="auto"><div>Hi, <br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 10, 2020, 15:23 Emilio Fernandes <<a href="mailto:emilio.fernandes70@gmail.com">emilio.fernandes70@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello Varnish team,<div><br></div><div>I'd like to ask whether AARCH64 architecture is officially supported one.</div><div>I wasn't able to find anything on the website but I've found that there is a CI [1] and some tickets [2]. </div><div>Few comments in this ticket [3] say that ARM64 is known to work fine on FreeBSD and Linux (Ubuntu & Fedora).</div><div>Finally I see only x86_64 and amd64 packages at [4]</div><div><br></div><div>My request is: Would it be possible to add aarch64 package(s) to PackageCloud too ?</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">+1 for ARM64 packages! </div><div dir="auto"><br></div><div dir="auto">Martin</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>OSes update the packages with a delay. At the moment the only option to update after a security</div><div>release fix is to build from source. It is OK but it would be nicer if "apt update && apt upgrade" </div><div>does it for me as soon as there is something new in PackageCloud.</div><div><br></div><div>And maybe mention somewhere on the website which are the supported architectures.</div><div><br></div><div>Thank you for Varnish Cache!</div><div><br></div><div>Gracias!</div><div>Emilio</div><div><br></div><div>1. <a href="https://github.com/varnishcache/varnish-cache/blob/b365be2d281944d5c79be92ff73b3dc02c5db6be/.travis.yml#L35-L43" target="_blank" rel="noreferrer">https://github.com/varnishcache/varnish-cache/blob/b365be2d281944d5c79be92ff73b3dc02c5db6be/.travis.yml#L35-L43</a></div><div>2. <a href="https://github.com/varnishcache/varnish-cache/issues?q=is%3Aissue+aarch64+" target="_blank" rel="noreferrer">https://github.com/varnishcache/varnish-cache/issues?q=is%3Aissue+aarch64+</a> & <a href="https://github.com/varnishcache/varnish-cache/issues?q=is%3Aissue+arm64" target="_blank" rel="noreferrer">https://github.com/varnishcache/varnish-cache/issues?q=is%3Aissue+arm64</a></div><div>3. <a href="https://github.com/varnishcache/varnish-cache/issues/3227#issuecomment-590334301" target="_blank" rel="noreferrer">https://github.com/varnishcache/varnish-cache/issues/3227#issuecomment-590334301</a></div><div>4. <a href="https://packagecloud.io/varnishcache/varnish63?page=1" target="_blank" rel="noreferrer">https://packagecloud.io/varnishcache/varnish63?page=1</a></div></div>
_______________________________________________<br>
varnish-dev mailing list<br>
<a href="mailto:varnish-dev@varnish-cache.org" target="_blank" rel="noreferrer">varnish-dev@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev" rel="noreferrer noreferrer" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev</a><br>
</blockquote></div></div></div>