June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1050653] New: python3.6 should provide python3-typing (python-Sphinx concerned)
by bugzilla_noreply＠novell.com 22 Oct '21

22 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1050653 Bug ID: 1050653 Summary: python3.6 should provide python3-typing (python-Sphinx concerned) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since version 3.5 python3 is providing python3-typing. python3-typing has be deleted or not present in Tumbleweed. python3-Sphinx (1.6.3) in d:l:p can't be build due to lack of python3-typing python3-Sphinx 1.5.2 is still available and installable in TW (oss). Suggestion was made to have python3.5+ providing python3-typing -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1049186] New: python-3.6 packages do not build reproducibly
by bugzilla_noreply＠novell.com 22 Oct '21

22 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 Bug ID: 1049186 Summary: python-3.6 packages do not build reproducibly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jmatejek(a)suse.com Found By: Development Blocker: --- e.g. python-simplejson has one-bit diffs in .pyc files See http://rb.zq1.de/compare.factory-20170713/python-simplejson-compare.out in python3-simplejson.rpm we get -00004e50 68 6f 72 5f 5f da 07 64 65 63 69 6d 61 6c 72 0c |hor__..decimalr.| +00004e50 68 6f 72 5f 5f 5a 07 64 65 63 69 6d 61 6c 72 0c |hor__Z.decimalr.| in python3-simplejson-test.rpm we get the opposite change -00000580 72 13 00 00 00 5a 07 64 65 63 69 6d 61 6c 72 03 |r....Z.decimalr.| +00000580 72 13 00 00 00 da 07 64 65 63 69 6d 61 6c 72 03 |r......decimalr.| and it seems to be related to filesystem ordering, since it built reproducibly when using a filesystem with sorted readdir using disorderfs via reproducible-faketools-filesys from https://build.opensuse.org/package/show/home:bmwiedemann:reproducible/repro… -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1013563] New: dell 7470 - cpu gets throttled a lot
by bugzilla_noreply＠novell.com 20 Oct '21

20 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1013563 Bug ID: 1013563 Summary: dell 7470 - cpu gets throttled a lot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With a normal usage, on table, browsing+ssh the machine quite often throtlles: [39814.739914] mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not register event ret=-22 [39814.741816] mei_wdt: probe of mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02 failed with error -22 [39867.021572] CPU3: Core temperature above threshold, cpu clock throttled (total events = 1355) [39867.021573] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1355) [39867.021574] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1355) [39867.021575] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1355) [39867.021576] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1355) [39867.021580] mce_notify_irq: 1 callbacks suppressed [39867.021581] mce: [Hardware Error]: Machine check events logged [39867.021583] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1355) [39867.021585] mce: [Hardware Error]: Machine check events logged [39867.022565] CPU1: Core temperature/speed normal [39867.022566] CPU3: Core temperature/speed normal [39867.022567] CPU0: Package temperature/speed normal [39867.022567] CPU2: Package temperature/speed normal [39867.022568] CPU3: Package temperature/speed normal [39867.022569] CPU1: Package temperature/speed normal -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1124198] New: ca-certificates-mozilla fail at update
by bugzilla_noreply＠novell.com 20 Oct '21

20 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124198 Bug ID: 1124198 Summary: ca-certificates-mozilla fail at update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: tbro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While upgrading rsync.opensuse.org to the latest updates with zypper dup, I found the following bug: ( 2/58) Install: ca-certificates-mozilla-2.30-lp150.3.9.1.noarch .....................................................................[ready] Additional output rpm: p11-kit: couldn't create symlink: /var/lib/ca-certificates/pem/57bcb2da.0: File exists Died at /usr/lib/ca-certificates/update.d/80etc_ssl.run line 87. maybe somebody can look into this :). Thanks. Maybe somebody bumped ca-certificates-mozilla but didn't bump ca-certificates =) Additional information: Information for package ca-certificates-mozilla: ------------------------------------------------ Repository : Hauptaktualisierungs-Repository Name : ca-certificates-mozilla Version : 2.30-lp150.3.9.1 Arch : noarch Vendor : openSUSE Installed Size : 282.1 KiB Installed : Yes (automatically) Status : up-to-date Source package : ca-certificates-mozilla-2.30-lp150.3.9.1.src Summary : CA certificates for OpenSSL Description : This package contains some CA root certificates for OpenSSL extracted from MozillaFirefox # rpm -qf /usr/lib/ca-certificates/update.d/80etc_ssl.run ca-certificates-2+git20170807.10b2785-lp150.6.3.1.noarch Information for package ca-certificates: ---------------------------------------- Repository : Hauptaktualisierungs-Repository Name : ca-certificates Version : 2+git20170807.10b2785-lp150.6.3.1 Arch : noarch Vendor : openSUSE Installed Size : 28.0 KiB Installed : Yes (automatically) Status : up-to-date Source package : ca-certificates-2+git20170807.10b2785-lp150.6.3.1.src Summary : Utilities for system wide CA certificate installation Description : Update-ca-certificates is intended to keep the certificate stores of SSL libraries like OpenSSL or GnuTLS in sync with the system's CA certificate store that is managed by p11-kit. # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.0" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.0" PRETTY_NAME="openSUSE Leap 15.0" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.0" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1102563] New: [Build 20180722] openQA test fails in first_boot
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 Bug ID: 1102563 Summary: [Build 20180722] openQA test fails in first_boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/711960/modules/first _boot/steps/21 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-create_hdd_gnome@aarch64 fails in [first_boot](https://openqa.opensuse.org/tests/711960/modules/first_boot/ste… The autologin for GNOME is broken on AArch64, whereas it is fine for x86_64. ## Reproducible Fails since (at least) Build [20180603](https://openqa.opensuse.org/tests/686547) ## Expected result Last good: [20180530](https://openqa.opensuse.org/tests/685290) (or more recent) Autologin should work also for AArch64 as it did previously. ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?test=create_hdd_gnome&flav… -- You are receiving this mail because: You are on the CC list for the bug.

2 30

[Bug 1137216] New: ovmf package misses binaries signed with keys for secureboot testing
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1137216 Bug ID: 1137216 Summary: ovmf package misses binaries signed with keys for secureboot testing Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ovmf package in Leap15.1/SLE15-SP1 misses binaries signed with keys for secureboot testing. The required update is https://build.opensuse.org/request/show/701042 While at it, we should add this update https://build.opensuse.org/request/show/686880 to fix aarch32 packaging. Could we add those updates for :Update, please? -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1134788] New: HiKey960 not booting into EDK2 after edk2 and arm-trusted-firmware updates
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134788 Bug ID: 1134788 Summary: HiKey960 not booting into EDK2 after edk2 and arm-trusted-firmware updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: All Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: guillaume.gardet(a)arm.com Reporter: afaerber(a)suse.com QA Contact: jsrain(a)suse.com CC: dmueller(a)suse.com Found By: --- Blocker: --- hardware:boot/{l-loader,arm-trusted-firmware}-hikey960 are no longer properly booting after Guillaume's replacement of my downstream edk2-hikey960 package and update of arm-trusted-firmware package. New serial output: NOTICE: BL2: v2.1(debug): NOTICE: BL2: Built : 13:51:40OURCE, Apr 9 2019 INFO: BL2: Doing platform setup INFO: UFS LUN0 contains 1024 blocks with 4096-byte size INFO: UFS LUN1 contains 1024 blocks with 4096-byte size INFO: UFS LUN2 contains 2048 blocks with 4096-byte size INFO: UFS LUN3 contains 7805952 blocks with 4096-byte size INFO: ufs: change power mode success INFO: BL2: Loading image id 2 INFO: Loading image id=2 at address 0x89c80000 INFO: Image id=2 loaded: 0x89c80000 - 0x89cb5100 INFO: BL2: Initiating SCP_BL2 transfer to SCP INFO: BL2: SCP_BL2: 0x89c80000@0x35100 INFO: BL2: SCP_BL2 HEAD: INFO: BL2: SCP_BL2 0x7000 0x179 0x159 0x149 INFO: BL2: SCP_BL2 0x189 0x18b 0x18d 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x18f INFO: BL2: SCP_BL2 0x191 0x0 0x193 0x195 INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x4d454355 0x43494741 0x424d554e 0x21215245 INFO: BL2: SCP_BL2 0x4a054904 0x42912000 0xf841bfbc 0xe7fa0b04 INFO: BL2: SCP_BL2 0xb88cf000 0x3b18 0x3d1c 0x6809493e INFO: BL2: SCP_BL2 0x4613680a 0x201f102 0xf0002a04 0x600a804c INFO: BL2: SCP_BL2 0x204f04f 0xf203fb02 0xf102440a 0x60100204 INFO: BL2: SCP_BL2 0x160f04f 0xf103fb01 0x68004834 0x61044408 INFO: BL2: SCP_BL2 0x61866145 0xf8c061c7 0xf8c08020 0xf8c09024 INFO: BL2: SCP_BL2 0xf8c0a028 0xf3efb02c 0xf3ef8208 0x68118309 INFO: BL2: SCP_BL2 0xf1026401 0xf0110204 0xbf070f04 0x46113220 INFO: BL2: SCP_BL2 TAIL: INFO: BL2: SCP_BL2 0x19cad091 0x19cad091 0x19cad5a9 0x19cad0ed INFO: BL2: SCP_BL2 0x19cad195 0x19cad1cd 0x19cad001 0x19cad2e5 INFO: BL2: SCP_BL2 0x19cad003 0x19cad209 0x0 0x19cad6a9 INFO: BL2: SCP_BL2 0x19cad469 0x19cad27d 0x19cad2b9 0x19cad005 INFO: BL2: SCP_BL2 0x19cad17d 0x19cad7e9 0x19cad809 0x19cad9a5 INFO: BL2: SCP_BL2 0x19cad015 0x19cad049 0x19b80040 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 transferred to SCP INFO: start fw loading INFO: fw load success WARNING: BL2: Platform setup already done!! INFO: BL2: Loading image id 3 INFO: Loading image id=3 at address 0x1ac58000 INFO: Image id=3 loaded: 0x1ac58000 - 0x1ac63024 INFO: BL2: Loading image id 4 INFO: Loading image id=4 at address 0x3f000000 INFO: Image id=4 loaded: 0x3f000000 - 0x3f00001c INFO: OPTEE ep=0x3f000000 INFO: OPTEE header info: INFO: magic=0x4554504f INFO: version=0x2 INFO: arch=0x1 INFO: flags=0x0 INFO: nb_images=0x1 INFO: BL2: Loading image id 21 INFO: Loading image id=21 at address 0x3f000000 INFO: Image id=21 loaded: 0x3f000000 - 0x3f044270 INFO: BL2: Skip loading image id 22 INFO: BL2: Loading image id 5 INFO: Loading image id=5 at address 0x1ac98000 INFO: Image id=5 loaded: 0x1ac98000 - 0x1ad88000 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0x1ac58000 INFO: SPSR = 0x3cd NOTICE: BL31: v2.1(debug): NOTICE: BL31: Built : 13:51:40OURCE, Apr 9 2019 INFO: ARM GICv2 driver initialized Previous output: NOTICE: BL2: v1.5(debug): NOTICE: BL2: Built : 18:48:01OURCE, Jun 3 2018 INFO: BL2: Doing platform setup INFO: UFS LUN0 contains 1024 blocks with 4096-byte size INFO: UFS LUN1 contains 1024 blocks with 4096-byte size INFO: UFS LUN2 contains 2048 blocks with 4096-byte size INFO: UFS LUN3 contains 7805952 blocks with 4096-byte size INFO: ufs: change power mode success INFO: BL2: Loading image id 2 INFO: Loading image id=2 at address 0x89c80000 INFO: Image id=2 loaded: 0x89c80000 - 0x89cb5100 INFO: BL2: Initiating SCP_BL2 transfer to SCP INFO: BL2: SCP_BL2: 0x89c80000@0x35100 INFO: BL2: SCP_BL2 HEAD: INFO: BL2: SCP_BL2 0x7000 0x179 0x159 0x149 INFO: BL2: SCP_BL2 0x189 0x18b 0x18d 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x18f INFO: BL2: SCP_BL2 0x191 0x0 0x193 0x195 INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x4d454355 0x43494741 0x424d554e 0x21215245 INFO: BL2: SCP_BL2 0x4a054904 0x42912000 0xf841bfbc 0xe7fa0b04 INFO: BL2: SCP_BL2 0xb88cf000 0x3b18 0x3d1c 0x6809493e INFO: BL2: SCP_BL2 0x4613680a 0x201f102 0xf0002a04 0x600a804c INFO: BL2: SCP_BL2 0x204f04f 0xf203fb02 0xf102440a 0x60100204 INFO: BL2: SCP_BL2 0x160f04f 0xf103fb01 0x68004834 0x61044408 INFO: BL2: SCP_BL2 0x61866145 0xf8c061c7 0xf8c08020 0xf8c09024 INFO: BL2: SCP_BL2 0xf8c0a028 0xf3efb02c 0xf3ef8208 0x68118309 INFO: BL2: SCP_BL2 0xf1026401 0xf0110204 0xbf070f04 0x46113220 INFO: BL2: SCP_BL2 TAIL: INFO: BL2: SCP_BL2 0x19cad091 0x19cad091 0x19cad5a9 0x19cad0ed INFO: BL2: SCP_BL2 0x19cad195 0x19cad1cd 0x19cad001 0x19cad2e5 INFO: BL2: SCP_BL2 0x19cad003 0x19cad209 0x0 0x19cad6a9 INFO: BL2: SCP_BL2 0x19cad469 0x19cad27d 0x19cad2b9 0x19cad005 INFO: BL2: SCP_BL2 0x19cad17d 0x19cad7e9 0x19cad809 0x19cad9a5 INFO: BL2: SCP_BL2 0x19cad015 0x19cad049 0x19b80040 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 transferred to SCP INFO: start fw loading INFO: fw load success WARNING: BL2: Platform setup already done!! INFO: BL2: Loading image id 3 INFO: Loading image id=3 at address 0x1ac58000 INFO: Image id=3 loaded: 0x1ac58000 - 0x1ac63028 INFO: BL2: Loading image id 4 INFO: Loading image id=4 at address 0x3f000000 INFO: Image id=4 loaded: 0x3f000000 - 0x3f00001c INFO: OPTEE ep=0x3f000000 INFO: OPTEE header info: INFO: magic=0x4554504f INFO: version=0x2 INFO: arch=0x1 INFO: flags=0x0 INFO: nb_images=0x1 INFO: BL2: Loading image id 21 INFO: Loading image id=21 at address 0x3f000000 INFO: Image id=21 loaded: 0x3f000000 - 0x3f045270 INFO: BL2: Skip loading image id 22 INFO: BL2: Loading image id 5 INFO: Loading image id=5 at address 0x1ac98000 INFO: Image id=5 loaded: 0x1ac98000 - 0x1ad88000 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0x1ac58000 INFO: SPSR = 0x3cd NOTICE: BL31: v1.5(debug): NOTICE: BL31: Built : 18:48:01OURCE, Jun 3 2018 WARNING: Using deprecated integer interrupt array in gicv2_driver_data_t WARNING: Please migrate to using an interrupt_prop_t array INFO: ARM GICv2 driver initialized INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 835769 was missing! INFO: BL31: cortex_a53: CPU workaround for 843419 was applied INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: plat_setup_psci_ops: INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x1ac98000 INFO: SPSR = 0x3c9 UEFI firmware (version Alpha built at 12:00:00 on May 31 2018) -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1134533] New: The emergency shell does not show the "Welcome" message
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134533 Bug ID: 1134533 Summary: The emergency shell does not show the "Welcome" message Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In openQA, when 'systemctl rescue' is executed, the emergency shell does not show the "Welcome" message: "You are in Rescue mode. After login..." Before "Give root password for maintenance" message. See https://openqa.opensuse.org/tests/928446#step/snapper_undochange/23 and https://openqa.opensuse.org/tests/928446#step/snapper_thin_lvm/58 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1124940] New: ghc-bootstrap fails to build for Leap 15.x for ARM
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124940 Bug ID: 1124940 Summary: ghc-bootstrap fails to build for Leap 15.x for ARM Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Check 15.1:ARM (armv7 and aarch64) build failures on: https://build.opensuse.org/package/show/openSUSE:Leap:15.1:ARM/ghc-bootstrap The problem is that pre-built binaries require glibc 2.27 and Leap 15.x has only glibc 2.26 So, ghc is now unresolvable on Leap 15.1:ARM -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1112433] New: file /usr/bin/embedspu conflicts between attempted installs of sdcc-3.6.0-lp151.3.2.ppc64le and binutils-2.29.1-lp151.5.2.ppc64le
by bugzilla_noreply＠novell.com 17 Oct '21

17 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1112433 Bug ID: 1112433 Summary: file /usr/bin/embedspu conflicts between attempted installs of sdcc-3.6.0-lp151.3.2.ppc64le and binutils-2.29.1-lp151.5.2.ppc64le Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Is the embedspu from binutils sufficient or is the one from sdcc different? -- You are receiving this mail because: You are on the CC list for the bug.

2 11