# Update DietPi from v7.3.2 to v8.4.2 keep failing (error messages inside) **URL:** \ **Category:** Troubleshooting\ **Created:** [25 May 2022 05:31 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220 "2022-05-25T05:31:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rak007](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/r/f17d59/32.png) [@rak007](https://dietpi.com/forum/u/rak007)\ **Post date:** [25 May 2022 05:31 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/1 "2022-05-25T05:31:56Z")
### Creating a bug report/issue #### Required Information - DietPi version: G\_DIETPI\_VERSION\_CORE=7 G\_DIETPI\_VERSION\_SUB=3 G\_DIETPI\_VERSION\_RC=2 G\_GITBRANCH=‘master’ G\_GITOWNER=‘MichaIng’ - Distro version: buster 1 - Kernel version: Linux DietPi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l GNU/Linux - SBC model: RPi 4 Model B (armv7l) - Power supply used : 3Amp - SD card used: Sandisk I think #### Additional Information (if applicable) - Bug report ID: dbd59660-bdec-48bb-97f9-0b3fca6f2d48 #### Steps to reproduce 1. Run dietpi-launcher and select the update option to update dietpi using inbuilt utility. #### Expected behaviour - Dietpi should be updated #### Actual behaviour - Update is erroring out with error shown below. #### Extra details (Log of the update which shows error) ```auto │ APT update │ - Command: apt-get -q update │ - Exit code: 100 │ - DietPi version: v7.3.2 (MichaIng/master) | HW_MODEL: 4 | HW_ARCH: 2 | DISTRO: 5 │ - Image creator: DietPi Core Team │ - Pre-image: Raspberry Pi OS Lite │ - Error log: │ Hit:1 https://download.mono-project.com/repo/debian raspbianbuster InRelease │ Get:2 http://deb.debian.org/debian buster-backports InRelease [46.7 kB] │ Hit:3 https://apt.sonarr.tv/debian buster InRelease │ Hit:4 https://archive.raspberrypi.org/debian buster InRelease │ Err:2 http://deb.debian.org/debian buster-backports InRelease │ The following signatures couldn't be verified because the public key is not available: NO_PUBKEY │ 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 │ Hit:5 https://repo.jellyfin.org/debian buster InRelease Get:6 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] │ Get:7 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB] │ Ign:7 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages │ Get:7 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [18.3 MB] │ Reading package lists... │ W: GPG error: http://deb.debian.org/debian buster-backports InRelease: The following signatures couldn't be │ verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 │ E: The repository 'http://deb.debian.org/debian buster-backports InRelease' is not signed. ``` ---
**Author:** ![trendy](https://dietpi.com/forum/user_avatar/dietpi.com/trendy/32/61_2.png) [@trendy](https://dietpi.com/forum/u/trendy)\ **Post date:** [25 May 2022 05:54 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/2 "2022-05-25T05:54:43Z")
```auto sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 648ACFD622F3D138 ``` ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [25 May 2022 06:00 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/3 "2022-05-25T06:00:30Z")
Welcome to our community. If I recall correctly the Debian repository was not part of our old RPI Buster images. Therefore the public key is missing. Did you added the Debian Buster Repository manually? Btw you simply could run `dietpi-update` to update your system. Anyway before doing this, I would recommend to update all `apt` package end ensure correct functioning of your system, because your system is quite old and there might be a lot of packages to be updated. You could do this by running ```auto apt update apt upgrade ``` Before running any update, think of creating a backup. Just in case 😉 ---
**Author:** ![rak007](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/r/f17d59/32.png) [@rak007](https://dietpi.com/forum/u/rak007)\ **Post date:** [25 May 2022 08:27 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/4 "2022-05-25T08:27:43Z")
Thank you so much for this. I was able to upgrade after running those 2 commands. ---
**Author:** ![rak007](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/r/f17d59/32.png) [@rak007](https://dietpi.com/forum/u/rak007)\ **Post date:** [25 May 2022 08:28 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/5 "2022-05-25T08:28:48Z")
Thanks, Yes I rarely update my DietPi setup so everything is old. atp upgrade ran for 30 min upgrading 250+ packages. But eventually I was able to upgrade my DietPi. ---
**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\ **Post date:** [25 May 2022 10:55 UTC](https://dietpi.com/forum/t/update-dietpi-from-v7-3-2-to-v8-4-2-keep-failing-error-messages-inside/13220/6 "2022-05-25T10:55:07Z")
Instead of adding the key in a deprecated way to `/etc/apt/trusted.gpg` (what `apt-key` does, which itself is deprecated), I suggest installing the related keyring package: [Index of /debian/pool/main/d/debian-archive-keyring](https://ftp.debian.org/debian/pool/main/d/debian-archive-keyring/) ```bash cd /tmp curl -O 'https://ftp.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2019.1+deb10u1_all.deb' dpkg -i debian-archive-keyring_2019.1+deb10u1_all.deb rm debian-archive-keyring_2019.1+deb10u1_all.deb ``` This places they keys as dedicated files into `/etc/apt/trusted.gpg.d`. Keep in mind when mixing Raspbian and Debian backports, that you are mixing packages with different binary architecture (ARMv6 vs ARMv7) and that there may be potential version/dependency conflicts. As long as packages do install/upgrade fine, no need to worry about it, but just keep that in mind when APT throws related errors, so you know what you might need to look at.