<div dir="ltr">The discussion has been moved to <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261">https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261</a> ...</div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 15, 2018 at 5:55 PM Alistair Grant <<a href="mailto:akgrant0710@gmail.com">akgrant0710@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Hi Everyone,<br>
<br>
Linux builds have been failing recently with error messages like:<br>
<br>
E: Failed to fetch <a href="http://something.deb" rel="noreferrer" target="_blank">http://something.deb</a> 404 Not Found [IP: 35.184.213.5 80]<br>
<br>
I've seen these types of errors on my machine, typically when I forget<br>
to run apt-get update before attempting to install or upgrade<br>
packages.<br>
<br>
@Rydier kindly provided some supporting evidence for the problem:<br>
<br>
--<br>
Error logs of linux builds for<br>
<a href="https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/378430866" rel="noreferrer" target="_blank">https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/378430866</a><br>
(and onwards) state they try loading<br>
<a href="http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.3_amd64.deb" rel="noreferrer" target="_blank">http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.3_amd64.deb</a><br>
while the file on server is<br>
<a href="http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.4_amd64.deb" rel="noreferrer" target="_blank">http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.4_amd64.deb</a><br>
so an out-of-date package cache is the likely culprit?<br>
--<br>
<br>
<br>
I've created an experimental branch which appears to solve the problem:<br>
<br>
<a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261" rel="noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261</a><br>
<br>
However I would expect that the travis infrastructure should<br>
automatically update build environments to ensure that the package<br>
cache is up to date.<br>
<br>
Can someone who is familiar with travis perhaps confirm that this is<br>
the correct approach, or suggest a better alternative (one possibility<br>
is that we keep this until the infrastructure is updated and then<br>
revert it).<br>
<br>
Thanks,<br>
Alistair<br>
</blockquote></div>