Public SourceMage Discussion List

[Thomas Orgis <thomas-forum AT orgis.org>]

Hi,

I'm trying to use the linux spell (from stable grimoire and git) for
once and I am stumbling over it's $SOURCE2 being broken:

bash$ gaze sources linux
linux-4.7.tar.xz
linux-4.7.tar.xz.sign


It should be linux-4.7.tar.sign instead. Compare

bash$ gaze sources glibc
glibc-2.24.tar.xz
glibc-2.24.tar.xz.sig
linux-4.7.tar.xz
linux-4.7.tar.sign


Now, is there someone who understands the dungeon of complexity that is
the linux spell? A bit of context may be useful: For a short time, I
had a linux spell that worked, then it switched to wanting the
tar.xz.sign . This was on an Atom netbook that I installed using the
old 0.9.6.3 ISO, as I didn't see any other viable installation source
for a 32 bit system.

This system has a rather old stable grimoire as base. My first task was
to install a new kernel so that the network works (rtl8187se …
transferring sources via sneakernet until then), then I wanted to bring
it to current stable. Some activity (I deleted some irrelevant stuff
about aborted casts):

Initial installation from ISO.

20160813:1955(+0000)    summon  linux   2.6.19.5        success 
20160813:1955(+0000)    cast    linux   2.6.19.5        start   
20160813:1956(+0000)    cast    linux   2.6.19.5        success 

Noticed that new kernel needs bc.

20160813:2051(+0000)    summon  bc      1.06    success 
20160813:2051(+0000)    cast    bc      1.06    start   
20160813:2051(+0000)    cast    bc      1.06    success 

Wanting to cast new kernel.

20160813:2055(+0000)    summon  linux   3.19.3  success 
20160813:2055(+0000)    cast    linux   3.19.3  start   
20160813:2055(+0000)    cast    linux   3.19.3  failure pre_build

Breakage with tar.xz extraction.

20160813:2108(+0000)    summon  xz-utils        5.2.0   success 
20160813:2108(+0000)    cast    xz-utils        5.2.0   start   
20160813:2111(+0000)    cast    xz-utils        5.2.0   success 

New basesystem has that … not the old one.

20160813:2112(+0000)    summon  linux   3.19.3  success 
20160813:2112(+0000)    cast    linux   3.19.3  start   
20160813:2114(+0000)    cast    linux   3.19.3  failure build

I got trouble with the linux spell menus, switching versions around,
trying to make it use the old tree, but that doesn't count until a
build was successful.

20160813:2123(+0000)    summon  linux           failure download failed
20160813:2123(+0000)    cast    linux           failure because it was 
missing source: .sign
20160813:2124(+0000)    summon  linux   3.19.3  success 
20160813:2124(+0000)    cast    linux   3.19.3  start   
20160813:2133(+0000)    summon  linux   3.19.3  success 
20160813:2133(+0000)    cast    linux   3.19.3  start   
20160813:2154(+0000)    cast    linux   3.19.3  failure build

Now linux told me that it won't build with the old gcc 4.1 . So, trying
to get gcc 4.6 built.

20160813:2206(+0000)    summon  gmp     4.3.2   success 
20160813:2206(+0000)    cast    gmp     4.3.2   start   
20160813:2206(+0000)    summon  autoconf        2.69    success 
20160813:2206(+0000)    summon  automake        1.14.1  success 
20160813:2206(+0000)    summon  mpfr    3.1.2   success 
20160813:2206(+0000)    summon  libmpc  1.0.2   success 
20160813:2206(+0000)    summon  gcc     4.6.4   failure download failed
20160813:2206(+0000)    summon  g++     4.6.1   success 
20160813:2214(+0000)    cast    gmp     4.3.2   success 
20160813:2214(+0000)    cast    autoconf        2.69    start   
20160813:2216(+0000)    cast    autoconf        2.69    success 
20160813:2217(+0000)    cast    automake        1.14.1  start   
20160813:2217(+0000)    cast    automake        1.14.1  failure build
20160813:2217(+0000)    cast    mpfr    3.1.2   start   

Automake found no ./configure since extraction of the tar.xz silently
failed, mpfr doesn't know what to patch and hangs in PRE_BUILD because
tar.xz extraction silently failed.

I though about what could be broken here … tried to update tar.

20160813:2225(+0000)    summon  tar     1.16.1  failure download failed
20160813:2225(+0000)    cast    tar     1.16.1  failure because it was 
missing source: tar-1.16.1.tar.bz2
20160813:2225(+0000)    summon  tar     1.28    success 
20160813:2225(+0000)    cast    tar     1.28    start   
20160813:2225(+0000)    cast    tar     1.28    failure build

