I'm thinking that we should add the problem to the errata list,
so that people know about the issue? I have commit access to webwml/english/devel/debian-installer/errata.wml, is writing to it
all it takes to publish an errata item, or is there more coordination
needed?
I'm thinking that we should add the problem to the errata list,
so that people know about the issue? I have commit access to >webwml/english/devel/debian-installer/errata.wml, is writing to it
all it takes to publish an errata item, or is there more coordination
needed?
Yes, that's all there's to do to get the errata updated.
Of course, it might take a few hours until that's noticed by the cron
job
Am 18. August 2021 21:17:57 MESZ schrieb Samuel Thibault <sthibault@debian.org>:
I'm thinking that we should add the problem to the errata list,
so that people know about the issue? I have commit access to >webwml/english/devel/debian-installer/errata.wml, is writing to it
all it takes to publish an errata item, or is there more coordination >needed?
Adding that to ../devel/debian-installer/ is one thing.
What about ../releases/bullseye/debian-installer/ ?
Samuel Thibault <sthibault@debian.org> (2021-08-18):
I'm thinking that we should add the problem to the errata list,
so that people know about the issue? I have commit access to webwml/english/devel/debian-installer/errata.wml, is writing to it
all it takes to publish an errata item, or is there more coordination needed?
Please feel free to document the problem in errata, that looks sane to
me.
Yes, that's all there's to do to get the errata updated. Of course, it
might take a few hours until that's noticed by the cron job that takes
care of updating the website from the webwml repository. I can trigger
a partial rebuild (only the devel/debian-installer part) if you'd like
some earlier confirmation that everything looks good.
The soundcard issue is now in the devel errata, but there is no link
to the errata page from https://www.debian.org/devel/debian-installer/ because it's conditioned "release=buster".
Holger Wansing <hwansing@mailbox.org> (2021-08-23):
The soundcard issue is now in the devel errata, but there is no link
to the errata page from https://www.debian.org/devel/debian-installer/ because it's conditioned "release=buster".
Hopefully that'll get fixed before the first D-I Bookworm Alpha, but
the condition thing is indeed something that need fixing; you might
remember scripts/post-release-checklist.txt, updating release names in
there was the reason for my starting that file. ;)
See f0b21d3c2dfe4f2c6b07737b9953aada7447f8c5 if you'd like to have an example, but it should be about performing both global replacements in
that file (in the right order of course).
Cyril Brulebois <kibi@debian.org> wrote (Mon, 23 Aug 2021 13:01:19 +0200):
Holger Wansing <hwansing@mailbox.org> (2021-08-23):
The soundcard issue is now in the devel errata, but there is no link
to the errata page from https://www.debian.org/devel/debian-installer/ because it's conditioned "release=buster".
Hopefully that'll get fixed before the first D-I Bookworm Alpha, but
the condition thing is indeed something that need fixing; you might remember scripts/post-release-checklist.txt, updating release names in there was the reason for my starting that file. ;)
See f0b21d3c2dfe4f2c6b07737b9953aada7447f8c5 if you'd like to have an example, but it should be about performing both global replacements in
that file (in the right order of course).
Done (for now. I have set bookworm-images-arches in english/template/debian/installer.wml as a copy of bullseye's arches;
will need to be updated if necessary / when these facts are known).
Hi,
Holger Wansing <hwansing@mailbox.org> wrote (Fri, 27 Aug 2021 15:11:34 +0200): >> Cyril Brulebois <kibi@debian.org> wrote (Mon, 23 Aug 2021 13:01:19 +0200): >> > Holger Wansing <hwansing@mailbox.org> (2021-08-23):
The soundcard issue is now in the devel errata, but there is no link
to the errata page from https://www.debian.org/devel/debian-installer/ >> > > because it's conditioned "release=buster".
Hopefully that'll get fixed before the first D-I Bookworm Alpha, but
the condition thing is indeed something that need fixing; you might
remember scripts/post-release-checklist.txt, updating release names in
there was the reason for my starting that file. ;)
See f0b21d3c2dfe4f2c6b07737b9953aada7447f8c5 if you'd like to have an
example, but it should be about performing both global replacements in
that file (in the right order of course).
Done (for now. I have set bookworm-images-arches in
english/template/debian/installer.wml as a copy of bullseye's arches;
will need to be updated if necessary / when these facts are known).
With that being done, we now have the section visible saying
"To install Debian testing, we recommend you use the Bullseye RC 3
release of the installer, after checking its errata. The following
images are available for Bullseye RC 3:
Official release "
... and so on, with the links pointing to bullseye rc3.
But these images are no longer there, so links are all dead.
Is this intended?
Were the links deleted by intend, and I should not have made this section >visible?
I seem to remember, that the images for the latest installer release
were always available ...
I've moved the RC3 images into the "archive" section now that bullseye
is released. We should update that text to point to the maint 11.0
release images instead.
Steve McIntyre <steve@einval.com> (2021-08-28):
I've moved the RC3 images into the "archive" section now that bullseye
is released. We should update that text to point to the maint 11.0
release images instead.
Apparently there was some early attempt at adressing that kind of moment within the release cycle, in comments. But that hadn't been touched
since 2009-2010.
I've tried to address that in the d-i/no-alpha-yet branch, comments
welcome. (The last commit would be reverted when we have an Alpha 1 published. Looking at the if-stable-release implementation, I decided
not to go for a new definition… switching from one commented-out block
to another seems just easier, even if I reckon this might annoy
translators at some point. I won't stop anyone wanting to implement such
a condition — we would probably define a new tag via images.data ;))
I tried similar yesterday already, but could not get it to work.
Today, I copied the mechanism from <if-etchnhalf-released>, and that
way it's fairly easy :-))
Patch attached.
I would prefer such solution, so we don't need to make the
comment-uncomment- dance over and over again... (remember, that
translations need to be synced as well)
I assume there will be no strong objections against this?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 53:37:33 |
| Calls: | 6,650 |
| Calls today: | 2 |
| Files: | 12,200 |
| Messages: | 5,330,494 |