This has been patched upstream in reprepro 5.3 but on our repository we're running 5.1 as deployed on bionic. I think that the quickest solution to this wll be to backport 5.3 to bionic. Hopefully the version from the newer systems can just be force installed.
As of buster dpkg is no longer creating Binary fields in changes files. This was debugged in https://github.com/ros-infrastructure/reprepro-updater/issues/73 and we have worked around it in our scripts for https://github.com/ros-infrastructure/reprepro-updater/issues/74
This has been patched upstream in reprepro 5.3 but on our repository we're running 5.1 as deployed on bionic. I think that the quickest solution to this wll be to backport 5.3 to bionic. Hopefully the version from the newer systems can just be force installed.
Research:
I found the change to support this upstream: https://salsa.debian.org/brlink/reprepro/commit/790f48475a6c8380a6a5103b6d21de533240df63
We need 5.3.0 or higher to get it. https://salsa.debian.org/brlink/reprepro/commits/debian
5.1.1 is deployed to Bionic 5.3.0 is deployed to disco https://packages.ubuntu.com/search?keywords=reprepro&searchon=names
Edit: We're still running xenial but it's also on 5.1.1