Project

General

Profile

Demande #5562

Migrer l'infra en Bullseye

Added by Quentin Gibeaux about 2 months ago. Updated about 1 month ago.

Status:
Nouveau
Priority:
Normale
Assignee:
-
Category:
-
Target version:
Start date:
09/02/2021
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Difficulté:
2 Facile

Description

Debian Bullseye est sorti, il faut migrer l'infra


Subtasks

Demande #5563: Migrer Guarana sur BullseyeNouveau

Actions
Demande #5564: Migrer Galanga sur BullseyeNouveau

Actions
Demande #5565: Migrer Virola sur BullseyeNouveau

Actions
Demande #5566: Migrer Calamus sur BullseyeNouveau

Actions
Demande #5567: Migrer bastion sur BullseyeNouveau

Actions
Demande #5568: Migrer admin sur BullseyeNouveau

Actions
Demande #5569: Migrer dns sur BullseyeNouveau

Actions
Demande #5570: Migrer mail sur BullseyeNouveau

Actions
Demande #5571: Migrer sympa sur BullseyeNouveau

Actions
Demande #5572: Migrer adl sur BullseyeNouveau

Actions
Demande #5573: Migrer lamp sur BullseyeNouveau

Actions
Demande #5574: Migrer agir sur BullseyeNouveau

Actions
Demande #5575: Migrer bots sur BullseyeNouveau

Actions
Demande #5576: Migrer dtc sur BullseyeNouveau

Actions
Demande #5577: Migrer republique-numerique sur BullseyeNouveau

Actions
Demande #5578: Migrer mumble sur BullseyeNouveau

Actions
Demande #5579: Migrer candidatsfr sur BullseyeNouveau

Actions
Demande #5580: Migrer pad sur BullseyeNouveau

Actions
Demande #5581: Migrer scm sur BullseyeNouveau

Actions
Demande #5582: Migrer pouet BullseyeNouveau

Actions
Demande #5583: Migrer spip BullseyeNouveau

Actions
Demande #5589: Générer un nouveau dépot bullseye pour apt.april.orgNouveau

Actions
Demande #5590: Migrer vers Debian Bullseye la vm webchatNouveau

Actions

Related issues

Related to Admins - Demande #3799: Migrer le parc des machines et VM vers Debian BusterFermé07/12/2019

Actions

History

#1

Updated by Christian P. Momon about 2 months ago

  • Related to Demande #3799: Migrer le parc des machines et VM vers Debian Buster added
#2

Updated by Christian P. Momon about 2 months ago

Quelques points relevés dans le fichier de release :

  • https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#security-archive
    5.1.3. Changed security archive layout
    
    For bullseye, the security suite is now named bullseye-security instead of codename/updates
    and users should adapt their APT source-list files accordingly when upgrading.
    
    The security line in your APT configuration may look like:
    
    deb https://deb.debian.org/debian-security bullseye-security main contrib
    
    If your APT configuration also involves pinning or APT::Default-Release, it is likely to require
    adjustments as the codename of the security archive no longer matches that of the regular archive.
    An example of a working APT::Default-Release line for bullseye looks like:
    
    APT::Default-Release "/^bullseye(|-security|-updates)$/";
    
    which takes advantage of the undocumented feature of APT that it supports regular expressions (inside /). 
    
  • https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#ssh-not-available
    5.1.23. No new SSH connections possible during upgrade
    
    Although existing Secure Shell (SSH) connections should continue to work through the upgrade as usual,
    due to unfortunate circumstances the period when new SSH connections cannot be established is longer than usual.
    If the upgrade is being carried out over an SSH connection which might be interrupted, it's recommended
    to upgrade openssh-server before upgrading the full system.
    

Also available in: Atom PDF