On 2/9/2022 3:43 PM, Paul Gevers wrote:
Hi,
Subject: 983357: Why is it not mentioned in bullseye release notes /
installation guide?
For at least the release notes, because nobody asked the editors to
include it.
On 09-02-2022 21:04, Chuck Zmudzinski wrote:
However, this is a well-known problem, but neither the Bullseye release
notes nor the Bullseye installation guide mentions this known problem
that has not yet been fixed.
Is this issue also present after an upgrade? Then, if you have a
proposal for the text to include, we can update the release notes. If
this is *only* influencing the installation the installation guide
might be a better place. Either way, I read the bug, but I don't have
any knowledge on xen, so I feel uncomfortable proposing a text. If it
should go into the release notes, please file a bug against the
release-notes package.
Paul
Thanks, Paul for your quick reply. After looking more carefully at the
way the installation guide and release notes are structured, I think the
best place to alert users to this problem would be by adding it to the
errata for debian-Installer
https://www.debian.org/releases/bullseye/debian-installer/index#errata
page which Chapter 3 of the Bullseye release notes links to.
Then a user could find the problem and workarounds just one click away
from Chapter 3 of the Bullseye release notes.
It looks like to do that I should file an installation bug report with
the debian installer team. The problem as I see it is that the debian
installer team is already aware of the problem and has been aware of it
for over six months because #983357 is marked as affecting d-i. So I do
not understand why #983357 is not included on the d-i bullseye errata page.
Debian installer team. Are you there? Do I need to file another bug in
addition to #983357 to get this problem listed on the bullseye (and also
RC versions) d-i errata pages?
Chuck
