[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928882: marked as done (unblock: ghc/8.4.4+dfsg1-3)

Your message dated Tue, 25 Jun 2019 21:44:00 +0200
with message-id <b04f55ad-8006-c087-832a-e35b7bac0c08@debian.org>
and subject line Re: Bug#928882: unblock: [pre-approval] ghc/8.4.4+dfsg1-3
has caused the Debian Bug report #928882,
regarding unblock: ghc/8.4.4+dfsg1-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
928882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928882
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Due to a misconfiguration of ghc, where it uses the 'arm1136jf-s' ARM11
core family on armel, all Haskell packages are currently miscompiled and
will only work on a subset of armel machines (the ones that use the
ARMv6 architecture or newer). This has been reported as #915333.

[#915333] https://bugs.debian.org/915333

In order to fix the above bug for buster, we have to:

1) Upload ghc/8.4.4+dfsg1-3 to unstable with the following fix:

	diff --git a/p/ghc/debian/patches/llvm-arm-unknown-linux-gnueabi.patch b/p/ghc/debian/patches/llvm-arm-unknown-linux-gnueabi.patch
	index 10fe15d0e4..0ac3a43a64 100644
	--- a/p/ghc/debian/patches/llvm-arm-unknown-linux-gnueabi.patch
	+++ b/p/ghc/debian/patches/llvm-arm-unknown-linux-gnueabi.patch
	@@ -8,7 +8,7 @@ Index: b/llvm-targets
	  ,("x86_64-unknown-windows", ("e-m:w-i64:64-f80:128-n8:16:32:64-S128", "x86-64", ""))
	  ,("arm-unknown-linux-gnueabihf", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "arm1176jzf-s", "+strict-align"))
	  ,("armv6-unknown-linux-gnueabihf", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "arm1136jf-s", "+strict-align"))
	-+,("arm-unknown-linux-gnueabi", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "arm1136jf-s", "+strict-align"))
	++,("arm-unknown-linux-gnueabi", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "arm7tdmi", "+soft-float -fp-only-sp -d16 -vfp2 -vfp3 -fp16 -vfp4 -fp-armv8 -neon -crypto +strict-align"))
	  ,("armv6l-unknown-linux-gnueabihf", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "arm1176jzf-s", "+strict-align"))
	  ,("armv7-unknown-linux-gnueabihf", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "generic", ""))
	  ,("armv7a-unknown-linux-gnueabi", ("e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "generic", ""))

2) binNMU on armel, all packages that were built with ghc

3) unblock ghc and binNMU-ed packages

Please note that I do not have the means to verify that the above fix is
working (other than asking the bug reporter to test git-annex after step
2 has been completed), since our armel buildds/porterboxes are based on
ARM v7 (this is why our tests run successfully on buildds and we didn't
catch this earlier).

How should we proceed? Do you think this is something worth fixing
before releasing buster?

-- 
Ilias

--- End Message ---
--- Begin Message --- 
Hi Ilias,

On 25-06-2019 11:17, Ilias Tsitsimpis wrote:
> Could you please unblock ghc/8.4.4+dfsg1-3 as well as every Haskell
> package that was rebuilt on armel? One exception to the above is the
> taffybar package, which has a newer version in unstable than in testing,
> and was on my binNMU list by mistake.

Unblocked, thanks.

> Thankfully, this is a leaf package
> (no other Haskell libraries depend on it) so it is safe to first allow
> all other packages to migrate to testing and then binNMU it directly on
> testing.

Unfortunately, we currently can't binNMU in testing. The package gets
cleaned-up before it hits the archive. Unknown bug somewhere. So
taffybar remains non-functioning on some armel machines until we can
binNMU in stable. Please file an binNMU bug for that.

> Please let me know if there is anything else I can do to help.

It helps if you can check if all the packages that you expect migrate.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: