public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 4/5] Add new package python3-msgpack
Date: Mon, 04 Feb 2019 18:23:03 +0100	[thread overview]
Message-ID: <8177e238-f045-f322-b9a9-64b37560e6b9@ipfire.org> (raw)
In-Reply-To: <60CBD600-A969-47EE-A883-235BD128500E@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]

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 <matthias.fischer(a)ipfire.org> 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
> 
> 

  reply	other threads:[~2019-02-04 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 11:52 [PATCH 1/5] Add new package python3-settuptools Jonatan Schlag
2019-02-01 11:52 ` [PATCH 2/5] Add new package python3-setuptools-scm Jonatan Schlag
2019-02-01 11:52 ` [PATCH 3/5] Add new package python3-llfuse Jonatan Schlag
2019-02-01 11:52 ` [PATCH 4/5] Add new package python3-msgpack Jonatan Schlag
2019-02-03  1:52   ` Matthias Fischer
2019-02-03 13:19     ` Matthias Fischer
2019-02-03 21:45       ` Michael Tremer
2019-02-04 17:23         ` Matthias Fischer [this message]
2019-02-04 22:44           ` Michael Tremer
2019-02-01 11:52 ` [PATCH 5/5] Add new package borgbackup Jonatan Schlag
2019-02-01 16:32 ` [PATCH 1/5] Add new package python3-settuptools Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8177e238-f045-f322-b9a9-64b37560e6b9@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox