unclear release-notes section

[Paul Gevers]

Hi all, Justin,

On IRC there was a remark about our security archive section. It
currently reads:

For bullseye, the security suite is now named
<literal>bullseye-security</literal> instead of
<literal>buster/updates</literal> and users should adapt their
APT source-list files accordingly when upgrading.

The readers were expecting to read bullseye/updates. Several proposals
came up:

1) "as would have been used for previous releases" or something
2) "For bullseye, the security suite is named bullseye-security. This
changed from the previous release which used buster/updates."
3) bullseye/updates.

or leave as-is (best for translations).

It reads fine by me, but I've seen it too often the last couple of days.
What do you think?

Paul

[Justin B Rye]

Post by Paul Gevers
On IRC there was a remark about our security archive section. It
For bullseye, the security suite is now named
<literal>bullseye-security</literal> instead of
<literal>buster/updates</literal> and users should adapt their
APT source-list files accordingly when upgrading.
The readers were expecting to read bullseye/updates. Several proposals
1) "as would have been used for previous releases" or something

Well, buster/updates isn't what *would* have been used, it's what
*was* used, and *other* previous releases used that format but not
that exact string. Maybe

For bullseye, the security suite is named
<literal>bullseye-security</literal> (not
<literal>bullseye/updates</literal>, the format used in
previous releases), and users should adapt their

Post by Paul Gevers
2) "For bullseye, the security suite is named bullseye-security. This
changed from the previous release which used buster/updates."

I'd use "has changed". It might be worth using a "variable" to
emphasise that we're talking about a change in format:

For bullseye, the security suite is named
<literal>bullseye-security</literal>. This is a change from
previous releases which used the format
<literal><replaceable>releasename</replaceable>/updates</literal>."

Post by Paul Gevers
3) bullseye/updates.

For that to work I'd also want to at least drop the "now", to avoid
saying that bullseye formerly used bullseye/updates.

Post by Paul Gevers
or leave as-is (best for translations).
It reads fine by me, but I've seen it too often the last couple of days.
What do you think?

I'm not sure either.

[Justin B Rye]

Second thoughts (and some coffee): changing

<literal>buster/updates</literal>

to

<literal><replaceable>releasename</replaceable>/updates</literal>

ought to be enough, and might be okay for translators. As long as we
don't accidentally use &releasename;.

[Marco Möller]

Post by Justin B Rye

Post by Paul Gevers
On IRC there was a remark about our security archive section. It
For bullseye, the security suite is now named
<literal>bullseye-security</literal> instead of
<literal>buster/updates</literal> and users should adapt their
APT source-list files accordingly when upgrading.
The readers were expecting to read bullseye/updates. Several proposals
1) "as would have been used for previous releases" or something

Well, buster/updates isn't what *would* have been used, it's what
*was* used, and *other* previous releases used that format but not
that exact string. Maybe
For bullseye, the security suite is named
<literal>bullseye-security</literal> (not
<literal>bullseye/updates</literal>, the format used in
previous releases), and users should adapt their

Post by Paul Gevers
2) "For bullseye, the security suite is named bullseye-security. This
changed from the previous release which used buster/updates."

I'd use "has changed". It might be worth using a "variable" to
For bullseye, the security suite is named
<literal>bullseye-security</literal>. This is a change from
previous releases which used the format
<literal><replaceable>releasename</replaceable>/updates</literal>."

Post by Paul Gevers
3) bullseye/updates.

For that to work I'd also want to at least drop the "now", to avoid
saying that bullseye formerly used bullseye/updates.

Post by Paul Gevers
or leave as-is (best for translations).
It reads fine by me, but I've seen it too often the last couple of days.
What do you think?

I'm not sure either.

What's about this version:


For the Debian release "bullseye", the repository providing security
updates is now addressed as <literal>bullseye-security</literal>
The format which was used in the past is no more supported, therefore do
not write <literal>bullseye/updates</literal> anymore.
Users have to adapt...


---
Marco

[Justin B Rye]

For the Debian release "bullseye", the repository providing security updates
is now addressed as <literal>bullseye-security</literal>
The format which was used in the past is no more supported, therefore do not
write <literal>bullseye/updates</literal> anymore.
Users have to adapt...

This changes a lot more than it needs to; undoing that and fixing
up the English a bit I get:

For bullseye, the security suite is now named
<literal>bullseye-security</literal>. The old
<literal><replaceable>releasename</replaceable>/updates</literal>
format is no longer supported, so users should adapt their
APT source-list files accordingly when upgrading.

That's quite good, but I don't know if it's worth the effort.

[Paul Gevers]

Hi,

Post by Marco Möller
For the Debian release "bullseye", the repository providing security
updates is now addressed as <literal>bullseye-security</literal>
The format which was used in the past is no more supported, therefore do
not write <literal>bullseye/updates</literal> anymore.
Users have to adapt...

To be honest, I'll like to stay as close as we can possibly can for the
translators.

I like the idea of Justin to go with releasename/updates.

Paul

[Marco Möller]

Post by Paul Gevers
Hi,

Post by Marco Möller
For the Debian release "bullseye", the repository providing security
updates is now addressed as <literal>bullseye-security</literal>
The format which was used in the past is no more supported, therefore do
not write <literal>bullseye/updates</literal> anymore.
Users have to adapt...

To be honest, I'll like to stay as close as we can possibly can for the
translators.
I like the idea of Justin to go with releasename/updates.
Paul

Good point, the translators, I haven't thought about this.

---
Marco

[Andrei POPESCU]

Post by Paul Gevers
Hi,

Post by Marco Möller
For the Debian release "bullseye", the repository providing security
updates is now addressed as <literal>bullseye-security</literal>
The format which was used in the past is no more supported, therefore do
not write <literal>********/updates</literal> anymore.
Users have to adapt...

To be honest, I'll like to stay as close as we can possibly can for the
translators.
I like the idea of Justin to go with releasename/updates.

It might also help to keep mentions of the unusable string (removed in
the quote above) as limited as possible, e.g. to keep it away from
search engines.

Kind regards,
Andrei