February 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 940478] New: ASL: rename conflicting-confusing package
by bugzilla_noreply＠novell.com 14 Jan '22

14 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=940478 Bug ID: 940478 Summary: ASL: rename conflicting-confusing package Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: alinm.elena(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Factory already has an "asl" package, and recently gained an "ASL" package. This very same name is, I will argue, confusing for both users and developers, as they only differ in case, and case is not something people pay sufficient attention to when e.g. reporting bugs or discussing. I suggest to rename the ASL package. Considering that "asl library" yields lots of different things on Google already, a package name like "advsimlib" might work better than "asllib". Confer with the asl.org.il team perhaps. [ The current plan is to reject, in the direct future, same-name submissions to Factory which only differ in casing. On a related notem, libzypp even falls over currently (but probably intentionally; see bug #940477). ] -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1060506] New: libkolabxml packages differ for every build
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1060506 Bug ID: 1060506 Summary: libkolabxml packages differ for every build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lbeltrame(a)kde.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matthias(a)mailaender.name Found By: Development Blocker: --- When working on the reproducible builds project for openSUSE I found that libkolabxml packages differ for every build unless ASLR is disabled in the build system. This indicates either usage of unitinialized memory (compare [1]) or using (randomized) pointers in output. /usr/lib64/libkolabxml.so.1.1.6 differs because of /home/abuild/rpmbuild/BUILD/libkolabxml-1.1.6/build/kolabformat-xcal-schema.cxx 2018-10-30 08:42:53.622040000 +0000 @@ -9014,9 +9014,9 @@ 0x00, 0x01, 0x6d, 0x09, 0x00, 0x01, 0x3f, 0x07, 0x00, 0x01, 0x23, 0x07, 0x00, 0x01, 0x53, 0x0a, 0x00, 0x01, 0x68, 0x07, 0x00, 0x01, 0x7f, 0x09, 0x00, 0x01, 0x4e, 0x04, 0x00, 0x01, 0xfe, 0xff, 0xff, 0xff, 0x1d, 0x00, - 0x06, 0x0e, 0x00, 0x06, 0xe8, 0x08, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, + 0x06, 0x0e, 0x00, 0x06, 0x25, 0x07, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0x00, 0x03, 0x0c, 0x00, 0x06, 0x58, 0x53, 0x41, 0x6e, 0x6e, 0x6f, 0x74, - 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0x11, 0x09, 0x00, 0x05, 0x3c, + 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0xb6, 0x01, 0x00, 0x05, 0x3c, 0x00, 0xff, 0x78, 0x73, 0x3a, 0x61, 0x6e, 0x6e, 0x6f, 0x74, 0x61, 0x74, [...] which probably comes from # Compile Schemas add_custom_command(OUTPUT kolabformat-xcal-schema.cxx COMMAND ${XSDBIN} --verbose --array-name iCalendar_schema --output-dir ${CMAKE_BINARY_DIR} ${SCHEMAS} which might be from ./compiled/xsdbin.cxx and/or involving the xsd package [1] https://build.opensuse.org/package/view_file/M17N/gcin/gcin-reproducible.pa… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061219] New: trackerbug: packages do not build reproducibly from including uninitialized memory
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1061219 Bug ID: 1061219 Summary: trackerbug: packages do not build reproducibly from including uninitialized memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write uninitialized memory into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1060111] New: bash: have: command not found
by bugzilla_noreply＠novell.com 30 Dec '21

30 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1060111 Bug ID: 1060111 Summary: bash: have: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just encountered this in openSUSE Tumbleweed where every terminal displays > bash: have: command not found upon startup. http://www.jerous.org/2016/09/19/bash-have-not-found describes the problem and proposes a solution. I don't know if it is the correct approach. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 997918] New: TW 20160901: unable to dup since docker-compose conflicts with python-requests
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=997918 Bug ID: 997918 Summary: TW 20160901: unable to dup since docker-compose conflicts with python-requests Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: fcastelli(a)suse.com Found By: --- Blocker: --- Another iteration of bug #984309 Problem: docker-compose-1.7.1-2.2.noarch conflicts with python-requests >= 2.11 provided by python-requests-2.11.1-1.1.noarch Solution 1: deinstallation of docker-compose-1.7.1-2.2.noarch Solution 2: keep obsolete python-requests-2.10.0-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1072403] New: [Build 20171211] openQA test fails in docker_compose
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1072403 Bug ID: 1072403 Summary: [Build 20171211] openQA test fails in docker_compose Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/557372/modules/docker _compose/steps/14 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_in_textmode@64bit fails in [docker_compose](http://openqa.opensuse.org/tests/557372/modules/docker_comp… ## Reproducible Fails since (at least) Build [20170428](http://openqa.opensuse.org/tests/395051) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?test=extra_tests_in_textmod… docker-compose is no longer installable, as python-texttable has been updated to version 1.1.1 (from 0.8.3) in sr 555176 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1062084] New: docker-compose broken because of python-docker-py
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1062084 Bug ID: 1062084 Summary: docker-compose broken because of python-docker-py Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker-compose broke after the last update, because of a broken dependancy on python-docker-py. % sudo zypper in docker-compose Chargement des données du dépôt... Lecture des paquets installés... Résolution des dépendances des paquets... Problème : rien ne fournit python-docker-py >= 1.10.3, qui est requis par docker-compose-1.8.1-1.2.noarch Solution 1 : ne pas installer docker-compose-1.8.1-1.2.noarch Solution 2 : casser docker-compose-1.8.1-1.2.noarch en ignorant certaines de ses dépendances % zypper info python-dockerpty Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet python-dockerpty : ------------------------------------------ Dépôt : openSUSE:Tumbleweed Nom : python-dockerpty Version : 0.4.1-1.3 Arch : noarch Fabricant : openSUSE Taille une fois installé : 78,6 KiB installé : Non État : non installé Paquet source : python-dockerpty-0.4.1-1.3.src Résumé : Docker API Client Description : Provides the functionality needed to operate the pseudo-tty (PTY) allocated to a docker container, using the Python client. % zypper info docker-compose Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet docker-compose : ---------------------------------------- Dépôt : openSUSE:Tumbleweed Nom : docker-compose Version : 1.8.1-1.2 Arch : noarch Fabricant : openSUSE Taille une fois installé : 512,9 KiB installé : Non État : non installé Paquet source : docker-compose-1.8.1-1.2.src Résumé : Define and run complex applications using Docker Description : Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. Compose is great for development environments, staging servers, and CI. We don't recommend that you use it in production yet. Previously known as Fig. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1004927] New: Upgrade to docker-compose 1.8.1
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004927 Bug ID: 1004927 Summary: Upgrade to docker-compose 1.8.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker in Leap 42.2 was updated to 1.12, but docker-compose, which can use new capabilities stuck on version 1.6.1. Please update docker-compose too. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1027448] New: Please use key release event for bracket completion plugin
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1027448 Bug ID: 1027448 Summary: Please use key release event for bracket completion plugin Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 715892 --> http://bugzilla.opensuse.org/attachment.cgi?id=715892&action=edit bracketcompletion: use key release event to work with input method From: bgo#778737 https://bugzilla.gnome.org/show_bug.cgi?id=778737 Some user reported that ibus-libpinyin/ibus-pinyin doesn't work with gedit plugin bracket completion. I tried to modify the gedit plugin code, it seems work now. Please review it, thanks! How to reproduce it: 1. Switch to C/C++ mode, press "(", bracket completion works. 2. Switch input method to "Intelligent Pinyin" or "Pinyin", it doesn't work. -- You are receiving this mail because: You are on the CC list for the bug.

2 7