Re: wesnoth-1.18_1.18.3-1~bpo12+1_source.changes REJECTED

[Vincent Cheng <vcheng@debian.org>]

Hi Micha,

On Fri, Dec 6, 2024 at 11:00 AM Micha Lenk <micha@debian.org> wrote:
>
> Hi Vincent,
>
> On 06.12.24 01:19, Vincent Cheng wrote:
> > In the meantime, would you allow binary uploads of wesnoth-1.18 to
> > backports-NEW to workaround this dak issue? I realize it's not ideal
> > and it's not what the NEW queue is supposed to be used for, but I'm
> > not sure what else I can do here.
>
> You could do that. Yet I wonder whether the current dak database state
> is important for the reproduction of the bug. For this reason I will
> refrain from processing that upload until some of the dak experts
> (that's not me) took a look and had a chance to investigate more detail.
>
> I still hope someone from the FTP maintainers (already looped in
> earlier) will eventually take a look and reply to your mail.

It's been approximately 6 months and source-only backport uploads for
wesnoth-1.18 are still failing as of today [1]. I imagine ftpmasters
are busy with other things so this probably isn't a top priority for
them, but I don't think it's fair to make users wait any longer for an
updated backport due to some weird dak issue that nobody has had time
to look into. This is also likely the last upload I'll make for
wesnoth-1.18 in bookworm-backports given how close we are to trixie.
As such, I've gone ahead and uploaded wesnoth-1.18 as a binary upload
to backports-new, which I'd like to request be accepted, unless you
have an alternative suggestion to get this package updated in
backports. Thanks!

Regards,
Vincent

[1] https://alioth-lists.debian.net/pipermail/pkg-games-devel/2025-June/069230.html