Bug#931052: release-notes text proposal for bug 931052: webkit2gtk not supported on non-sse2 i386 hardware

[Justin B Rye <justin.byam.rye@gmail.com>]

Paul Gevers wrote:
> +  <section id="webkit2gtk-on-non-sse2" arch="i386">
> +    <title>Initially no support for WebKitGTK based applications on non-SSE2

       <title>No initial support for WebKitGTK-based applications on non-SSE2

Or maybe just

       <title>WebKitGTK (initially) requires SSE2 support</title>

And how are we deciding when it's "WebKitGTK" and when it's
"webkit2gtk"?  Bear in mind that users have no easy way of mapping
from the name of a source package to the name of the specific library
they might or might not have installed.

> +    systems</title>
> +    <para>
> +      Due to changes in the upstream code, <systemitem
> +      role="package">webkit2gtk</systemitem> has been built with SSE2
> +      support. The changes in the Debian code came too late to be incorporated

Surely the change is that it now *lacks* support for *non*-SSE2
systems?  Or you could say that it has been built with a dependency
on SSE2 support.  Or:

         role="package">webkit2gtk</systemitem> has been built requiring SSE2
         support. Fixes for this in the Debian code came too late to be incorporated

> +      in the initial buster release. This means that systems that don't have
> +      SSE2 support build into their CPU can't run applications which use

s/build/built/

> +      WebKitGTK, e.g. <systemitem role="package">liferea</systemitem> or
> +      <systemitem role="package">zenity</systemitem>. These applications will
> +      crash, most likely with an <literal>Illegal instruction</literal> error
> +      message. It is expected that <systemitem
> +      role="package">webkit2gtk</systemitem> will support these older systems
> +      after the first update of <systemitem
> +      role="package">webkit2gtk</systemitem> in either a point release or
> +      security update.

This is also a bit short on concrete advice for users.  Could we add
something like

        Users of a modern desktop environment with older (roughly,
	pre-Pentium IV) CPUs may wish to delay upgrading until then.

None of my machines are this ancient, but "dpkg -l | grep -i webkit"
gives no output, so I would be safe anyway - right?

> +    </para>
> +  </section>
> +
>    <section id="noteworthy-obsolete-packages" condition="fixme">
>      <title>Noteworthy obsolete packages</title>
>      <para>

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package