[Backport release-23.11] moonlander: drop

[github-actions]

Bot-based backport to release-23.11, triggered by a label in #270480.

• Before merging, ensure that this backport is acceptable for the release.
  • Even as a non-commiter, if you find that it is not acceptable, leave a comment.

[fabianhjr]

Unsure about this drop @figsoda

[azahi]

This drop is a part of ZHF.

[figsoda]

It's probably better to mark it as broken before completely dropping the package

[azahi]

It's probably better to mark it as broken before completely dropping the package

I'm pretty sure that this package is not used by many, if any users at all. Marking it as broken won't change the fact that it's abandoned upstream and probably won't ever be fixed.

[fabianhjr]

Looking at Hydra

Last successful build 2023-10-21 21:55:31 First broken build 2023-11-16 23:46:21 This build 2023-11-21 15:08:47
Succeededbuild 239073895 Failedbuild 241077856 Failedbuild 241775011

First broken build was 2023-11-16, I think I would defer to figsoda suggestion of marking as broken on 23.11 rather than removal since the removal would normally not be backportable.

[azahi]

Alright, I'm not sure how to proceed here, since the package was already removed in master. Let's say we close this PR, do we need to make another one targeting the release branch and just mark it broken there, ignoring the master?

[fabianhjr]

Yes, another merge request targeting release-23.11 marking as broken.

Will close this one and feel free to ping me to merge the new PR.