Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:ldc has been trying to migrate for 76 days
[2]. Hence, I am filing this bug. Your package fails to build from
source on armhf and i386 while it successfully built there before.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=ldc

Hi,

ldc is a key package so will not be autoremoved. Is there any progress
on fixing this issue?

Paul

Hi Paul!

Am Sa., 9. Apr. 2022 um 17:30 Uhr schrieb Paul Gevers <elbrus@debian.org>:

I am currently really tid up with other stuff, so I do not have much
time (or actually, any...) to work on Debian's D toolchain, so help is
absolutely wanted here!
However, I hope that this particular issue will just solve itself with
the next LDC release which I'd submit as soon as it is available - at
least this bug report makes me think that LDC 1.29.x will resolve the
issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000919
That new version should actually happen rather soon, so maybe it's
okay to just wait a bit.
Unfortunately I really can't do any deeper investigation into this right now :-/

Cheers,
    Matthias

Hi Matthias,

Thanks for the reply. It a least makes clear where this bug stands.

Paul