bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-23 Thread Marius Bakke
Mark H Weaver writes: > Hi Ricardo, > > Interesting. I distinctly remember that there was no log file when I > looked last time. Hmm. > > Anyway, it seems that now, all of the failed builds have either build > logs available or else information about which dependency failed. I > don't remember

bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-22 Thread Mark H Weaver
Hi Ricardo, Interesting. I distinctly remember that there was no log file when I looked last time. Hmm. Anyway, it seems that now, all of the failed builds have either build logs available or else information about which dependency failed. I don't remember seeing any of this last time, but I'm

bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-22 Thread Ricardo Wurmus
Mark H Weaver writes: > Unfortunately, I'm unable to get *any* information about what went wrong > from Cuirass. None of the failed builds have associated log files, and > the build details page has no useful information either. For example: > > https://ci.guix.gnu.org/build/1488517/details

bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-21 Thread Mark H Weaver
In commit 1ad9c105c208caa9059924cbfbe4759c8101f6c9, I changed our linux-libre packages to deblob the linux-libre source tarballs ourselves, i.e. to run the deblobbing scripts provided by the linux-libre project to produce linux-libre source tarballs from the upstream linux tarballs: https://git