package: mini-buildd version: 1.0.12 severity: normal reprepro 4.17.1-1
The CI on our source control runs sbuild -d sid-hadron-snapshot --arch-all --source . Producing a changes file that includes binaries and sources. If that succeeds in passing some tests, we upload to mini-buildd. I expected it to throw away the binaries and run its own build. As an aside, this is coming from a trusted builder and a trusted chroot; it would be really convenient if there were a way to convince mini-buildd to accept binaries signed by a particular key along with sources. What actually happens is far more annoying. What I know for sure is that if I do a source upload not including the binaries the sources get installed into the repo, but the binaries never do. I tried to debug it. reprepro include is failing, but I don't seem to get the output from reprepro itself in daemon.log. When I unpack the buildresult by hand and run the same reprepro include command, I find that the size, sha-1 and md5 of the .deb are not what is expected. My guess is that the older deb from the initial .changes is getting left in incoming or somewhere where reprepro finds it and because of the rebuild it doesn't match what is expected.
