April 2020 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Upgrade apache2-mod_php7 halts zypper on TW
by Jogchum Reitsma 14 Apr '20

14 Apr '20

Hi, For some time now when upgrading TW (which I do regularly using zypper dup --no-allow-vendor-change) when it comes to apache2-mod_php7, zypper halts. That is, it ends with the 100% installed message, and than it stops. I have to "kill -9" it to free the terminal, and have to start zypper anew. Anyone any idea whit might cause that? cheers, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 9

[opensuse-support] Multiple persistent 'Digest verification failed' errors when 'zypper dup' on tumbleweed
by Vibhav Sharma 12 Apr '20

12 Apr '20

On OpenSUSE Tw zypper lr > Repository priorities are without effect. All enabled repositories share > the same priority. > > # | Alias | Name | > Enabled | GPG Check | Refresh > > ---+-------------------------------------+----------------------------+---------+-----------+-------- > 1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | > Yes | (r ) Yes | Yes > 2 | download.opensuse.org-oss | Main Repository (OSS) | > Yes | (r ) Yes | Yes > 3 | download.opensuse.org-tumbleweed | Main Update Repository | > Yes | (r ) Yes | Yes > 4 | http-download.opensuse.org-447cf2a7 | openSUSE:Factory | No > | ---- | ---- > 5 | http-download.opensuse.org-6925c72a | hardware:razer | > Yes | (r ) Yes | Yes > 6 | http-download.opensuse.org-e45a9633 | openSUSE:Tumbleweed | No > | ---- | ---- > 7 | http-download.opensuse.org-f3a8d516 | home:Horst3180 | > Yes | (r ) Yes | Yes > 8 | http-ftp.gwdg.de-2eba93dd | Packman Repository | > Yes | (r ) Yes | Yes > 9 | http-opensuse-guide.org-da5f09af | libdvdcss repository | > Yes | (r ) Yes | Yes > 10 | repo-debug | openSUSE-Tumbleweed-Debug | No > | ---- | ---- > 11 | repo-source | openSUSE-Tumbleweed-Source | No > | ---- | ---- > When I do zypper dup, I get : Retrieving package glibc-2.31-3.2.x86_64 > (5/418), 1.7 MiB ( 5.9 MiB > unpacked) > Retrieving: glibc-2.31-3.2.x86_64.rpm > .......................................................................................................[done > (1.3 MiB/s)] > > Warning: Digest verification failed for file 'glibc-2.31-3.2.x86_64.rpm' > [/var/tmp/AP_0xTh4ctF/x86_64/glibc-2.31-3.2.x86_64.rpm] > > expected 5d1bb5abf4e3b5abbf191469151c2923a80c3545a7add6b2d6051617102bbaba > but got a89ae86e05e55440b3cdf4cf39ae1323fb87459a7968aaeafed6c9f1d2f2f066 > > For consistently the same packages. I have tried: # zypper ref (tried --force too) # zypper clean # zypper dup multiple times but keep getting the same issue. Some packages are even reporting multiple different digests on retrying: (Following is from one run) Retrieving package gcc9-info-9.2.1+git1192-1.3.noarch > (174/418), 2.3 MiB ( 2.2 MiB > unpacked) > Retrieving: gcc9-info-9.2.1+git1192-1.3.noarch.rpm > ........................................................................................[done > (790.2 KiB/s)] > > Warning: Digest verification failed for file > 'gcc9-info-9.2.1+git1192-1.3.noarch.rpm' > [/var/tmp/AP_0xTh4ctF/noarch/gcc9-info-9.2.1+git1192-1.3.noarch.rpm] > > expected 0474686086f939eaa42921d38542824b8066fb0f49902ac29b16876693e37802 > but got b13c9fde9d2dbcf03cdf49048fa0088c56ae19e4e925020f41cbf1ac67a5a845 > > Accepting packages with wrong checksums can lead to a corrupted system and > in extreme cases even to a system compromise. > > However if you made certain that the file with checksum 'b13c..' is > secure, correct > and should be used within this operation, enter the first 4 characters of > the checksum > to unblock using this file on your own risk. Empty input will discard the > file. > > Unblock or discard? [b13c/...? shows all options] (discard): > Package gcc9-info-9.2.1+git1192-1.3.noarch (Main Repository (OSS)) seems > to be corrupted during transfer. Do you want to retry retrieval? > Abort, retry, ignore? [a/r/i] (a): r > Retrieving package gcc9-info-9.2.1+git1192-1.3.noarch > (174/418), 2.3 MiB ( 2.2 MiB > unpacked) > Retrieving: gcc9-info-9.2.1+git1192-1.3.noarch.rpm > ..........................................................................................[done > (1.5 MiB/s)] > > Warning: Digest verification failed for file > 'gcc9-info-9.2.1+git1192-1.3.noarch.rpm' > [/var/tmp/AP_0xTh4ctF/noarch/gcc9-info-9.2.1+git1192-1.3.noarch.rpm] > > expected 0474686086f939eaa42921d38542824b8066fb0f49902ac29b16876693e37802 > but got d544e4e1439a2a79ea65173bb2c142a26f1ca1818d21a4d2c9264ccc853fe0ae > > Accepting packages with wrong checksums can lead to a corrupted system and > in extreme cases even to a system compromise. > > However if you made certain that the file with checksum 'd544..' is > secure, correct > and should be used within this operation, enter the first 4 characters of > the checksum > to unblock using this file on your own risk. Empty input will discard the > file. > > Unblock or discard? [d544/...? shows all options] (discard): > Package gcc9-info-9.2.1+git1192-1.3.noarch (Main Repository (OSS)) seems > to be corrupted during transfer. Do you want to retry retrieval? > Abort, retry, ignore? [a/r/i] (a): r > Retrieving package gcc9-info-9.2.1+git1192-1.3.noarch > (174/418), 2.3 MiB ( 2.2 MiB > unpacked) > Retrieving: gcc9-info-9.2.1+git1192-1.3.noarch.rpm > ..........................................................................................[done > (1.3 MiB/s)] > > Warning: Digest verification failed for file > 'gcc9-info-9.2.1+git1192-1.3.noarch.rpm' > [/var/tmp/AP_0xTh4ctF/noarch/gcc9-info-9.2.1+git1192-1.3.noarch.rpm] > > expected 0474686086f939eaa42921d38542824b8066fb0f49902ac29b16876693e37802 > but got d544e4e1439a2a79ea65173bb2c142a26f1ca1818d21a4d2c9264ccc853fe0ae > > Accepting packages with wrong checksums can lead to a corrupted system and > in extreme cases even to a system compromise. > > However if you made certain that the file with checksum 'd544..' is > secure, correct > and should be used within this operation, enter the first 4 characters of > the checksum > to unblock using this file on your own risk. Empty input will discard the > file. > > Unblock or discard? [d544/...? shows all options] (discard): > Package gcc9-info-9.2.1+git1192-1.3.noarch (Main Repository (OSS)) seems > to be corrupted during transfer. Do you want to retry retrieval? > Abort, retry, ignore? [a/r/i] (a): r > Retrieving package gcc9-info-9.2.1+git1192-1.3.noarch > (174/418), 2.3 MiB ( 2.2 MiB > unpacked) > Retrieving: gcc9-info-9.2.1+git1192-1.3.noarch.rpm > ..........................................................................................[done > (1.3 MiB/s)] > > Warning: Digest verification failed for file > 'gcc9-info-9.2.1+git1192-1.3.noarch.rpm' > [/var/tmp/AP_0xTh4ctF/noarch/gcc9-info-9.2.1+git1192-1.3.noarch.rpm] > > expected 0474686086f939eaa42921d38542824b8066fb0f49902ac29b16876693e37802 > but got b13c9fde9d2dbcf03cdf49048fa0088c56ae19e4e925020f41cbf1ac67a5a845 > > Accepting packages with wrong checksums can lead to a corrupted system and > in extreme cases even to a system compromise. > > However if you made certain that the file with checksum 'b13c..' is > secure, correct > and should be used within this operation, enter the first 4 characters of > the checksum > to unblock using this file on your own risk. Empty input will discard the > file. > > Unblock or discard? [b13c/...? shows all options] (discard): >

