Hi Justin, On 29-06-2019 12:24, Justin B Rye wrote: > 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.
diff --git a/en/issues.dbk b/en/issues.dbk index cdf71c12..6f56d9d7 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -288,6 +288,32 @@ $ sudo update-initramfs -u </para> </section> + <section id="webkit2gtk-on-non-sse2" arch="i386"> + <title>WebKitGTK (initially) requires SSE2 support</title> + <para> + Due to changes in the upstream code, <systemitem + 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 built into their CPU can't run applications which + use 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. + </para> + <para> + 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. Users of a modern desktop environment with older + (roughly, pre-Pentium IV) CPUs may wish to delay upgrading until then. + It is also intended that the buster-backports archive will receive an + updated package once that archive opens up for uploads, so an alternative + could be to install <systemitem role="package">webkit2gtk</systemitem> + from there once it's available. + </para> + </section> + <section id="noteworthy-obsolete-packages" condition="fixme"> <title>Noteworthy obsolete packages</title> <para>
Description: OpenPGP digital signature