On Thu, Jun 27, 2019 at 03:26:32PM +0300, Adrian Bunk wrote:
> > We like to support non-sse2 on i386, but we are not comfortable
> > fixing webkit2gtk at this stage of the release.
>
> Why is this relatively small change a problem in a package where new
> upstream versions are permitted after
On Thu, Jun 27, 2019 at 01:27:42PM +0200, Paul Gevers wrote:
> reassign 931052 release-notes
> retitle 931052 webkit2gtk not supported on non-sse2 i386 hardware
>...
> We like to support non-sse2 on i386, but we are not comfortable fixing
> webkit2gtk at this stage of the release.
Why is this
On Thu, Jun 27, 2019 at 01:27:42PM +0200, Paul Gevers wrote:
> We like to support non-sse2 on i386, but we are not comfortable
> fixing webkit2gtk at this stage of the release. Therefore, we will
> not unblock this change, but we want the release notes to mention
> this, so users are warned.
Ok,
reassign 931052 release-notes
retitle 931052 webkit2gtk not supported on non-sse2 i386 hardware
user release.debian@packages.debian.org
usertags 931052 - unblock
thanks
Hi Alberto,
On 25-06-2019 10:04, Alberto Garcia wrote:
> Please unblock package webkit2gtk
>
> Upstream WebKitGTK has
On Tue, Jun 25, 2019 at 11:04:59AM +0300, Alberto Garcia wrote:
> This upload disables the JIT compiler and enables the CLoop
> JavaScript interpreter, which is slower but works on all CPUs. It
> also removes the gcc SSE2 flags. Only the i386 build is affected by
> these changes.
I realized that
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package webkit2gtk
Upstream WebKitGTK has recently stopped supporting i386 CPUs without
SSE2 extensions, as other browsers (Chromium, Firefox) already did a
few years ago.
6 matches
Mail list logo
