Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"

[Osamu Aoki <osamu@debian.org>]

Hi,

I favor moving away from pre-dh7 packages and I support people pushing for it.  But I
am in intriguing situation with this effort.  Can someone help me.

At: https://udd.debian.org/cgi-bin/autoremovals.cgi

I see:

Osamu Aoki <osamu@debian.org>
   debian-history: buggy deps xdelta3, flagged for removal in 28.4 days
   debian-reference: buggy deps xdelta3, flagged for removal in 28.4 days
   maint-guide: buggy deps xdelta3, flagged for removal in 28.4 days

These are all COMPAT=13 packages with d/control having:

> Build-Depends: debhelper-compat (= 13)

Thus, it doesn't make sense to be connected to 
> xdelta3: Removal of obsolete debhelper compat 5 and 6 in bookworm
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965883


Also, these packages are not even listed in the original hit list:
https://lists.debian.org/debian-devel/2020/07/msg00065.html


I have been using at least compat=8 since 2013 for 2 of these packages and compat=7
since 2010 for another.  So I can't figure out why these packages are suddenly
flagged.  The last packaging update of debian-history was in 2021 by Bdale Garbee
(not me). So this can't be caused by a silly oversight repeated by a single DD. 

Does any one have idea what is happening?  To whom should I raise issue to avoid
being removed?  Or should I have to fix something?

Regards,

Osamu


FYI: Since all these build PDF files via the TeTex tool chain, the building of these
packages eats a lot of memory even though these have no big programs to build.