<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Even,</p>
<p>Unfortunately, the builds still fail with the same error messages
today.</p>
<p>I tried following setups:</p>
<p>- Branch: <font size="2"><i>master</i></font>; Command: <font
size="2"><i>docker/ubuntu-full/build.sh --platform linux/amd64</i></font><br>
</p>
<p>- Branch: <font size="2"><i>release/3.5</i></font>; Command: <font
size="2"><i>docker/ubuntu-full/build.sh --platform linux/amd64
--gdal v3.5.3</i></font></p>
<p>I am on the latest git status in both cases.</p>
<p>I also deleted the <i><font size="2">gdal-docker-cache</font> </i>by
executing<i> <font size="2">rm -rf ~/gdal-docker-cache</font> </i>but
it did not solve the problem.<br>
</p>
<p>Regards,</p>
<p>Dirk</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 28.03.23 um 22:00 schrieb Even
Rouault:<br>
</div>
<blockquote type="cite"
cite="mid:9f17082a-8da4-931e-6c87-e04905b805f7@spatialys.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Dirk,<br>
</p>
<div class="moz-cite-prefix">Le 28/03/2023 à 21:11, Dirk Stenger a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:8ceb8c2a-124d-d04d-3364-7da04be989a7@lat-lon.de">
<p>All,</p>
<p>Currently, the GDAL Docker Build fails:</p>
<p><i>~/git/gdal$ docker/ubuntu-full/build.sh --platform
linux/amd64</i><i><br>
</i><i>...</i><i><br>
</i><i> ---> Running in c13d037d7761</i><i><br>
</i><i>Downloading cache...</i><i><br>
</i><i>rsync: [sender] change_dir
"osgeo/gdal:ubuntu-full/proj/x86_64" (in gdal-docker-cache)
failed: No such file or directory (2)</i><i><br>
</i><i>rsync error: some files/attrs were not transferred (see
previous errors) (code 23) at main.c(1865) [Receiver=3.2.7]</i><i><br>
</i><i>rsync: [Receiver] read error: Connection reset by peer
(104)</i><i><br>
</i><i>The command '/bin/sh -c .
/buildscripts/bh-set-envvars.sh &&
DESTDIR=/build_tmp_proj /buildscripts/bh-proj.sh
&& LD_LIBRARY_PATH=/build_tmp_proj/usr/local/lib
/build_tmp_proj/usr/local/bin/projsync --target-dir
/tmp/proj_grids --all && rm -rf
/build_tmp_proj' returned a non-zero code: 23</i><br>
</p>
<p>A couple of days ago, I was still able to build it (v3.5).</p>
</blockquote>
<p>Make sure you update on latest git. If you're on the 3.5
branch, I'm not sure its build scripts will work properly with
latest master</p>
<p>But given where the error occurs, I suspect this might be
something related to downloading PROJ remote grids. There has
been a new grid added today and the indexes refreshed. Perhaps
there has been some out-of-sync issue with CloudFront. I suggest
you just retry, a few times if needed (that just worked fine for
me without any need for retry, but we might not hit the same
CloudFront instances)<br>
</p>
<p>Even</p>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com" moz-do-not-send="true">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
l a t / l o n GmbH
Im Ellig 1 53343 Wachtberg, Germany
phone ++49 +228 24 333 784
<a class="moz-txt-link-freetext" href="http://www.lat-lon.de">http://www.lat-lon.de</a> <a class="moz-txt-link-freetext" href="http://www.deegree.org">http://www.deegree.org</a>
lat/lon gesellschaft für raumbezogene informationssysteme mbH
Registergericht: Amtsgericht Bonn, HRB 13042
Geschäftsführer: Jens Fitzke und Torsten Friebe</pre>
</body>
</html>