astroquery: please RM from oracular

[Graham Inggs]

astroquery's autopkgtest currently prevents astropy from migrating.

astroquery FTBFS and was removed from Debian testing on 2024-01-20.

$ reverse-depends src:astroquery
Reverse-Recommends
==================
* astro-python3 (for python3-astroquery)
* python3-astropy-affiliated (for python3-astroquery)
* python3-astropy-coordinated (for python3-astroquery)

Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x

$ reverse-depends -b src:astroquery
No reverse dependencies found

[Christian Ehrhardt  (paelzer)]

Ack on FTBFS [1] and being removed from Testing.

Since there is no way it can resolve without a new upload and at the same time blocks other things from migrating I think removing is better than pushing it back to -proposed.

Dependencies indeed are "only" recommends which do not block the removal and in this case seem not right to e.g. modify the depending packages. Instead the problem of astroquery/astropy_helpers not being python 3.12 compatible needs to be fixed and that is known and tracked in Debian already.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057543
[2]: https://tracker.debian.org/news/1496364/astroquery-removed-from-testing/

[Christian Ehrhardt  (paelzer)]

Nothing in proposed

rmadison -u ubuntu -s oracular,oracular-proposed astroquery
 astroquery | 0.4.6+dfsg-4 | oracular/universe | source

Yet the main reason to for this to be a removal is that it also blocks astropy.
But that migrated or was cancelled

rmadison -u ubuntu -s oracular,oracular-proposed astropy
 astropy | 6.1.2-1 | oracular/universe | source

python3.12 compat in astroquery was fixed a while ago
- https://github.com/astropy/astroquery/pull/2838
And released
- https://github.com/astropy/astroquery/releases/tag/v0.4.7

And it seems the work on that goes on:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058104

Expecting it to drop needing python3-astropy-helpers and a removal of that once ready.

I hope I understood the case correctly.
By no more blocking others, but being FTBFS (yet with a fix known) I think a removal is too much, but demotion to -proposed seems justifiable.

But even that might be too much since the fix is known for the only problem being e.g. serving the package later and then an FTBFS is fatal. But since there exists a solution (although not yet packaged) it seems it can stay.

TBH, I'm torn on the decision of "do nothing" or "demote to proposed".
I'd say no to a removal right now.

To not clean overzealous I'll mark it Won't Fix and I'm happy to be contacted and convincecd otherwise

[Ole Streicher (olebole)]

I am about to upload a fixed version of astroquery to Debian unstable; this should help to fix this w/o removing.

[Christian Ehrhardt  (paelzer)]

I see https://launchpad.net/ubuntu/+source/astroquery/0.4.7+dfsg-1
Which migrated just fine.

None of the astro* left in excuses.

\o/

Thank you so much @Ole!