Unattended Upgrades fail

Hello,
I know this is not really a tor related issue but maybe someone knows a solution anyway. I am using debian on a vsp and want to run a entry guard relay. I tried to enable automatic updates following this guide: Tor Project | Debian and Ubuntu.

if I run # unattended-upgrade --debug, the output looks like this:

Marking not allowed <apt_pkg.PackageFile object: filename:'/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_main_i18n_Translation-en'  a=stable-updates,c=main,v=11-updates,o=Debian,l=Debian arch='' site='deb.debian.org' IndexType='Debian Translation Index' Size=45666 ID:7> with -32768 pin
Marking not allowed <apt_pkg.PackageFile object: filename:'/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_main_binary-amd64_Packages'  a=stable-updates,c=main,v=11-updates,o=Debian,l=Debian arch='amd64' site='deb.debian.org' IndexType='Debian Package Index' Size=56940 ID:6> with -32768 pin
Applying pinning: PkgFilePin(id=7, priority=-32768)
Applying pin -32768 to package_file: <apt_pkg.PackageFile object: filename:'/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_main_i18n_Translation-en'  a=stable-updates,c=main,v=11-updates,o=Debian,l=Debian arch='' site='deb.debian.org' IndexType='Debian Translation Index' Size=45666 ID:7>
Applying pinning: PkgFilePin(id=6, priority=-32768)
Applying pin -32768 to package_file: <apt_pkg.PackageFile object: filename:'/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_main_binary-amd64_Packages'  a=stable-updates,c=main,v=11-updates,o=Debian,l=Debian arch='amd64' site='deb.debian.org' IndexType='Debian Package Index' Size=56940 ID:6>
Using (^linux-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^kfreebsd-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^gnumach-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-modules-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-kernel-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^linux-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^kfreebsd-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^gnumach-.*-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-modules-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-kernel-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$) regexp to find kernel packages
Using (^linux-.*-5\.10\.0\-21\-amd64$|^linux-.*-5\.10\.0\-21$|^kfreebsd-.*-5\.10\.0\-21\-amd64$|^kfreebsd-.*-5\.10\.0\-21$|^gnumach-.*-5\.10\.0\-21\-amd64$|^gnumach-.*-5\.10\.0\-21$|^.*-modules-5\.10\.0\-21\-amd64$|^.*-modules-5\.10\.0\-21$|^.*-kernel-5\.10\.0\-21\-amd64$|^.*-kernel-5\.10\.0\-21$|^linux-.*-5\.10\.0\-21\-amd64$|^linux-.*-5\.10\.0\-21$|^kfreebsd-.*-5\.10\.0\-21\-amd64$|^kfreebsd-.*-5\.10\.0\-21$|^gnumach-.*-5\.10\.0\-21\-amd64$|^gnumach-.*-5\.10\.0\-21$|^.*-modules-5\.10\.0\-21\-amd64$|^.*-modules-5\.10\.0\-21$|^.*-kernel-5\.10\.0\-21\-amd64$|^.*-kernel-5\.10\.0\-21$) regexp to find running kernel packages
pkgs that look like they should be upgraded: 
Fetched 0 B in 0s (0 B/s)                                                      
fetch.run() result: 0
Packages blacklist due to conffile prompts: []

Anyone has an idea how to solve this issue?
Regards!

I don’t see any issues? Whats the problem?

Ah really? I just thought that the output should look somewhat smoother :laughing: