I've reached out to Dimitri recently to get some more information about the build and run time dependencies.
I think there are a couple of options.
1. Pursue dropping python-requests from debian/control for build dependencies.
*Note I think just the testing would be broken, but at least mongodb would be usable and in a workable state. (quick fix/low effort)
2. Upgrade everything from Python2 to Python3. Which is probably the best option for long-term maintenance. (medium effort)
3. Sergio's 2nd option -
- Reintroduce python-requests to the archive. While this would guarantee that mongodb (and possibly other packages that B-D on python-requests) builds fine, it would also mean going through a more extensive SRU process, I think.
(I don't have a good estimate on how long this would take)
I've reached out to Dimitri recently to get some more information about the build and run time dependencies.
I think there are a couple of options.
1. Pursue dropping python-requests from debian/control for build dependencies.
*Note I think just the testing would be broken, but at least mongodb would be usable and in a workable state. (quick fix/low effort)
2. Upgrade everything from Python2 to Python3. Which is probably the best option for long-term maintenance. (medium effort)
3. Sergio's 2nd option -
- Reintroduce python-requests to the archive. While this would guarantee that mongodb (and possibly other packages that B-D on python-requests) builds fine, it would also mean going through a more extensive SRU process, I think.
(I don't have a good estimate on how long this would take)
Thanks,
Heather Lemon