From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH 4/5] Add new package python3-msgpack Date: Sun, 03 Feb 2019 21:45:21 +0000 Message-ID: <60CBD600-A969-47EE-A883-235BD128500E@ipfire.org> In-Reply-To: <6110f3c4-65e1-bd07-76e0-77f758b6e297@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3313447164123321927==" List-Id: --===============3313447164123321927== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sorry, I overlooked those in Jonatan=E2=80=99s patch. Arne has fixed this next now - I believe. -Michael > On 3 Feb 2019, at 13:19, Matthias Fischer w= rote: >=20 > On 03.02.2019 02:52, Matthias Fischer wrote: >> Hi, >>=20 >> Something weird happened. >>=20 >> While building and packaging current 'next' I ran into an error with >> 'python3-msgpack': >>=20 >> ***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-g= nu.so: >> Cannot stat: No such file or directory >> tar: Exiting with failure status due to previous errors >> make: *** [python3-msgpack:58: dist] Error 2 >> ... >>=20 >> ERROR: Packaging python3-msgpack [ FAIL ] >> Check /home/matz/ipfire-2.x/log/_build.packages.log for errors if >> applicable [ FAIL ] >>=20 >> ***SNAP*** >> ... >=20 > Confirmed with second - clean - build using current 'next', this time > without 'curl 7.63.0'. Identical error. >=20 > Best, > Matthias --===============3313447164123321927==--