This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kbtbNAMQYkWvBb7479Wux1VSccJzFKdGe
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

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


--kbtbNAMQYkWvBb7479Wux1VSccJzFKdGe--

-----BEGIN PGP SIGNATURE-----

wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmEX/cEFAwAAAAAACgkQnFyZ6wW9dQoq Qwf+OHR+RXHTvlFLdTdFqi6Y60MKcq7ItOq4NGHxxBvzJNlc1TcWVSxloSpTLa5X7i9H5H7h2CMd wrBEGhNLyckzMzsmwAZWZyjiI49dPYVkyp4oBEYmuETp2LcalFYsLDyqce2HHXXXBgzBiGhdfMJN LDiPERzZbT/vo23YMa9yTLXL9vrlxSeffR7KfqECPxdgS6TSRl6vOI51IcxRfm+jxpgJDkUUuLMk uSDf5gwo9lyfgJUzLuz3IojnljMNxOEyA5EpOAFg4SCBk5okEUAXHLQOZhGgUaaiXk7MjA0i821q WGxxL+AP+Dl4hqxYqa+o66kmhB3Sf6Tg6jQEZkQPFg==
=Dfq2
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Paul Gevers wrote:

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

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

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>."

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.

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.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 14.08.21 19:57, Justin B Rye wrote:

Paul Gevers wrote:

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

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

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>."

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Marco Möller wrote:

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.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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;.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 14.08.21 21:10, Paul Gevers wrote:

Hi,

On 14-08-2021 20:41, Marco Möller wrote:

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...

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XF9A4CnnejFEATiwqMaBlDbAZmrAEpD7S
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

On 14-08-2021 20:41, Marco Möller wrote:

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...

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


--XF9A4CnnejFEATiwqMaBlDbAZmrAEpD7S--

-----BEGIN PGP SIGNATURE-----

wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmEYFTQFAwAAAAAACgkQnFyZ6wW9dQo1 6Qf/ZMBazHuaxTTHDL7XomwGMqnzarEDezZJNFeZBJs1SKnXlpk1aipYusZ2bTLB9KrZUx61AHxO yeBW65pz1U+eluDW94tqIwnVCK8CpsaRKx6gGZf07T39GgJG+ZPkpWyeGARsuwKeCyabqGW926He hog/lGLlx1PugWJgzfe4uhDv8OJoKl7fpErHRGoV2IcWM6bB5TqKTOJ1PH2+lFGr3PgKKaAvmZX3 nYUCZ0Non6hZYus9DSvSHvjp7FaY3o4BFmp6EUBmRuotLZ8Dd4ZQr2xm6K/0iDj8uXt/2YwtoKEd ymxiB+teDS9VrpN7ooPWXs/0+WC7f/SIW/CNtt+PFw==
=PCt+
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sb, 14 aug 21, 21:10:44, Paul Gevers wrote:

Hi,

On 14-08-2021 20:41, Marco Möller wrote:

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>********/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
--
http://wiki.debian.org/FAQsFromDebianUser

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE5E64jOIbhY42OXqk/8eFRO8iNBwFAmEZGQkACgkQ/8eFRO8i NBzH+g/+IdgQLDrMvlJqsqAaZ/YSsPuBpse7DTUeq5uF6HWIEtzjJPYk0Jv3lDgt //imsiVRs/gKWKFsqLULTZc0jwUUO6LvO8IlrVt7Pi5GJ/IZ0vPo2w3zIe/SxouF 1HptKZEA+J1ujIZr2JLBCBjtMGtYaqk8pikiI9ZZlltQr0C/Ai4vwS0p0AKp++Bx /n/8grhMYrDWMM3o4C2BI31qjFevQcdkw8cRkEEDNL3LY/4f6U1zGbfZWZiyt4iN dIDyAJ09PTtd8QEy52jC5NaoAvOHu41tAjt9adViouSANC7W7N76Q6rCz32D870A dVMlkU7q4VAxFN5dJdtvG8QXrmr2Eg6gngSwPRo9CUI7tVWNJqwGxbLDSiULQLW4 BmI0naKQY+AfsJzDcuKVymyD5oqjn76mg/caWznV0/peZAB4Kthw3PM412ZLDzXA JMP1cDv+VMaAq/5SA9BSXpXvvkKgW8elLm5gFsUBvDZKACJKohgO+OpVWhOPIT8F 8qaPmUvr7Pk3e7DUSMrMzqoAvsL8apzOF9iHba9GC1Xx+2JP+TX7yd296kceku6i VL9Fz5FQXbAHC9qBw4HxDPWVijnI8+HtCtTrbYt0s7RPOjXpM+Vbl8la8ecFN1Ls yRSWM8ksozUJXH1UMKV15+SZmtJ6zNsKFQnvSw4XxPPrD5GBPIQ=
=fRUs
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)