Lately, I have been working towards triggering Debian Unstable builds with Debian OBS packages. As reported before, We can already build packages for both Debian 8 and 9, but while trying to build packages agains Debian unstable I have been reaching the following issue:
OBS scheduler reads the project configuration and starts downloading dependencies. The deendencies get downloaded but the build is never dispatched (the package stays on a "blocked" state). The downloaded dependencies get cleaned up and the scheduler starts the downloads again. OBS enters in an infinite loop there. We traced the issue all the way down to the OBS API call which is triggered when OBS needs to download missing dependenies. For some reason, the number of parameters (number of dependencies to be downloaded) affects the final response of the API call. When trying to download too many packages, The CPIO archive is not built correctly and OBS builds fail. At the moment, we are still investigating why such calls fail with too many params and why it only fails for Debian Testing and Unstable repositories. Here is my blog post with more details on the issue https://athoscr.me/blog/gsoc2018-6/ -- Athos Ribeiro http://www.ime.usp.br/~athoscr
