July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193179] New: L3: Installing python3.9 in SLE image pulls in Python3.6 packages [ref:_00D1igLOd._5001iltVIZ:ref]
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193179 Bug ID: 1193179 Summary: L3: Installing python3.9 in SLE image pulls in Python3.6 packages [ref:_00D1igLOd._5001iltVIZ:ref] Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SLES 15 Status: NEW Keywords: DSLA_REQUIRED Severity: Major Priority: P5 - None Component: Basesystem Assignee: mcepl(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: andreas.taschner(a)suse.com, brent.griggs(a)suse.com, bugzilla-notif-sf(a)suse.com, dleuenberger(a)suse.com, mcepl(a)suse.com, nicola.dimarzo(a)suse.com, tabraham(a)suse.com Depends on: 1192249 Found By: Novell Technical Services Services Priority: 1000 Blocker: --- +++ This bug was initially created as a clone of Bug #1192249 +++ If one installs Python3.9 in a SLE 15 SP3 image from us, then the dependencies will bring in _both_ python 3.9 _and_ python3.6. According to the customer this looks like some kind of dependency issue towards /usr/bin/python that [in their opinion] looks wrong. The fact that 3.6 is the 'system default' python is no excuse since nothing else in the SLE images requires python .. Easily reproduced like this : - Run a SLES 15 SP3 image from registry.suse.com - (optional) remove the apparently no-good container-suseconnect tool that delays all zypper operations - Add Basesystem repos from your favourite mirror - zypper install python39 Example from my lab : dilirium:~ # docker run -it registry.suse.com/suse/sle15:15.3.17.8.25 bash d6f695acdf2f:/ # zypper rm -y container-suseconnect [...] d6f695acdf2f:/ # zypper ar -f http://172.30.44.1/repo/SUSE/Products/SLE-Module-Basesystem/15-SP3/x86_64/p… SLE-Module-Basesystem15-SP3-Pool [...] d6f695acdf2f:/ # zypper ar -f http://172.30.44.1/repo/SUSE/Updates/SLE-Module-Basesystem/15-SP3/x86_64/up… SLE-Module-Basesystem15-SP3-Updates [...] d6f695acdf2f:/ # rpm -qa | grep python d6f695acdf2f:/ # zypper -n in --no-recommends python39 [...] The following 7 NEW packages are going to be installed: libexpat1 libpython3_6m1_0 libpython3_9-1_0 python-rpm-macros python3-base python39 python39-base [...] (1/7) Installing: libexpat1-2.2.5-3.6.1.x86_64 ...................../-/..[done] (2/7) Installing: python-rpm-macros-20200207.5feb6c1-3.11.1.noarch ./-/..[done] (3/7) Installing: libpython3_6m1_0-3.6.13-10.3.1.x86_64 ............/-/..[done] (4/7) Installing: python3-base-3.6.13-10.3.1.x86_64 ................/-/..[done] (5/7) Installing: libpython3_9-1_0-3.9.6-4.3.3.x86_64 ............../-/..[done] (6/7) Installing: python39-base-3.9.6-4.3.3.x86_64 ................./-/..[done] (7/7) Installing: python39-3.9.6-4.3.4.x86_64 ....................../-/..[done] d6f695acdf2f:/ # rpm -qa | grep python | sort libpython3_6m1_0-3.6.13-10.3.1.x86_64 libpython3_9-1_0-3.9.6-4.3.3.x86_64 python-rpm-macros-20200207.5feb6c1-3.11.1.noarch python3-base-3.6.13-10.3.1.x86_64 python39-3.9.6-4.3.4.x86_64 python39-base-3.9.6-4.3.3.x86_64 d6f695acdf2f:/ # -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1190566] New: Python 3.6 does not include the compat fixes to work with OpenSSL 3.0.0
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1190566 Bug ID: 1190566 Summary: Python 3.6 does not include the compat fixes to work with OpenSSL 3.0.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: pmonrealgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Python 3.10, 3.9 and 3.8 have released the compatibility fixes to build and work with OpenSSL 3.0.0. But python 3.6 does not include these fixes and it seems that upstream is not going to port them to 3.6. Note that many packages fail to build due to this in the staging project where we are testing the OpenSSL 3.0.0 update: * https://build.opensuse.org/project/show/openSUSE:Factory:Staging:Gcc7 I'm not sure about the plans to keep 3.6 in Factory or not. But, if 3.6 is going to stay in Factory for long, it would be convenient to have these fixes also in Factory in that case. Here is the upstream bug for this task with all the required commits: * Make Python compatible with OpenSSL 3.0.0: https://bugs.python.org/issue38820 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1200977] The `shutdown -r now` leads effectivly to a halted system
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200977 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(werner(a)suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201371] New: nim fails tests on 1-core VM
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201371 Bug ID: 1201371 Summary: nim fails tests on 1-core VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: david.anes(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860101 --> http://bugzilla.opensuse.org/attachment.cgi?id=860101&action=edit build log While working on reproducible builds for openSUSE, I found that our nim package failed to build on 1-core VMs Steps to Reproduce: osc co openSUSE:Factory/nim && cd $_ osc build --vm-type=kvm -j1 --clean --noservice standard -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] transactional update: exit 1 without real indication
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 https://bugzilla.suse.com/show_bug.cgi?id=1201348#c2 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Flags| |needinfo?(fvogt(a)suse.com) --- Comment #2 from Dominique Leuenberger <dimstar(a)opensuse.org> --- @Fabien: you mentioned that you had a more recent image available that we could use for the update tests? This image in use is ~ 2 years old - half an eternity for a rolling distro. Having a more recent base might be close to reality -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] transactional update: exit 1 without real indication
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|iforster(a)suse.com |dimstar(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] transactional update: exit 1 without real indication
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 https://bugzilla.suse.com/show_bug.cgi?id=1201348#c1 --- Comment #1 from Ignaz Forster <iforster(a)suse.com> --- Debugging revealed that this is caused by a zypper segfault. The zypper segfault is independent of transactional-update and also happens when updating that old snapshot in read-write mode with zypper directly. Fabian's suspicion is that the crash is caused by a bug in zypper logging, which has been fixed for a while already... That doesn't help in this case however as the active zypper updating the packages is still the old version. Assigning back to Dominique for clarification on how to proceed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198744] New: salt incompatible with python-Jinja2 3.1
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198744 Bug ID: 1198744 Summary: salt incompatible with python-Jinja2 3.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Jinja2 is submitted to update from version 3.0 to 3.1.1 https://build.opensuse.org/request/show/965274 openQA detected salt being incompatible with this Jinja version in e.g https://openqa.opensuse.org/tests/2307654#step/salt/26 from jinja2 import BaseLoader, Markup, TemplateNotFound, nodes ImportError: cannot import name 'Markup' from 'jinja2' (/usr/lib/python3.8/site-packages/jinja2/__init__.py) The Jinja maintaner mentioned jinja2.Markup has been deprecated, use markupsafe.Markup instead. https://stackoverflow.com/questions/71645272/importerror-cannot-import-name… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201340] New: kalendarac daemon crashes after every reminder
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201340 Bug ID: 1201340 Summary: kalendarac daemon crashes after every reminder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: martin.doucha(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating KOrganizer to the latest version, the Kalendarac reminder daemon crashes every time I dismiss a reminder. Then I have to open KOrganizer to restart it, otherwise I won't get any further reminders. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1200583] FreeCAD Segfaults Opening Any Example (libc.so.6)
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200583 https://bugzilla.suse.com/show_bug.cgi?id=1200583#c12 --- Comment #12 from Adrian Schr�ter <adrian.schroeter(a)suse.com> --- I will look into this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0