# Repo sync stuck

**URL:** <https://community.iode.tech/t/repo-sync-stuck/2091>\
**Category:** System and Apps\
**Created:** [30 November 2023 21:45 UTC](https://community.iode.tech/t/repo-sync-stuck/2091 "2023-11-30T21:45:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scr](https://community.iode.tech/letter_avatar_proxy/v4/letter/s/58956e/32.png) [@scr](https://community.iode.tech/u/scr)\
**Post date:** [30 November 2023 21:45 UTC](https://community.iode.tech/t/repo-sync-stuck/2091/1 "2023-11-30T21:45:32Z")

</div>

I am experiencing a similar yet not identical problem described here: [Repo sync stuck: Host key verification failed](https://community.iode.tech/t/repo-sync-stuck-host-key-verification-failed/1554)

Multiple attemts - even from scratch: Always yielding the idenatical result that I fail to download the sources for builing iodeos. Status unchanged since about a week.

It always stops at the same point:

```auto
The authenticity of host 'gitlab.com (2606:4700:90:0:f22e:fbec:5bed:a9b9)' can't be established.neage/sepolicy
ED25519 key fingerprint is SHA256:eUXGGm1YGsMAS7vkcx6JOJdOGHPem5gQp4taiCfCLB8.
This key is not known by any other names
Fetching: 74% (916/1235) 2:26:44 | 20 jobs | 12:26:42 lineage/device_lineage_sepolicy @ device/lineage/sepolicy

```

The complaints about the unestablished authenticity of host [gitlab.com](http://gitlab.com) start right in the beginning. However, download continues up to exactly 74% and then sits there forever.

I do not see a corresponding entry in my ~/.ssh/known\_hosts.

Does anyone know how to interpret these messages - ideally with a hint on how to get past this point so I can create a build for iode 4.7?

Comments and suggestions will be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![vince31fr](https://community.iode.tech/user_avatar/community.iode.tech/vince31fr/32/13_2.png) [@vince31fr](https://community.iode.tech/u/vince31fr)\
**Post date:** [1 December 2023 00:14 UTC](https://community.iode.tech/t/repo-sync-stuck/2091/2 "2023-12-01T00:14:08Z")

</div>

That’s fixed, you can sync again.