Oh, right. My bad. Tar of course comes as a tar.xz nowadays … but lynx
and I had the same idea shortly after:

20160813:2326(+0000)    summon  file    5.23    success 
20160813:2326(+0000)    cast    file    5.23    start   
20160813:2327(+0000)    dispel  file    4.19    success 
20160813:2327(+0000)    cast    file    5.23    success

With the updated file, sorcery is able to detect tar.xz and handle it
properly, also with old tar. But, where was I? Ah, updating gcc for linux.
        
20160813:2328(+0000)    cast    mpfr    3.1.2   failure pre_build

That was the old PRE_BUILD that I finally cancelled in another terminal.

20160813:2328(+0000)    summon  automake        1.14.1  success 
20160813:2328(+0000)    summon  mpfr    3.1.2   success 
20160813:2328(+0000)    summon  libmpc  1.0.2   success 
20160813:2328(+0000)    summon  gcc     4.6.4   failure download failed
20160813:2328(+0000)    resurrect       gmp     4.3.2   success 
20160813:2328(+0000)    summon  g++     4.6.1   success 
20160813:2328(+0000)    cast    automake        1.14.1  start   
20160813:2328(+0000)    cast    automake        1.14.1  success 
20160813:2328(+0000)    cast    mpfr    3.1.2   start   
20160813:2331(+0000)    cast    mpfr    3.1.2   success 
20160813:2331(+0000)    cast    libmpc  1.0.2   start   
20160813:2334(+0000)    cast    libmpc  1.0.2   success 
20160813:2334(+0000)    cast    gcc     4.6.4   failure because it was 
missing source: gcc-core-4.6.4.tar.bz2.sig
20160814:0006(+0000)    summon  gcc     4.6.4   success 
20160814:0006(+0000)    summon  g++     4.6.1   success 
20160814:0007(+0000)    dispel  g++     4.1.1   success 
20160814:0007(+0000)    cast    gcc     4.6.4   start   
20160814:0220(+0000)    dispel  gcc     4.1.1   success 
20160814:0221(+0000)    cast    gcc     4.6.4   success 
20160814:0222(+0000)    cast    g++     4.6.1   start   
20160814:0222(+0000)    cast    g++     4.6.1   success 

Finally, after some running around for the forgotten .sig, I got a
shiny new gcc version 4.6.4.

20160814:1102(+0000)    summon  linux   2.6.39.4        success 
20160814:1102(+0000)    cast    linux   2.6.39.4        start   

Oh, eh … again confused with the linux spell and its menus. I wanted
3.19.

20160814:1104(+0000)    summon  linux   3.19    failure download failed
20160814:1104(+0000)    cast    linux   3.19    failure because it was 
missing source: linux-3.19.tar.xz.sign
20160814:1105(+0000)    summon  linux   3.19    failure download failed
20160814:1105(+0000)    cast    linux   3.19    failure because it was 
missing source: linux-3.19.tar.xz.sign
20160814:1108(+0000)    summon  linux   3.19    failure download failed
20160814:1108(+0000)    cast    linux   3.19    failure because it was 
missing source: linux-3.19.tar.xz.sign
20160814:1109(+0000)    summon  linux   3.19    failure download failed
20160814:1109(+0000)    cast    linux   3.19    failure because it was 
missing source: linux-3.19.tar.xz.sign

Boom. That summon worked before! Eh wait … not exactly. For some reason
the .3 patch got dropped. I selected it in the menu! Meh … but the
thing is that the summon worked before, with tar.sign instead of
tar.xz.sign.

I've seen an error of grep _after_ the summon attempt … about
--exclude-dir not being supported. But an update of grep …

20160814:1118(+0000)    summon  grep    2.22    success 
20160814:1118(+0000)    cast    grep    2.22    start   
20160814:1119(+0000)    cast    grep    2.22    failure build

… fails with funky header issues. Seems like it's incompatible with the
glibc on this system.

That's it so far … any ideas about the linux spell's sources breakage?
I tried casting glibc from current stable, but that also tried to get
linux-2.6.<something>.tar.bz2.sign for headers … which also doesn't
exist. This doesn't seem to happen for 3.x or at least 4.x kernel headers.

Hints?


Alrighty then,

Thomas

Attachment: pgphLbNpRaYvI.pgp
Description: Digitale Signatur von OpenPGP