[Debian-med-packaging] Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

[Emanuele Rocca]

Hi Mathieu,

On 2024-01-14 11:24, Mathieu Malaterre wrote:
> On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca <ema at debian.org> wrote:
> > We should downgrade the severity to minor once the fix enters unstable, but
> > keep the bug open as this seems to be an interesting case of
> > stack-clash-protection malfunctioning on 32bit arm to further look into.
> 
> Bit lost here... I do not see the bug reported against GCC-13 package.

Sorry for the lack of context. Out of all packages in the archive, a few
(less than 10 it seems, rebuilds still ongoing) fail to build on armhf
or armel with the stack-clash-protection flag on, but build successfully
without it. It's not entirely clear why this is the case yet, but we
know that disabling the flag fixes the issue. For this reason I would
suggest to disable stackclash on the armel build of dcmtk (just like you
did in experimental) to make sure the package builds properly again, but
keep #1060104 open at a lower severity so that we don't lose track of
this.

> In the end do you want me to upload a patched 3.6.7 or is it ok to
> wait for transition ?

Up to you really, no rush on my side.

Thanks,
  Emanuele