-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
First, x.org is missing from SLES, apparently:
Enter version to install: (<ENTER> for latest)
4.5.2
Installer already exists. Not downloading.
User install from RPM installer R-4.5.2-1-1.aarch64.rpm...
Updating package indexes...
Refreshing service 'container-suseconnect-zypp'.
Repository 'SLE_BCI' is up to date.
All repositories have been refreshed.
Installing R-4.5.2-1-1.aarch64.rpm...
Refreshing service 'container-suseconnect-zypp'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: 1: nothing provides 'xorg-x11' needed by the to be installed R-4.5.2-1-1.aarch64
Solution 1: do not install R-4.5.2-1-1.aarch64
Solution 2: break R-4.5.2-1-1.aarch64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c/d/?] (c): 2
Ignoring the dependency:
> x11()
Error in x11() : X11 module cannot be loaded
In addition: Warning message:
In grSoftVersion() :
unable to load shared object '/opt/R/4.5.2/lib/R/modules//R_X11.so':
libSM.so.6: cannot open shared object file: No such file or directory
Adding the oss opensuse 16.0 repo fixes this:
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/aarch64 repo-oss
zypper refresh
This needs a manual step to accept the signing key, this can be probably automated:
76ebfcbb3cd8:~ # zypper refresh
Refreshing service 'container-suseconnect-zypp'.
Repository 'SLE_BCI' is up to date.
Looking for gpg keys in repository repo-oss.
gpgkey=http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/aarch64/repodata/repomd.xml.key
New repository or package signing key received:
Repository: repo-oss
Key Fingerprint: AD48 5664 E901 B867 051A B15F 35A2 F86E 29B7 00A4
Key Name: openSUSE Project Signing Key <opensuse@opensuse.org>
Key Algorithm: RSA 4096
Key Created: Mon Jun 20 14:03:14 2022
Key Expires: Fri Jun 19 14:03:14 2026
Rpm Name: gpg-pubkey-29b700a4-62b07e22
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
IDK if adding this repo would be reasonable for SLES 16.0 users. Do we know anyone that uses our builds on this distro or on other SLES versions?
EDIT: adding the oss key is easy:
rpm --import https://cdn.opensuse.org/distribution/leap/16.0/repo/oss/aarch64/repodata/repomd.xml.key
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels