December 2021 - openSUSE Factory - openSUSE Mailing Lists

Replacing Fcitx4 with Fcitx5 in Factory
by Nianqing Yao 04 Jan '22

04 Jan '22

Hi everyone, There's a input method framework called fcitx4 shipped with openSUSE Tumbleweed and Leap, but when the whole project turns to new fcitx5, fcitx4 seems to be abounded and outdated. As far as I know, fcitx5 only exists in i18n project on the OBS, not in the main OSS repo. Could it possible to replace fcitx4 with fcitx5 in factory's OSS repo? So that Tumbleweed and Leap will finally benefit from it.

3 3

Again AMDGPU issue (TW)
by Frans de Boer 03 Jan '22

03 Jan '22

LS, Due to time constrains, I just post the issue first here. After a short time, 5.15.8 and 5.16.9-rc6 crash again. Probably different reason as before. Log listing: Dec 20 10:47:17 pws1 systemd[2497]: Started Kate - Advanced Text Editor. Dec 20 10:47:20 pws1 kioslave5[4403]: Qt: Session management error: networkIdsList argument is NULL Dec 20 10:53:59 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! Dec 20 10:54:02 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005 Dec 20 10:54:02 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! Dec 20 10:54:06 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005 Dec 20 10:54:06 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! Dec 20 10:54:06 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=51260, emitted seq=51262 Dec 20 10:54:06 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg.bin pid 1903 thread Xorg.bin:cs0 pid 1937 Dec 20 10:54:06 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Dec 20 10:54:06 pws1 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 20 10:54:09 pws1 kernel[1828]: Last message '[drm:amdgpu_cs_ioctl' repeated 4 times, suppressed by syslog-ng on pws1.fransdb.local Dec 20 10:54:09 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005 Dec 20 10:54:09 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to disable gfxoff! Dec 20 10:54:10 pws1 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 20 10:54:21 pws1 kernel[1828]: Last message '[drm:amdgpu_cs_ioctl' repeated 7 times, suppressed by syslog-ng on pws1.fransdb.local Dec 20 10:54:20 pws1 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Dec 20 10:54:20 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed Dec 20 10:54:20 pws1 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Dec 20 10:54:20 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Dec 20 10:54:21 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx Dec 20 10:54:24 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005 Dec 20 10:54:24 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to disable smu features. Dec 20 10:54:24 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Fail to disable dpm features! Dec 20 10:54:24 pws1 kernel: [drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block <smu> failed -62 Dec 20 10:54:24 pws1 kernel: [drm] free PSP TMR buffer Dec 20 10:54:25 pws1 kernel: [drm] psp gfx command DESTROY_TMR(0x7) failed and response status is (0x80000306) Dec 20 10:54:25 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset Dec 20 10:54:25 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset Dec 20 10:54:25 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset Dec 20 10:54:29 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005 Dec 20 10:54:29 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset failed Dec 20 10:54:29 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:03:00.0 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ---------------------------- I shall report this later today in bugzilla. 5.15.7 and 5.16.0-rc5 where fine. Regards, Frans. -- A: Yes, just like that A: Ja, net zo Q: Oh, Just like reading a book backwards Q: Oh, net als een boek achterstevoren lezen A: Because it upsets the natural flow of a story A: Omdat het de natuurlijke gang uit het verhaal haalt Q: Why is top-posting annoying? Q: Waarom is Top-posting zo irritant?

2 3

odd style of URL on download.o.o (but causing a lot of traffic)
by Per Jessen 03 Jan '22

03 Jan '22

I am seeing a lot of traffic with GET URLs such as these: GET /repositories/./Apache:/MirrorBrain/SLE_15_SP2/x86_64/http://build.opensuse.org/ GET /repositories/Apache/openSUSE_Leap_15.2/x86_64/https://software.opensuse.org/ GET /repositories/./Apache:/Shibboleth/SLE_12_SP2/repodata/http://build.opensuse.org/ GET /repositories/./Apache:/MirrorBrain/SLE_15_SP2/https://software.opensuse.org/ Of course they all result in a 404, but currently such requests take up almost 10% of our total http traffic. Does anyone recognise that unusual request format, with 'https://software.opensuse.org/' or 'http://build.opensuse.org/' appended ? This started on 6 December with a few hundred thousand requests, but grew to 2million by 13 December, now around 3.5-4million a day. -- Per Jessen, Zürich (7.9°C) Member, openSUSE Heroes

7 25

Build 20211201 Crash / Reboot
by Joe Salmeri 01 Jan '22

01 Jan '22

I just had my first crash and reboot on this system since I installed TW on it 9 months ago. System has been running fine and I was using it at the time it occurred with Chrome, VMWare Player, konsole, and my editor running. In the approximately 20 minutes before the crash / reboot I found lots of the following journal messages: kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' About 10 minutes before the crash / reboot, snapper-timeline.service ran to cleanup snapshots and completed without an issues. 4 minutes later the following journal messages occurred, the video went black, and system rebooted. I was typing at the time this occurred. plasmashell[1773]: file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:34:43: QML ScrollBar: Binding loop detected for property "visible" kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[1750]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11925]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kglobalaccel5[11977]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY' kernel: loop: module loaded kernel: lp: driver loaded but no devices found kernel: PPP generic driver version 2.4.2 kernel: tun: Universal TUN/TAP device driver, 1.6 kernel: watchdog: watchdog0: watchdog did not stop! kernel: watchdog: watchdog0: watchdog did not stop! kernel: VFIO - User Level meta-driver version: 0.3 kernel: watchdog: watchdog0: watchdog did not stop! kernel: watchdog: watchdog0: watchdog did not stop! System booted back up fine and I ran checks on all the drives and there were no issues. TW was updated to 20211201 on 12/03/2021. System is on 24/7 and has only been booted 2 times since then (for normal reasons, not because of problems). System is an i7 with 32 GB ram using Intel HD internal graphics. I believe this is what caused the crash: file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:34:43: QML ScrollBar: Binding loop detected for property "visible" but am wondering why all the meta key issues are being reported??? The meta key has been working fine. Anyone else seen this issue?

3 2

[opensuse-factory] reproducible builds status 2021-12
by Bernhard M. Wiedemann 31 Dec '21

31 Dec '21

Hi, last month's status: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… Last months' reproducible builds project updates (including my work): https://reproducible-builds.org/reports/2021-11/ I uploaded https://rb.zq1.de/compare.factory-20211231/ today and rbstats are: total-packages: 14268 (+5) build-tried: 14238 (+5) build-failed: 31 (-3) build-n-a: 296 (+9) build-succeeded: 13911 (-1) build-official-failed+na: 36 (-18) build-compare-failed: 406 (+9) build-compare-succeeded: 13505 (-10) verify-failed: 454 (-5) verified-semi-reproducible: 13134 (-54) bit-by-bit-identical: 13467 (+39) not-bit-by-bit-identical: 440 (-38) not-bit-by-bit-identicalcheck: 444 (-40) https://rb.zq1.de/compare.factory-20211231/graph.png shows the change over time https://rb.zq1.de/compare.factory-20211231/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 5 were in ring0 35 were in ring1 That makes it 40/3247 => 1.23 % which is below the overall average of 406/13911 => 2.92 % 440/13911 => 3.16 % of packages are not perfectly reproducible unreproducible packages in ring0(bootstrap): bison PGO+parallelism gcc10 PGO grep PGO? pam PDF/date python38 PGO Ciao Bernhard M.

1 0

Tumbleweed - Review of the week 2021/52
by Dominique Leuenberger / DimStar 31 Dec '21

31 Dec '21

Dear Tumbleweed users and hackers, The last week of the year, and the last day of the year, are coming to an end. Tumbleweed had a small dip, as the last two snapshots that moved to openQA had to be stopped from being published. Nevertheless, we still managed to publish 6 snapshots before heading out to the new- year celebrations (1223…1228). The snapshots contained those relevant changes: * Qemu 6.2.0 * Boost 1.78.0 * gimp 2.10.30 * gpg 2.3.4 * Pango 1.50.3 * sssd 2.6.3 * Default ruby interpreter switched from 2.7 to 3.0 The staging projects are mostly, but not completely, empty. The few ones in use are testing these items: * Wayland 1.20 (Seems to cause some bugs, see https://bugzilla.opensuse.org/show_bug.cgi?id=1194190 * Linux kernel 5.15.12 * Ruby 3.1. A direct attempt to switch to Ruby 3.1, and removing Ruby 2.7 and Ruby 3.0 in one go. Most likely it will be phased a little bit (e.g. Vagrant is not Ruby 3.1 compatible yet) * zstd 1.5.1: breaks build of zchunk and libzypp * Enabling the build of python310-* modules; the move of the default python3 provider to python310 could follow soon after Cheers, and a happy new year, Dominique

1 0

Re Tumbleweed repo errors
by David Walker 30 Dec '21

30 Dec '21

The possibility of specifying multiple download servers is great. I do think, though, that something has been amiss with download.opensuse.org for the past week or so. Just today, I've gotten server errors of the form from a "zypper dup": Retrieving: gnome-shell-classic-41.1-1.1.noarch.rpm ...........[error (974 B/s)] Download (curl) error for 'http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/noarch/gnome…': Error code: Curl error 55 Error message: Connection died, tried 5 times before giving up Abort, retry, ignore? [a/r/i/...? shows all options] (a): r It recovers after I respond "r" to its question about what to do, but this should be a rare event. David

4 7

Re: Python version and TW
by Du, Felix (NSB - CN/Qingdao) 30 Dec '21

30 Dec '21

Is there a plan when python310 will be the default to replace python38? Best regards, ---------------------------------------- Name: Felix Du Tel: +86 15376874189 E-mail: felix.du(a)nokia-sbell.com<mailto:felix.du@nokia-sbell.com>

1 0

New Tumbleweed snapshot 20211228 released!
by Dominique Leuenberger 30 Dec '21

30 Dec '21

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: bind (9.16.23 -> 9.16.24) fetchmail (6.4.25 -> 6.4.26) gpgme gpgmeqt grub2 libical (3.0.11 -> 3.0.12) libical-glib (3.0.11 -> 3.0.12) netpbm python-SQLAlchemy (1.4.27 -> 1.4.29) python-incremental python-setuptools ruby (2.7 -> 3.0) yast2-trans (84.87.20211219.ed0ba1e469 -> 84.87.20211227.623da84d84) === Details === ==== bind ==== Version update (9.16.23 -> 9.16.24) Subpackages: bind-doc bind-utils python3-bind - Upgrade to release 9.16.24 This upgrade fixes the following bugs: * mdig now honors the operating system's preferred ephemeral port range. * Fix a "named" crash related to removing and restoring a `catalog-zone` entry in the configuration file and running `rndc reconfig`. * dns_sdlz_putrr failed to process some valid resource records. * dnssec-dsfromkey failed to omit revoked keys. Functional change: * Change the message when accepting TCP connection has failed to say "Accepting TCP connection failed" and change the log level for ISC_R_NOTCONNECTED, ISC_R_QUOTA and ISC_R_SOFTQUOTA results codes from ERROR to INFO. [bind-9.16.24.tar.xz] ==== fetchmail ==== Version update (6.4.25 -> 6.4.26) Subpackages: fetchmailconf - update to 6.5.26: * When using wolfSSL 5.0.0, work around a bug that appears to hit wolfSSL when receiving handshake records while still in SSL_peek(). Workaround is to read 1 byte and cache it, then call SSL_peek() again. This affects only some servers. * New serbian translation. ==== gpgme ==== Subpackages: libgpgme11 libgpgmepp6 - Add patches to support building bindings packages for Python 3.10 * gpgme-D545-python310.patch -- https://dev.gnupg.org/D545 * gpgme-D546-python310.patch -- https://dev.gnupg.org/D546 ==== gpgmeqt ==== - Add patches to support building bindings packages for Python 3.10 * gpgme-D545-python310.patch -- https://dev.gnupg.org/D545 * gpgme-D546-python310.patch -- https://dev.gnupg.org/D546 ==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - Fix CVE-2021-3981 (bsc#1189644) * 0001-grub-mkconfig-restore-umask-for-grub.cfg.patch - Fix can't allocate initrd error (bsc#1191378) * 0001-Factor-out-grub_efi_linux_boot.patch * 0002-Fix-race-in-EFI-validation.patch * 0003-Handle-multi-arch-64-on-32-boot-in-linuxefi-loader.patch * 0004-Try-to-pick-better-locations-for-kernel-and-initrd.patch * 0005-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch * 0006-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch * 0007-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch * 0008-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch * 0009-x86-efi-Reduce-maximum-bounce-buffer-size-to-16-MiB.patch * 0010-efilinux-Fix-integer-overflows-in-grub_cmd_initrd.patch * 0011-Also-define-GRUB_EFI_MAX_ALLOCATION_ADDRESS-for-RISC.patch ==== libical ==== Version update (3.0.11 -> 3.0.12) - update to 3.0.12: * Fix a libicalval crash in cleanVObject * METHOD:DECLINECOUNTER must have DTEND or DURATION * Handle if DTEND and DURATION are both missing * Improved FindICU (copied from official CMake) * Buildsystem fixes (especially for the Ninja generator) * Built-in timezones updated to tzdata2021e ==== libical-glib ==== Version update (3.0.11 -> 3.0.12) - update to 3.0.12: * Fix a libicalval crash in cleanVObject * METHOD:DECLINECOUNTER must have DTEND or DURATION * Handle if DTEND and DURATION are both missing * Improved FindICU (copied from official CMake) * Buildsystem fixes (especially for the Ninja generator) * Built-in timezones updated to tzdata2021e ==== netpbm ==== Subpackages: libnetpbm11 - signed-char.patch: fix bad use of plain char ==== python-SQLAlchemy ==== Version update (1.4.27 -> 1.4.29) - Update to 1.4.29: - truly, just plenty of small bugfixes, see the changelog on the Web https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.29 - update to 1.4.28: Bugfixes, see * https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.28 ==== python-incremental ==== - Do not use %{python_module ?} for suggests, as this would suggest all python flavors. Rather rely on the python singlespec macros to rewrite as needed. ==== python-setuptools ==== - Remove unzip BuildRequires: the tarball is proper gz compressed, no zip files to decompress here. ==== ruby ==== Version update (2.7 -> 3.0) - switch the default ruby to 3.0 ==== yast2-trans ==== Version update (84.87.20211219.ed0ba1e469 -> 84.87.20211227.623da84d84) Subpackages: yast2-trans-af yast2-trans-ar yast2-trans-bg yast2-trans-bn yast2-trans-bs yast2-trans-ca yast2-trans-cs yast2-trans-cy yast2-trans-da yast2-trans-de yast2-trans-el yast2-trans-en_GB yast2-trans-es yast2-trans-et yast2-trans-fa yast2-trans-fi yast2-trans-fr yast2-trans-gl yast2-trans-gu yast2-trans-hi yast2-trans-hr yast2-trans-hu yast2-trans-id yast2-trans-it yast2-trans-ja yast2-trans-jv yast2-trans-ka yast2-trans-km yast2-trans-ko yast2-trans-lo yast2-trans-lt yast2-trans-mk yast2-trans-mr yast2-trans-nb yast2-trans-nl yast2-trans-pa yast2-trans-pl yast2-trans-pt yast2-trans-pt_BR yast2-trans-ro yast2-trans-ru yast2-trans-si yast2-trans-sk yast2-trans-sl yast2-trans-sr yast2-trans-sv yast2-trans-ta yast2-trans-th yast2-trans-tr yast2-trans-uk yast2-trans-vi yast2-trans-wa yast2-trans-xh yast2-trans-zh_CN yast2-trans-zh_TW yast2-trans-zu - Update to version 84.87.20211227.623da84d84: * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Slovak) * New POT for text domain 'storage'. * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Catalan) * Translated using Weblate (Catalan) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Ukrainian) * Translated using Weblate (Japanese) * Translated using Weblate (Slovak) * New POT for text domain 'storage'. * New POT for text domain 'base'.

1 0

Python version and TW
by Frans de Boer 28 Dec '21

28 Dec '21

LS, TW should be a rolling release and has for the most part the latest version of packages. Alas, Python is not one of them. Python now is at version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one tries to cross-compile Python-3.10.1. It is not possible to do so because Python needs - by (bad?) design - a similar version major/minor version on the building machine. So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1? Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from the same issue, is there a workaround for Python? Regards, Frans.

4 4