# Apt update Trouble

**URL:** <https://forum.clockworkpi.com/t/apt-update-trouble/8161>\
**Category:** DevTerm\
**Created:** [March 13, 2022, 1:20am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161 "2022-03-13T01:20:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zappy](https://avatars.discourse-cdn.com/v4/letter/z/eb9ed0/32.png) [@zappy](https://forum.clockworkpi.com/u/zappy)\
**Post date:** [March 13, 2022, 1:20am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/1 "2022-03-13T01:20:47Z")

</div>

Sorry if this has already been on here - I didn’t see anything relevant after a quick glance, but I might have missed it.

I’m getting this error from `apt update`

```auto
The repository 'https://raw.githubusercontent.com/clockworkpi/apt/main/debian stable Release' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
ere

```

I’ve done the key-adding procedure that a websearch suggests, but it doesn’t seem to help.  
It’s probably a brainfart on my end, but can anyone shed some light on this for me?

---

<div class="post-metadata">

**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\
**Post date:** [March 13, 2022, 3:00am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/2 "2022-03-13T03:00:10Z")

</div>

> [@zappy](#):
>
> I’ve done the key-adding procedure that a websearch suggests, but it doesn’t seem to help.

how to did the key-adding procedure?

---

<div class="post-metadata">

**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\
**Post date:** [March 13, 2022, 3:06am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/3 "2022-03-13T03:06:02Z")

</div>

repo has been fixed now

sorry for the misoperation of apt repo

---

<div class="post-metadata">

**Author:** ![mth75](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@mth75](https://forum.clockworkpi.com/u/mth75)\
**Post date:** [March 13, 2022, 12:58pm UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/4 "2022-03-13T12:58:34Z")

</div>

are there any updates available regarding the HDMI output for the A04?

---

<div class="post-metadata">

**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\
**Post date:** [March 14, 2022, 12:16am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/5 "2022-03-14T00:16:43Z")

</div>

no not yet,sorry …

> [@mth75](#):
>
> are there any updates available regarding the HDMI output for the A04?

---

<div class="post-metadata">

**Author:** ![zappy](https://avatars.discourse-cdn.com/v4/letter/z/eb9ed0/32.png) [@zappy](https://forum.clockworkpi.com/u/zappy)\
**Post date:** [March 15, 2022, 1:51am UTC](https://forum.clockworkpi.com/t/apt-update-trouble/8161/6 "2022-03-15T01:51:37Z")

</div>

Thanks, it’s working now!

FYI, these are the commands I found online to try and fix the problem:

```auto
wget -O - https://raw.githubusercontent.com/clockworkpi/apt/main/debian/KEY.gpg | sudo apt-key add - 
sudo apt-key del 57B7A98BBEBA8C10CA4458810DD08811478B1249
sudo apt update

```

Got that from here: [Apt update fails with NO\_PUBKEY error](https://forum.clockworkpi.com/t/apt-update-fails-with-no-pubkey-error/7951)

Thanks again! 😀