Hi, On 03.02.2019 22:45, Michael Tremer wrote: > Sorry, I overlooked those in Jonatan’s patch. > > Arne has fixed this next now - I believe. Sorry, that didn't help. Tonight I made a third test build containing your fix: same error as below. Contents of /build/usr/lib/python3.6/site-packages/msgpack/: ... root(a)Devel: /home/matz/ipfire-2.x/build/usr/lib/python3.6/site-packages/msgpack # ls -l total 292 -rw-r--r-- 1 root root 1056 Jul 30 2016 exceptions.py -rw-r--r-- 1 root root 35973 Mar 10 2018 fallback.py -rw-r--r-- 1 root root 1605 Mar 10 2018 __init__.py -rwxr-xr-x 1 root root 108124 Feb 4 01:56 _packer.cpython-36m-i386-linux-gnu.so drwxr-xr-x 2 root root 4096 Feb 4 01:29 __pycache__ -rwxr-xr-x 1 root root 134828 Feb 4 01:56 _unpacker.cpython-36m-i386-linux-gnu.so -rw-r--r-- 1 root root 20 Mar 10 2018 _version.py ... Something I can do? Best, Matthias > -Michael > >> On 3 Feb 2019, at 13:19, Matthias Fischer wrote: >> >> On 03.02.2019 02:52, Matthias Fischer wrote: >>> Hi, >>> >>> Something weird happened. >>> >>> While building and packaging current 'next' I ran into an error with >>> 'python3-msgpack': >>> >>> ***SNIP*** >>> ... >>> '/usr/src/config/rootfiles/packages//python3-msgpack' -> >>> '/install/packages/package/ROOTFILES' >>> tar: >>> usr/lib/python3.6/site-packages/msgpack/_packer.cpython-36m-i586-linux-gnu.so: >>> Cannot stat: No such file or directory >>> tar: >>> usr/lib/python3.6/site-packages/msgpack/_unpacker.cpython-36m-i586-linux-gnu.so: >>> Cannot stat: No such file or directory >>> tar: Exiting with failure status due to previous errors >>> make: *** [python3-msgpack:58: dist] Error 2 >>> ... >>> >>> ERROR: Packaging python3-msgpack [ FAIL ] >>> Check /home/matz/ipfire-2.x/log/_build.packages.log for errors if >>> applicable [ FAIL ] >>> >>> ***SNAP*** >>> ... >> >> Confirmed with second - clean - build using current 'next', this time >> without 'curl 7.63.0'. Identical error. >> >> Best, >> Matthias > >