all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] Unable to sync Debian Bullseye repo
Date: Wed, 18 Oct 2023 15:42:35 +0200	[thread overview]
Message-ID: <fb3fe61b-48c7-43b4-8597-d6e216aff80b@gmail.com> (raw)

Hi all,

since a few days my mirror server is unable to update the Bullseye repo.

Config in /etc/proxmox-offline-mirror.cfg:

mirror: bullseye
        architectures all
        architectures amd64
        base-dir /srv/www/debian/.mirror
        ignore-errors false
        key-path /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.asc
        repository deb http://ftp.de.debian.org/debian bullseye main contrib non-free
        sync true
        verify true

Error that is shown:

# proxmox-offline-mirror mirror snapshot create bullseye
Fetching Release/Release.gpg files
-> GET 'http://ftp.de.debian.org/debian/dists/bullseye/Release.gpg'..
-> GET 'http://ftp.de.debian.org/debian/dists/bullseye/Release'..
Verifying 'Release(.gpg)' signature using provided repository key..

Encountered 2 errors:

Signature #0: Missing key: A7236886F3CCCAAD148A27F80E98404D386FA1D9

Signature #1: Missing key: 4CB50190207B4758A3F73A796ED0E7B82643E131

Error: No valid signature found.


Any other mirror is synchronized successfully, e.g.

- bookworm
- bookworm-backports
- bookworm-security
- bookworm-updates
- bullseye-backports
- bullseye-security
- bullseye-updates


Any thoughts?


Thanks,

	Uwe



                 reply	other threads:[~2023-10-18 13:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb3fe61b-48c7-43b4-8597-d6e216aff80b@gmail.com \
    --to=uwe.sauter.de@gmail.com \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal