Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libxp6 pre-depends on multiarch-support #403

Open
N-Accumbens opened this issue May 24, 2021 · 5 comments
Open

Libxp6 pre-depends on multiarch-support #403

N-Accumbens opened this issue May 24, 2021 · 5 comments
Labels

Comments

@N-Accumbens
Copy link

Hello,

I am trying to make a singularity container and it seems the build failed.

Here's the neurodocker command I ran

docker run --rm repronim/neurodocker:master generate singularity \
        --base debian:buster \
        --pkg-manager=apt \
        --freesurfer version=7.1.1 method=binaries --copy /usr/local/freesurfer/license.txt \
                 /opt/free-surfer-7.1.1 \
        --fsl version=6.0.4 method=binaries \
        --spm12 version=r7771 method=binaries > singularity.script

Here's the build command I used

VERSION=0.0.1
singularity build ptime_$VERSION.sif singularity.script

Attached is the build.log

The relevant message seems to be at the end

Selecting previously unselected package libxp6:amd64.
dpkg: regarding /tmp/toinstall.deb containing libxp6:amd64, pre-dependency problem:
 libxp6 pre-depends on multiarch-support
  multiarch-support is not installed.

dpkg: error processing archive /tmp/toinstall.deb (--install):
 pre-dependency problem - not installing libxp6:amd64
Errors were encountered while processing:
 /tmp/toinstall.deb
FATAL:   While performing build: while running engine: exit status 1
@zndr27
Copy link

zndr27 commented Jun 21, 2021

I'm having the same issue.

@Brainarea
Copy link

Dont know if you still have that issue but i might have found a workaround, see my post there: #419

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 14, 2023
@stebo85
Copy link
Collaborator

stebo85 commented Sep 17, 2023

I think it's safe to remove multiarch from these recipes because they are not needed anymore - has anyone else tested this and can confirm?

@github-actions github-actions bot removed the stale label Sep 18, 2023
Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants