unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#36754: New linux-libre failed to build on armhf on Berlin
@ 2019-07-21 23:56 Mark H Weaver
  2019-07-22 16:10 ` Ricardo Wurmus
  2019-07-22 17:13 ` Mark H Weaver
  0 siblings, 2 replies; 17+ messages in thread
From: Mark H Weaver @ 2019-07-21 23:56 UTC (permalink / raw)
  To: 36754

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.savannah.gnu.org/cgit/guix.git/commit/?id=1ad9c105c208caa9059924cbfbe4759c8101f6c9

The following queries show that the updated packages built successfully
on x86_64, i686, and aarch64, but they all failed on armhf:

  https://ci.guix.gnu.org/search?query=linux-libre-5.2.2
  https://ci.guix.gnu.org/search?query=linux-libre-4.19.60
  https://ci.guix.gnu.org/search?query=linux-libre-4.14.134
  https://ci.guix.gnu.org/search?query=linux-libre-4.9.186
  https://ci.guix.gnu.org/search?query=linux-libre-4.4.186
  https://ci.guix.gnu.org/search?query=linux-libre-arm-veyron-5.2.2
  https://ci.guix.gnu.org/search?query=linux-libre-arm-generic-5.2.2
  https://ci.guix.gnu.org/search?query=linux-libre-arm-generic-4.19.60
  https://ci.guix.gnu.org/search?query=linux-libre-arm-generic-4.14.134
  https://ci.guix.gnu.org/search?query=linux-libre-arm-omap2plus-5.2.2
  https://ci.guix.gnu.org/search?query=linux-libre-arm-omap2plus-4.19.60
  https://ci.guix.gnu.org/search?query=linux-libre-arm-omap2plus-4.14.134

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

My first guess was that something went wrong in the 'computed' origin
that runs the deblobbing script.  However, that's apparently not the
case, because all of the updated 'linux-libre-headers' packages built
successfully on armhf, and those use the same source tarballs as the
main 'linux-libre' packages.

  https://ci.guix.gnu.org/search?query=linux-libre-headers-5.2.2
  https://ci.guix.gnu.org/search?query=linux-libre-headers-4.19.60
  https://ci.guix.gnu.org/search?query=linux-libre-headers-4.14.134

Can someone help me find out what's going on here?  Until then, I'm
sorry to say that armhf-linux users will be unable to update their
systems.

       Mark

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2019-09-12  8:42 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-07-21 23:56 bug#36754: New linux-libre failed to build on armhf on Berlin Mark H Weaver
2019-07-22 16:10 ` Ricardo Wurmus
2019-07-22 17:13 ` Mark H Weaver
2019-07-23 16:46   ` Marius Bakke
2019-07-23 17:33     ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds (was: New linux-libre failed to build on armhf on Berlin) Mark H Weaver
2019-07-23 17:49       ` Mark H Weaver
2019-07-23 21:26         ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds Ludovic Courtès
2019-07-23 21:55           ` Ricardo Wurmus
2019-08-01 15:39             ` Ricardo Wurmus
2019-07-24 11:09           ` Mark H Weaver
2019-07-24 14:56             ` Ludovic Courtès
2019-08-01 14:09               ` Marius Bakke
2019-08-01 16:37                 ` Mark H Weaver
2019-08-01 21:06                   ` Ricardo Wurmus
2019-08-07 14:30                     ` Ricardo Wurmus
2019-08-16 10:25                       ` Ludovic Courtès
2019-09-12  8:41                         ` Ludovic Courtès

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).