2 3

[opensuse-support] Updating kernel on persistent Live image?
by Andrei Borzenkov 10 Apr '20

10 Apr '20

Is it possible at all? Kernel/initrd are loaded from separate boot partition and openSUSE itself is configured without bootloader. It is possible to install new kernel, but it is not used. I had some hope that initial initird is using some tricks to kexec kernel from (persistent) root partition, but apparently this is not the case. I can of course copy new kernel/initrd into boot partition, but I am not sure generated initrd is suitable for Live boot. Anyone did it before? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] commercial use
by Samet Kocaoluk 10 Apr '20

10 Apr '20

Hello All, i want install openSUSE 15.1 leap on the corparate server. Can i use it commercially? İs it legally? Thank you, Samet K.

2 1

[opensuse-support] network manager on leap 15.1
by David T-G 09 Apr '20

09 Apr '20

Hi, all -- I am so frickin' tired of this stupid Network Manager thing. I've gone round and round looking at YaST and seeing that I'm using NM and trying to find nm-applet to set an IP, and it all just goes in a circle. I am in this case using my Live 15.1 thumb drive, right out of the box (so to speak), and trying to assign a static IP address for this server. I've hit docs sites, wikis, mailing list archives, and more and I'm just getting nowhere. I would REALLY love some simple Pointers for Dummies steps to get this thing set. TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 6

[opensuse-support] Installing the Shorewall lite firewall is not possible. What is wrong?
by JadoNena 07 Apr '20

07 Apr '20

I did ask this question before on the opensuse-security list because I was thinking it is about security. One other person said that may be better to ask the question here becuase it is about installation. Ok. I am asking it twice on two lists! Sorry. Here it is. Helo, I am hoping to install Shorewall lite firewall on the remote VM. On it I am running openSUSE Leap 15.1 for production. It is just new instaled. I added the most modern version repositorie zypper ar https://download.opensuse.org/repositories/security:/netfilter/openSUSE_Lea… Security zypper install shorewall-lite shorewall-init When I install it zypper install shorewall-lite shorewall-init there is this problem Problem: shorewall-init-5.2.4-242.1.noarch requires shorewall >= 5.0, but this requirement cannot be provided not installable providers: shorewall-5.1.12.4-lp151.2.24.noarch[Leap151OSS] shorewall-5.2.4-lp151.238.1.noarch[Security] Solution 1: do not install shorewall-lite-5.2.4-242.1.noarch Solution 2: do not install shorewall-init-5.2.4-242.1.noarch Solution 3: break shorewall-init-5.2.4-242.1.noarch by ignoring some of its dependencies I do not understand it. What do I do that is the problem? Thank you for the help, Janek -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

8 19