Migration 11.x vers 12.x

What type of hardware are you using: Other(?)
What YunoHost version are you running: 11.3.0.2
How are you able to access your server: The webadmin
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: Mon installation est sur un vps d’OVH

Describe your issue

La migration vers la version 12.x de younohost a échoué.

Share relevant logs or error messages

ended_at: 2025-12-06 17:08:17.843860
error: ‘Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed
to run command ‘‘aptitude update’’’
interface: cli
operation: tools_migrations_migrate_forward
parent: null
started_at: 2025-12-06 17:08:14.439732
success: false
yunohost_version: 11.3.0.2

============

2025-12-06 17:08:14,448: INFO - Running migration 0027_migrate_to_bookworm…
2025-12-06 17:08:14,456: INFO - Starting migration to Bookworm…
2025-12-06 17:08:14,648: INFO - Patching the sources.lists file…
2025-12-06 17:08:14,674: DEBUG - Running: LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none aptitude update --quiet=2 -o=Dpkg::Use-Pty=0 -o “APT::Status-Fd=$YNH_STDINFO”
2025-12-06 17:08:16,837: WARNING - W: GPG error: https://packages.gitlab.com/runner/gitlab-runner/debian bookworm InRelease: The following signatures were invalid: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key) packages@gitlab.com
2025-12-06 17:08:16,838: WARNING - E: The repository ‘https://packages.gitlab.com/runner/gitlab-runner/debian bookworm InRelease’ is not signed.
2025-12-06 17:08:16,839: WARNING - E: Failed to download some files
2025-12-06 17:08:16,839: WARNING - W: Failed to fetch https://packages.gitlab.com/runner/gitlab-runner/debian/dists/bookworm/InRelease: The following signatures were invalid: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key) packages@gitlab.com
2025-12-06 17:08:16,840: WARNING - E: Some index files failed to download. They have been ignored, or old ones used instead.
2025-12-06 17:08:17,841: ERROR - Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed to run command ‘aptitude update’
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/yunohost/tools.py”, line 786, in tools_migrations_run
migration.run()
File “/usr/lib/python3/dist-packages/yunohost/migrations/0027_migrate_to_bookworm.py”, line 135, in run
aptitude_with_progress_bar(“update”)
File “/usr/lib/python3/dist-packages/yunohost/utils/system.py”, line 315, in aptitude_with_progress_bar
raise YunohostError(
yunohost.utils.error.YunohostError: Failed to run command ‘aptitude update’

Bonjour @arterrien

Il y a deux sortes de problèmes avec les clés GPG servant à signer les paquets debian

  1. Elles périment et il faut parfois importer de nouvelles clés. avant la debian 12 cela se finissait avec une commande apt-key.
  2. Entre la debian 11 et la debian 12 le système de confiance a changé et repose sur une clé par dépôt plutôt qu’une liste de clé de confiances globale.

Le passage en debian 12 puis 13 implique aussi le choix de nouveaux standards pour les paquets, les anciens formats sont dépréciés.

Il y a de nombreux posts pour ton problème dont stackoverflow https://stackoverflow.com/questions/78204736/gitlab-runner-update-failed-with-gpg-error-signatures-were-invalid le plus adapté semble être Linux package signatures | GitLab Docs

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.