May 2022 - openSUSE Support - openSUSE Mailing Lists

After updating Leap 15.3 all repositories become invalid?
by J Leslie Turriff 09 Jul '22

09 Jul '22

Last night I performed | zypper --non-interactive update --no-recommends then rebooted. Now when I perform | zypper refresh I get this: | ~ | ● zypper refresh | Retrieving repository 'Codec' metadata ............................................................................................................................................................................................................................. [error] | Repository 'Codec' is invalid. | [Codec|http://opensuse-guide.org/repo/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [Codec|http://opensuse-guide.org/repo/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Codec' because of the above error. | Repository 'Local' is up to date. | Problem retrieving files from 'Mozilla'. | Download (curl) error for 'https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/repod…': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'Mozilla' because of the above error. | Retrieving repository 'Packman Repository' metadata ................................................................................................................................................................................................................ [error] | Repository 'Packman Repository' is invalid. | [ftp.gwdg.de-openSUSE_Leap_$releasever| http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [ftp.gwdg.de-openSUSE_Leap_$releasever| http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Packman Repository' because of the above error. | Problem retrieving files from 'google-chrome'. | Download (curl) error for 'https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'google-chrome' because of the above error. | Problem retrieving files from 'hplip'. | Download (curl) error for 'https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15…': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'hplip' because of the above error. | Retrieving repository 'Fonts' metadata ............................................................................................................................................................................................................................. [error] | Repository 'Fonts' is invalid. | [openSUSE_Leap_15.3| http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [openSUSE_Leap_15.3| http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Fonts' because of the above error. | Retrieving repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' metadata ...................................................................................................................................................... [error] | Repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' is invalid. | [repo-backports-debug-update| http://download.opensuse.org/update/leap/15.3/backports_debug/] Valid metadata not found at specified URL | History: | - [repo-backports-debug-update| http://download.opensuse.org/update/leap/15.3/backports_debug/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' because of the above error. | Retrieving repository 'Update repository of openSUSE Backports' metadata ........................................................................................................................................................................................... [error] | Repository 'Update repository of openSUSE Backports' is invalid. | [repo-backports-update|http://download.opensuse.org/update/leap/15.3/backpor…] Valid metadata not found at specified URL | History: | - [repo-backports-update|http://download.opensuse.org/update/leap/15.3/backpor…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository of openSUSE Backports' because of the above error. | Retrieving repository 'Debug Repository' metadata .................................................................................................................................................................................................................. [error] | Repository 'Debug Repository' is invalid. | [repo-debug|http://download.opensuse.org/debug/distribution/leap/15.3/repo/o…] Valid metadata not found at specified URL | History: | - [repo-debug|http://download.opensuse.org/debug/distribution/leap/15.3/repo/o…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Debug Repository' because of the above error. | Retrieving repository 'Debug Repository (Non-OSS)' metadata ........................................................................................................................................................................................................ [error] | Repository 'Debug Repository (Non-OSS)' is invalid. | [repo-debug-non-oss| http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/] Valid metadata not found at specified URL | History: | - [repo-debug-non-oss| http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Debug Repository (Non-OSS)' because of the above error. | Retrieving repository 'Update Repository (Debug)' metadata ......................................................................................................................................................................................................... [error] | Repository 'Update Repository (Debug)' is invalid. | [repo-debug-update|http://download.opensuse.org/debug/update/leap/15.3/oss] Valid metadata not found at specified URL | History: | - [repo-debug-update|http://download.opensuse.org/debug/update/leap/15.3/oss] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Debug)' because of the above error. | Retrieving repository 'Update Repository (Debug, Non-OSS)' metadata ................................................................................................................................................................................................ [error] | Repository 'Update Repository (Debug, Non-OSS)' is invalid. | [repo-debug-update-non-oss|http://download.opensuse.org/debug/update/leap/15…] Valid metadata not found at specified URL | History: | - [repo-debug-update-non-oss| http://download.opensuse.org/debug/update/leap/15.3/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Debug, Non-OSS)' because of the above error. | Retrieving repository 'Non-OSS Repository' metadata ................................................................................................................................................................................................................ [error] | Repository 'Non-OSS Repository' is invalid. | [repo-non-oss|http://download.opensuse.org/distribution/leap/15.3/repo/non-o…] Valid metadata not found at specified URL | History: | - [repo-non-oss|http://download.opensuse.org/distribution/leap/15.3/repo/non-o…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Non-OSS Repository' because of the above error. | Retrieving repository 'Main Repository' metadata ................................................................................................................................................................................................................... [error] | Repository 'Main Repository' is invalid. | [repo-oss|http://download.opensuse.org/distribution/leap/15.3/repo/oss/] Valid metadata not found at specified URL | History: | - [repo-oss|http://download.opensuse.org/distribution/leap/15.3/repo/oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Main Repository' because of the above error. | Retrieving repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' metadata ........................................................................................................................................................ [error] | Repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' is invalid. | [repo-sle-debug-update|http://download.opensuse.org/debug/update/leap/15.3/s…] Valid metadata not found at specified URL | History: | - [repo-sle-debug-update|http://download.opensuse.org/debug/update/leap/15.3/s…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' because of the above error. | Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata ...................................................................................................................................................................... [error] | Repository 'Update repository with updates from SUSE Linux Enterprise 15' is invalid. | [repo-sle-update|http://download.opensuse.org/update/leap/15.3/sle/] Valid metadata not found at specified URL | History: | - [repo-sle-update|http://download.opensuse.org/update/leap/15.3/sle/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with updates from SUSE Linux Enterprise 15' because of the above error. | Retrieving repository 'Source Repository' metadata ................................................................................................................................................................................................................. [error] | Repository 'Source Repository' is invalid. | [repo-source|http://download.opensuse.org/source/distribution/leap/15.3/repo…] Valid metadata not found at specified URL | History: | - [repo-source|http://download.opensuse.org/source/distribution/leap/15.3/repo…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Source Repository' because of the above error. | Retrieving repository 'Main Update Repository' metadata ............................................................................................................................................................................................................ [error] | Repository 'Main Update Repository' is invalid. | [repo-update|http://download.opensuse.org/update/leap/15.3/oss] Valid metadata not found at specified URL | History: | - [repo-update|http://download.opensuse.org/update/leap/15.3/oss] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Main Update Repository' because of the above error. | Retrieving repository 'Update Repository (Non-Oss)' metadata ....................................................................................................................................................................................................... [error] | Repository 'Update Repository (Non-Oss)' is invalid. | [repo-update-non-oss|http://download.opensuse.org/update/leap/15.3/non-oss/] Valid metadata not found at specified URL | History: | - [repo-update-non-oss|http://download.opensuse.org/update/leap/15.3/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Non-Oss)' because of the above error. | Retrieving repository 'Untested Updates' metadata .................................................................................................................................................................................................................. [error] | Repository 'Untested Updates' is invalid. | [repo-update-test|http://download.opensuse.org/update/leap/15.3-test/] Valid metadata not found at specified URL | History: | - [repo-update-test|http://download.opensuse.org/update/leap/15.3-test/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Untested Updates' because of the above error. | Retrieving repository 'trinity-bin' metadata ....................................................................................................................................................................................................................... [error] | Repository 'trinity-bin' is invalid. | [trinity-bin| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Valid metadata not found at specified URL | History: | - [trinity-bin| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'trinity-bin' because of the above error. | Retrieving repository 'trinity-noarch' metadata .................................................................................................................................................................................................................... [error] | Repository 'trinity-noarch' is invalid. | [trinity-noarch| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Valid metadata not found at specified URL | History: | - [trinity-noarch| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'trinity-noarch' because of the above error. | Some of the repositories have not been refreshed because of an error. | @20:30:33,root@pinto rc=4 I had not made any changes before or after doing the update. Here are my repositories: | ~ | ● zypper lr -u | Repository priorities in effect: (See 'zypper lr -P' for details) | 97 (raised priority) : 1 repository | 98 (raised priority) : 3 repositories | 99 (default priority) : 19 repositories | | # | Alias | Name | Enabled | GPG Check | Refresh | URI | ---+---------------------------------------+------------------------------------------------------------------------------+---------+-----------+---------+-------------------------------------------------------------------------------------- | 1 | Codec | Codec | Yes | (r ) Yes | Yes | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/ | 2 | Local | Local | Yes | ( ) No | Yes | dir:/usr/local/RPMrepository | 3 | Mozilla | Mozilla | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ | 4 | ftp.gwdg.de-openSUSE_Leap_$releasever | Packman Repository | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/ | 5 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | https://dl.google.com/linux/chrome/rpm/stable/x86_64 | 6 | hplip | hplip | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15… | 7 | openSUSE_Leap_15.3 | Fonts | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/ | 8 | repo-backports-debug-update | Update repository with Backports debuginfo package updates for openSUSE Leap | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/backports_debug/ | 9 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/backports/ | 10 | repo-debug | Debug Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/ | 11 | repo-debug-non-oss | Debug Repository (Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/ | 12 | repo-debug-update | Update Repository (Debug) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/oss | 13 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/non-oss/ | 14 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ | 15 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ | 16 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/sle/ | 17 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/sle/ | 18 | repo-source | Source Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/ | 19 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss | 20 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ | 21 | repo-update-test | Untested Updates | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3-test/ | 22 | trinity-bin | trinity-bin | Yes | (r ) Yes | Yes | http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… | 23 | trinity-noarch | trinity-noarch | Yes | (r ) Yes | Yes | http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… | @20:30:15,root@pinto rc=0 Leslie -- Platform: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.11 tde-config: 1.0

7 14

x2go immediately disconnects after connection
by Tristan Miller 01 Jun '22

01 Jun '22

Dear all, I've been using X2Go on a pair of openSUSE Tumbleweed systems. On 2022-05-23 I did a dist-upgrade on both and now I'm no longer able to run a remote application or desktop via X2Go -- the client successfully connects to the server but then immediately disconnects. There's nothing obvious in the client and server logs (even at debug-level verbosity) that explains the immediate disconnects -- I see the client successfully connecting to the server and then immediately disconnecting. (Still, I can provide the logs on request.) Some additional relevant pieces of information: * The problem occurs regardless which remote application or desktop I'm trying to run. I've tried xfce4-terminal, xterm, icewm, and others. * The client has no problem connecting to the Tumbleweed server directly via ssh -X and running remote applications. * The client has no problem connecting to an X2Go server running on a different machine running Leap 15.3. * X2Go itself was not updated in the dist-upgrade. * I've tried upgrading to the latest development versions of x2goserver and x2goclient but this hasn't helped. ( I am thinking that some security-hardening update may be at fault here. I tried temporarily disabling AppArmor on the server but that didn't work around the problem. And it doesn't look like the server's sshd_config file was touched in the dist-upgrade. Can anyone suggest any further troubleshooting steps? If anyone cares to do any testing themselves, my packages for the latest x2goserver, x2goclient, nx-libs, and pinentry-x2go are available at <https://download.opensuse.org/repositories/home:/psych0naut:/x2go/openSUSE_…>. Regards, Tristan -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tristan Miller Free Software developer, ferret herder, logologist https://logological.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 3

Re: Request for Old ISO/Verification Hash
by Lubos Kocman 30 May '22

30 May '22

Hello fireclay! I'm bit afraid that we do not hold backups of files for rolling releases, It sort of makes sense as you can have up to 7 snapshots a week. I did check /backup on pontifex but unfortunatelly it was only for content of /var. If you feel confident that there could be more request like this one, you should probably write a proposal to admin(a)opensuse.org<mailto:admin@opensuse.org> to keep checksum files for e.g. 14 days or similar. I can imagine that this might be quite demanding feature in regions with low bandwidth, where people want to be sure-sure that their image was corrupted before downloading a new one. But then TW might not be the best fit in given environment. Dominique do you have thoughts on this one? Leap could use similar approach for quarterly updates. Lubos On Thu, 2022-05-26 at 13:49 +0000, opensuse.fireclay(a)simplelogin.fr wrote: 1. Where can I find this old ISO? openSUSE-Tumbleweed-DVD-x86_64-Snapshot20220515.iso 2. If not can I get ISO Hash Check file or key to verify my ISO. 3. If still not how can I check integrity of my aforesaid ISO. Would appreciate any helpful response. Thanks

1 0

Ice Breaker:
by -pj 28 May '22

28 May '22

https://www.youtube.com/watch?v=BRRy6t5K3R4

2 3

Where we can find good souls to help build a repo and maintain him ?
by Felipe fernandes da costa 27 May '22

27 May '22

I suggest a private server outside from university. But for that happen need at least money to build minimal structure.

2 1

15.4 boot failure - NVME / filesystem not found by latest kernel
by Felix Miata 25 May '22

25 May '22

UEFI booting. pi3p16s154 is nvme0n1p16 ext4 root filesystem LABEL. crypto is not employed anywhere on the PC. 5.14.21-150400.19 kernel boots normally. 5.14.21-150400.22 kernel is not recognizing USB stick insertion, so there's no way I know to get /run/initramfs/rdsosreport.txt onto a stick for susepasting, and susepaste isn't in the emergency shell. Neither does the shell include grep. I rebuilt initrd with add_dracutmodules+=debug but still no susepaste or grep, or lsblk, or fdisk, or improvement. Selected excerpts from rdsosreport.txt: systemd-modules-load.service: Failed with result 'exit-code'. Failed to start Load Kernel Modules. systemd-modules-load...Failed to look up module alias 'sg': Function not implemented condition check resulted in dracut pre-trigger hook being skipped dracut-initqueue...Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: /lib/dracut/hooks/initqueue/finished/devexists-/dev/disk/by-label-pi3p16s154.sh "if ! grep After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup(a)*.service 2>/dev/null; then [ -e " /dev/disk/by-label/pi3p16s154" ] ... Warning: dracut-initqueue: starting timeout scripts Warning: Could not boot. systemd[1]: Starting Dracut Emergency Shell.... Is there anything above that suggests why the .22 initrd failed to enable nvme / filesystem to be found? https://paste.opensuse.org/57952814 is output from lsinitrd /boot/initrd. I did essentially the same dup to 15.4 a week ago on another PC with same Intel b250 chipset, also UEFI & nvme, and no trouble. I copied each of 3 .22 initrds from the first PC to the second. The first boots normally. The second not, initially stopping at starting dracut initqueue hook, winding up in emergency shell. So did the #3 initrd. The initrd from the update last week copied to today's also fails in same manner. The big difference between the two PCs: the problem PC contains 2 HDDs with multiple partitions, about half of which comprise several mdraid devices, none of which have anything to do with booting the problem 15.4 installation. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 3

Continue zypper dup now that 15.4 is RC?
by Robert Williams 24 May '22

24 May '22

Now that Leap 15.4 has reached RC status is it still recommended to use zypper dup until GM, or can one now achieve the same result with zypper patch or zypper up? -- Bob

4 5

Crashed install on filesystem package instalation
by Fodrek Peter ml. 24 May '22

24 May '22

Dear openSUSE experts, I have crahed system that I want to reinstall via USB install of Tumbleweed withou format partitions On the system there were/are some directory links with absolute path made like/in style of eg. mkdir /home/partOfShare mv /usr/share/"someDir" /home/partOfShare ln -s /home//partOfShare/"someDir" /usr/share I was recovered most of the install failures by replacing absolute links to relavive links via cd /usr/share ln -s ../../partOfShare/"someDir" . BUT during install there are failed install filesystem package with lua script fialed (:%prein/filesystem..") No such file o directory Only other erros are missing /bin/sh, even if there is working binary (not link) in /mnt/bin whene using installer. but every error message conatins %preinst I asume that %postinst may be problem as well. I cannot find content of %preinst variable, so I cannot find which directory to check for bad link. I there anzbody who is able and allowed to send me directorz where to find content of %preinst variable, please? Thank you for any data that helps me to find not corect path I look forward hearing from you Yours faithfullz Peter Fodrek,j.j.

3 2

Which repository to use for postfix-policyd-spf-perl on Leap 15.4 in Raspberry Pi 4B
by Freek de Kruijf 24 May '22

24 May '22

Searching for the package postfix-policyd-spf-perl for Leap 15.4 architecture armv7l, I found: https://download.opensuse.org/repositories/devel:/languages:/perl/ with version for almost all openSUSE versions: openSUSE_Leap_15.0 till openSUSE_Leap_15.3, and SLE_15 till SLE_15_SP4, but Leap 15.4 is only mentioned as 15.4. Fortunately it is a noarch packet, so most likely they are all almost the same. But still, is this last one meant for Leap 15.4? It would be more consistent if it is named openSUSE_Leap_15.4. -- fr.gr. member openSUSE Freek de Kruijf

2 1

15.4 RC suddently asks for decision on suse packages signing key when going into yast2 online_update_configuration gui?
by cagsm 18 May '22

18 May '22

Support, a freshly updated 15.4 RC (via zypper dup some day(s) ago) suddenly asks for a decision on this suse packages signing key in yast2 module when going into the online update configuration gui. what the heck? YaST2 - online_update_configuration @ tux01 Loading the Package Manager... x Load Sources => Refresh Sources - Rebuild Cache - Load Data ┌──────────────────────────────────────────────────────────────────────────────────────────────────┐ │┌──────────────────────────────────┐ Import Untrusted GnuPG Key │ ││The owner of the key may ┬ The following GnuPG key has been found in repository │ ││distribute updates, packages, and │ Update repository with updates from SUSE Linux Enterprise 15│ ││package repositories that your │ (http://download.opensuse.org/update/leap/15.4/sle/): │ ││system will trust and offer for │ ┌──────────────────────────────────────────────────────────┐│ ││installation and update without │ │ID: 70AF9E8139DB7C82 ─│ ││any further warning. In this way, │ │Name: SuSE Package Signing Key ││ ││importing the key into your │ │Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB ││ ││keyring of trusted keys allows the┴ └──────────────────────────────────────────────────────────┘│ ││key owner to have a certain amount│ You can choose to import it into your keyring of trusted │ ││of control over the software on │ public keys, meaning that you trust the owner of the key. │ ││your system. │ You should be sure that you can trust the owner and that │ ││ │ the key really belongs to that owner before importing it. │ ││A warning dialog opens for every │ │ │└──────────────────────────────────┘ [Trust] [Cancel] │ └──────────────────────────────────────────────────────────────────────────────────────────────────┘ Downloading: 3 KiB/s (on average 3 KiB/s) - http://download.opensuse.org/update/.../repodata/repomd.xml i have not clicked or selected anything i only fired up yast2 and went into that module to check the state of online updates and if they were configured etc. what now? why? :( what IS the advices and best practices work flow actually for the END USER on these matters deciding about keys and their acceptance and trust when messing or just working with the normal default repos on the various opensuse leap systems? I just fail to understand how a normal user would need to make up decisions of trust and everything that goes into this. I am very dissatistfied with these matters :( frustrated. ty.

1 0