xz missing from build container?

[baerbock]

Is it possible, that the xz command is missing from build container?

Step 52/62 : RUN wget -qO- http://download.qt.io/official_releases/qt/5.11/5.11.3/single/qt-everywhere-src-5.11.3.tar.xz | tar xJ && 	patch -d ~/qt-everywhere-src-5.11.3 -p0 < ~/qt.musl.patch && 	wget -qO- https://raw.githubusercontent.com/gentoo/libressl/master/dev-qt/qtnetwork/files/qtnetwork-5.11.3-libressl-2.8.patch | patch -d ~/qt-everywhere-src-5.11.3/qtbase -p1 && 	mv ~/config.opt ~/qt-everywhere-src-5.11.3 && 	cd ~/qt-everywhere-src-5.11.3 && ./configure -redo && make -j4 -Oline && make -j4 install && 	cd ~ && rm -r ~/qt-everywhere-src-5.11.3 && 	export PATH=/home/kdedev/qt-everywhere-5.11.3/bin:$PATH && 	wget -qO- http://download.qt.io/snapshots/ci/qtwebkit/5.212/1515668564/src/submodules/qtwebkit-everywhere-src-5.212.tar.xz | tar xJ && 	cd qtwebkit-everywhere-src-5.212 &&     cmake -DPORT=Qt -DCMAKE_BUILD_TYPE=Release -DQt5_DIR=/home/kdedev/qt-everywhere-5.11.3 -DCMAKE_PREFIX_PATH=/home/kdedev/qt-everywhere-5.11.3/lib/cmake -DCMAKE_INSTALL_PREFIX=/home/kdedev/qt-everywhere-5.11.3 -DENABLE_SAMPLING_PROFILER=0 -DUSE_THIN_ARCHIVES=OFF &&     make -j4 && make -j4 install &&     cd ~ && rm -r ~/qtwebkit-everywhere-src-5.212 && 	wget -qO- https://gitlab.com/accounts-sso/libaccounts-qt/-/archive/master/libaccounts-qt-master.tar.gz | tar xz &&	cd ~/libaccounts-qt-master &&     patch -p0 < /home/kdedev/libaccounts.patch &&     qmake PREFIX=/home/kdedev/qt-everywhere-5.11.3 &&     make -j4 -Oline && make -j4 install &&     cd ~ && rm -r ~/libaccounts-qt-master && 	wget -qO- https://gitlab.com/accounts-sso/signond/-/archive/master/signond-master.tar.gz | tar xz && 	cd ~/signond-master &&     patch -p0 < /home/kdedev/signon.patch &&     qmake PREFIX=/home/kdedev/qt-everywhere-5.11.3 &&     make -j4 -Oline && make -j4 install &&     cd ~ && rm -r ~/signond-master
 ---> Running in 3545c6dba264
**xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now**
The command '/bin/sh -c wget -qO- http://download.qt.io/official_releases/qt/5.11/5.11.3/single/qt-everywhere-src-5.11.3.tar.xz | tar xJ && 	patch -d ~/qt-everywhere-src-5.11.3 -p0 < ~/qt.musl.patch && 	wget -qO- https://raw.githubusercontent.com/gentoo/libressl/master/dev-qt/qtnetwork/files/qtnetwork-5.11.3-libressl-2.8.patch | patch -d ~/qt-everywhere-src-5.11.3/qtbase -p1 && 	mv ~/config.opt ~/qt-everywhere-src-5.11.3 && 	cd ~/qt-everywhere-src-5.11.3 && ./configure -redo && make -j4 -Oline && make -j4 install && 	cd ~ && rm -r ~/qt-everywhere-src-5.11.3 && 	export PATH=/home/kdedev/qt-everywhere-5.11.3/bin:$PATH && 	wget -qO- http://download.qt.io/snapshots/ci/qtwebkit/5.212/1515668564/src/submodules/qtwebkit-everywhere-src-5.212.tar.xz | tar xJ && 	cd qtwebkit-everywhere-src-5.212 &&     cmake -DPORT=Qt -DCMAKE_BUILD_TYPE=Release -DQt5_DIR=/home/kdedev/qt-everywhere-5.11.3 -DCMAKE_PREFIX_PATH=/home/kdedev/qt-everywhere-5.11.3/lib/cmake -DCMAKE_INSTALL_PREFIX=/home/kdedev/qt-everywhere-5.11.3 -DENABLE_SAMPLING_PROFILER=0 -DUSE_THIN_ARCHIVES=OFF &&     make -j4 && make -j4 install &&     cd ~ && rm -r ~/qtwebkit-everywhere-src-5.212 && 	wget -qO- https://gitlab.com/accounts-sso/libaccounts-qt/-/archive/master/libaccounts-qt-master.tar.gz | tar xz &&	cd ~/libaccounts-qt-master &&     patch -p0 < /home/kdedev/libaccounts.patch &&     qmake PREFIX=/home/kdedev/qt-everywhere-5.11.3 &&     make -j4 -Oline && make -j4 install &&     cd ~ && rm -r ~/libaccounts-qt-master && 	wget -qO- https://gitlab.com/accounts-sso/signond/-/archive/master/signond-master.tar.gz | tar xz && 	cd ~/signond-master &&     patch -p0 < /home/kdedev/signon.patch &&     qmake PREFIX=/home/kdedev/qt-everywhere-5.11.3 &&     make -j4 -Oline && make -j4 install &&     cd ~ && rm -r ~/signond-master' returned a non-zero code: 2

[jschultz]

I don't know. You know how to take a look inside?

docker exec --rm -it xxxxxxxxxxxxxxxxxxxx sh

where xxxxxxxxxxxxxxxxxxxxxx is the SHA256 code of the image layer, (after the ---->) in the build log.

I'm actually surprised your build got that far. I tried it again lately and it fell over building libgpg-error. The problem is that the patches I made to the voidlinux build scripts aren't all compatible with the current release. I'm trying to get some answers from the voidlinux community about archives of their repositories. Until I can sort that issue out it's probably not worth spending time on this.

[baerbock]

@jschultz May I support your issue at the voidlinux community? Which patch exactly is now incompatible?

[jschultz]

The problem is that voidlinux doesn't archive old package versions. I asked a question about it here. I'm not convinced that the space requirements would be all that onerous but I need to do some calculations first. In any case it would require someone to organise so it's not going to happen any time soon.

Anyway I merged my changes into the upstream voidlinux yesterday and that much of it works now.

Other problems relate to Qt. At least they archive old releases but now it seems that version 5.11.3 no longer compiles. I've updated to use Qt 5.12.4 and it's building right now. Let's see how far it gets...