- In the 1.0.7 version of python3-msgpack there is one filename that has been introduced in the rootfile that has an architecture specific name. This did not get flagged up by the IPFire build process so I missed it. - I noticed it from the aarch64 nightly build of next continually failing at the package installation section of python3-msgpack because it could not find that file which was labelled in the original patch submission explicitly with the x86_64 name. - This patch corrects that, replacing the x86_64 with xxxMACHINExxx and bumping the PAK VER for this package.

Signed-off-by: Adolf Belka adolf.belka@ipfire.org --- config/rootfiles/packages/python3-msgpack | 2 +- lfs/python3-msgpack | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/config/rootfiles/packages/python3-msgpack b/config/rootfiles/packages/python3-msgpack index 2347b0834..e5742ddb9 100644 --- a/config/rootfiles/packages/python3-msgpack +++ b/config/rootfiles/packages/python3-msgpack @@ -6,7 +6,7 @@ usr/lib/python3.10/site-packages/msgpack #usr/lib/python3.10/site-packages/msgpack-1.0.7-py3.10.egg-info/top_level.txt usr/lib/python3.10/site-packages/msgpack/__init__.py usr/lib/python3.10/site-packages/msgpack/_cmsgpack.cpp -usr/lib/python3.10/site-packages/msgpack/_cmsgpack.cpython-310-x86_64-linux-gnu.so +usr/lib/python3.10/site-packages/msgpack/_cmsgpack.cpython-310-xxxMACHINExxx-linux-gnu.so usr/lib/python3.10/site-packages/msgpack/_cmsgpack.pyx usr/lib/python3.10/site-packages/msgpack/_packer.pyx usr/lib/python3.10/site-packages/msgpack/_unpacker.pyx diff --git a/lfs/python3-msgpack b/lfs/python3-msgpack index f09edd3e8..1179678fc 100644 --- a/lfs/python3-msgpack +++ b/lfs/python3-msgpack @@ -33,7 +33,7 @@ DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) PROG = python3-msgpack -PAK_VER = 4 +PAK_VER = 5

DEPS = # borgbackup only works with specific versions of python3-msgpack - check when updating