FTBFS on all recent uploads

[Vagrant Cascadian]

On 2023-06-22, Boyuan Yang wrote:
> 在 2023-06-20星期二的 06:31 +0200，Joachim Zobel写道：
>> I have a FTBFS on all uploads after the end of the freeze. Example:
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gap-aclib.html
>> 
>> All these packages had been changed to compat 13. Unfortunately I have
>> no idea why I get these. I can see two logs of successful builds and a
>> diff for them. At the end of each log I find reproducible ➤ FTBFS, so
>> this probably is because my build fails to be reproducible. However the
>> only diff I see is the diff between the build logs. 
>> 
>> Any hints on what to do about these would be helpful.
>
> In the link above, when clicking "build2" under amd64 1.3.2-3--build2, the log
> shows that the build machine raised an error before your source code
> actually got built. It might be a machine configuration error. Forwarding
> your email to Debian reproducible-builds mailing list since they may know
> more about it.

We had a few glitches after the bookworm released, but I *think* they
should be sorted out by now...

FTBFS do get rescheduled fairly often, and if you really need, they can
be manually rescheduled (if you are a debian developer, you should be
able to click on the triangle of arrows to reschedule).

live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20230622/0e0e5510/attachment.sig>