Control: severity -1 important
Control: block -1 by 852798
Downgrading severity since armhf binaries were removed in #853296.
Marked as blocked by #852798 in fpc.
Hi,
On 26-01-17 07:25, Graham Inggs wrote:
> I see the same failure with 0.20140804.1~dfsg.1-1.
I expected that.
> According to reproducible builds [1], the last successful build on
> armhf was on 2016-02-19.
That coincides more or less with the upload of fpc 3.0.0 to unstable.
Paul
Weird, I tried various values of kMaxnSLices down to 1500 with no effect.
I was able to work around the problem by moving lScanResX and friends
to global variables, as per the attached patch.
It builds on armhf, but someone familiar should verify program
functionality (on amd64 should be fine).
The patch below adds line number information to the generated parconvert.s:
--- a/dcm2nii/dcm2nii.lpi
+++ b/dcm2nii/dcm2nii.lpi
@@ -482,6 +482,7 @@
+
Because of the additional lines, this changes the assembler messages to:
(9009) Assembling
I see the same failure with 0.20140804.1~dfsg.1-1.
According to reproducible builds [1], the last successful build on
armhf was on 2016-02-19.
Can we request removal of the armhf binary, so this can at least
migrate before the final freeze?
I have some ideas on how to debug this further.
[1]
Source: mricron
Version: 0.20140804.1~dfsg.1-2
Severity: serious
This might be a bug in fpc?
https://buildd.debian.org/status/fetch.php?pkg=mricron=armhf=0.20140804.1~dfsg.1-2=1484442821=0
...
(3104) Compiling parconvert.pas
/«PKGBUILDDIR»/dcm2nii/parconvert.pas(340,40) Hint: (5057) Local
6 matches
Mail list logo
