Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

mmfile.d:147 fails: Could not map file into memmory (Invalid argument) #26

Open
baryluk opened this issue Dec 25, 2022 · 3 comments
Open
Labels
priority: immediate Should be immediately addressed. type: bug Something isn't working.

Comments

@baryluk
Copy link

baryluk commented Dec 25, 2022

Using ISO in qemu.

moss 0.1-2

When trying to install python:

image

I tried installing moss-dbginfo for better stack trace, but it didn't help (and `moss-dbginfo is at different version). I could not find debug package for other dependencies like phobos easily either).

@baryluk
Copy link
Author

baryluk commented Dec 26, 2022

Similar issue with zsh 5.9-1 package.

And ldc 1.30.0-1

And ruby 3.1.3-1 (initially it started install, but then got stuck. ctrl-c, and retry now leads to same issue as above)

python, ldc, ruby all have libffi in common, so maybe it is related

@ermo
Copy link
Member

ermo commented Jan 7, 2023

Here's a solid repro (courtesy @joebonrichie )

Test plan for borky

12345678$ moss remote add protosnek https://dev.serpentos.com/protosnek/x86_64/stone.index -D rootfs/
$ moss remote add volatile https://dev.serpentos.com/volatile/x86_64/stone.index -D rootfs/ -p 10
$ moss it bash dash coreutils systemd grep nss ~/sos/snekpit/main/base/moss/moss-0.1-4-1-x86_64.stone -D rootfs/
$ sudo systemd-nspawn -D rootfs/ -b
$ sudo systemd-nspawn -D rootfs/
# moss it python
# which python3
# moss it python

@ermo ermo added priority: immediate Should be immediately addressed. type: bug Something isn't working. labels Jan 7, 2023
@ikeycode
Copy link
Member

Lack of networking is the root cause - we need to add proper error handling.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: immediate Should be immediately addressed. type: bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

3 participants