cryptoadvance / cryptoadvance/specter-desktop
Clarifying glibc support for version2
- Dominant language
- Python
- Stars
- 847
- Forks
- 259
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 2
Description
So we have a kind of unstructured dependency conflict.
```
2023-02-01T08:21:19.988Z [info] : Starting specterd /k9ert/.specter/specterd-binaries/specterd server,--no-filelog,--devstatus-threshold,alpha,--specter-data-folder,~/.specter_mainchain
2023-02-01T08:21:20.755Z [info] : stderr-[3020617] Error loading Python lib '/tmp/_MEIgwVmZY/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIgwVmZY/libpython3.10.so.1.0)
```
It's #373 reappearing.
We're using the [registry.gitlab.com/cryptoadvance/specter-desktop/electron-builder:latest](https://github.com/cryptoadvance/specter-desktop/tree/master/docker/electron-builder) to build the Appimages for Linux and windows. As we're doing both in one go, the underlying image is `electronuserland/builder:wine` (and we install python on top). `electronuserland/builder:wine` is in turn based on `electronuserland/builder:node` which in turn is based in `electronuserland/builder:base`.
So to check the different glibc-versions for `registry.gitlab.com/cryptoadvance/specter-desktop/electron-builder`:
| tag | glibc | comment |
| 202301.31 | 2.31 | found a 1 year old version on my disk which i simply uploaded with this tag just to have some backup |
| latest | 2.35 | created anew on 31.Jan 23 |
So now we need to migrate to python 3.10. How do we do that?
# Status Quo
`registry.gitlab.com/cryptoadvance/specter-desktop/electron-builder:latest` is based on `electronuserland/builder:latest`.
Contributor guide
Assessment
This issue has not been assessed yet.