Ludovic Courtès <l...@gnu.org> writes: > Ricardo Wurmus <rek...@elephly.net> skribis: > >> Ludovic Courtès <l...@gnu.org> writes: > > [...] > >>> With UEFI (almost) ready, Guile 2.2 in the house, and “make release”, >>> should we aim for next week (like Wed. 17th)? Can we focus on polishing >>> the remaining bits and testing? >>> >>> If the schedule turns out to be too tight, we could move to the week >>> after. >> >> I’d like to merge wip-installer, but not start it by default. It would >> be a shame to see the branch bit-rot. > > I agree we shouldn’t let it bitrot. Earlier I suggested postponing it > though, because we wouldn’t have time to test it (nobody is currently > working on it AFAIK): > > https://lists.gnu.org/archive/html/guix-devel/2017-04/msg00491.html > > WDYT?
Okay, let’s merge it some time after the release to be sure that it doesn’t break anything. >> We also need to fix the glibc on hurd (the patch for i686 should not be >> applied there), but I haven’t been able to reproduce the failure on >> hydra. https://hydra.gnu.org/build/2036383/nixlog/1/raw > > Cross-compilation to GNU/Hurd from x86_64-linux-gnu works: > > $ guix build sed --target=i586-pc-gnu > /gnu/store/rd2jngvxbyk5a1yy2ysd0d3wwkbw0pmc-sed-4.4 > > It would be better to fix cross builds from i686 as well. I can take a > look but I wouldn’t consider it a blocker. You don’t need to spend time on this. I didn’t know that it’s a cross build *from* i686 that’s failing. Earlier I didn’t find the right incantation to reproduce that failing build, but now I should be able to figure it out and fix it. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
