public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pveceph/package-repos: adapt further to new deb822 format
Date: Wed, 16 Jul 2025 16:57:02 +0200	[thread overview]
Message-ID: <20250716145702.315217-1-s.sterz@proxmox.com> (raw)

fixes up some outdated uses of the old package repositories and adds a
bit more explanation for users trying to install the firmware package

Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
 pve-package-repos.adoc | 12 ++++++++++--
 pveceph.adoc           |  2 +-
 2 files changed, 11 insertions(+), 3 deletions(-)

diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc
index 18348f6..063bc6f 100644
--- a/pve-package-repos.adoc
+++ b/pve-package-repos.adoc
@@ -147,8 +147,8 @@ addition to a {pve} Proxmox repository
 ~~~~~~~~~~~~~~~~~~~~~~
 
 This repository contains the latest packages and is primarily used by developers
-to test new features. To configure it, add the following line to
-`/etc/apt/sources.list`:
+to test new features. To configure it, add the following stanza to the file
+`/etc/apt/sources.list.d/proxmox.sources`:
 
 .File `/etc/apt/sources.list.d/proxmox.sources`
 ----
@@ -244,6 +244,14 @@ To be able to install packages from this component, run
 `editor /etc/apt/sources.list`, append `non-free-firmware` to the end of each
 `.debian.org` repository line and run `apt update`.
 
+If you upgraded your {pve} 9 install from a previous version of {pve} and have
+modernized your package repositories to the new deb822-style, you will need to
+adapt `/etc/apt/sources.list.d/debian.sources` instead. Run `editor
+/etc/apt/sources.list.d/debian.sources` and add `non-free-firmware` to the lines
+starting with `Components:` of each stanza.
+
+NOTE: Modernizing your package repositories is recommended. Otherwise, `apt` on
+Debian Trixie will complain. You can run `apt modernize-sources` to do so.
 
 [[repos_secure_apt]]
 
diff --git a/pveceph.adoc b/pveceph.adoc
index 79aa045..9e71964 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -302,7 +302,7 @@ pveceph install
 ----
 
 This sets up an `apt` package repository in
-`/etc/apt/sources.list.d/ceph.list` and installs the required software.
+`/etc/apt/sources.list.d/ceph.sources` and installs the required software.
 
 
 Initial Ceph configuration via CLI
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2025-07-16 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 14:57 Shannon Sterz [this message]
2025-07-16 15:16 ` [pve-devel] applied: " Thomas Lamprecht

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=20250716145702.315217-1-s.sterz@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal