February 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1078841] New: FTBFS: openSUSE:Factory/jack-rack fails to build
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078841 Bug ID: 1078841 Summary: FTBFS: openSUSE:Factory/jack-rack fails to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package jack-rack fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1078840] New: FTBFS: openSUSE:Factory/espresso fails to build
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078840 Bug ID: 1078840 Summary: FTBFS: openSUSE:Factory/espresso fails to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package espresso fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1078838] New: FTBFS: openSUSE:Factory/geda-gaf fails to build
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078838 Bug ID: 1078838 Summary: FTBFS: openSUSE:Factory/geda-gaf fails to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package geda-gaf fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1078815] New: Error when selecting Custom twice during User Interface selection
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078815 Bug ID: 1078815 Summary: Error when selecting Custom twice during User Interface selection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Macintosh OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wb_jerry(a)hotmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 Build Identifier: I am testing Leap build 115.1 on Virtualbox Version 5.2.6 r120293 and my OS version is mac OS High Sierra Version 10.13.3. During the installation when I am asked to select User Interface, if I select 'Custom' and click next, then click back to the User Interface selection, then click next again, an error would occur saying "SetOverlay called when old overlay was not cleared" Reproducible: Always Steps to Reproduce: 1.Boot using build 115.1 iso 2.proceed to User Interface, click 'Custom' then 'next' 3.Make no change to the software selection, click 'back' 4.Now you are back to the User Interface, and the selection should still be 'Custom'. Click 'next' again and an error will pop up. Actual Results: Error Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: SetOverlay called when old overlay was not cleared Caller: /mounts/mp_0001/usr/share/YaST2/modules/ProductFeature.rb:329: in 'SetOverlay' Expected Results: Should see software selection page again. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1078805] libstorage-ng autoyast PartitionImpl.cc:730 THROW
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078805 http://bugzilla.suse.com/show_bug.cgi?id=1078805#c2 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |bwiedemann(a)suse.com Flags| |needinfo?(bwiedemann(a)suse.c | |om) --- Comment #2 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Your profile includes this for the / partition <partition_id config:type="integer">24</partition_id> Which means the partition id of your main ext4 partition should be set to "AST Windows". Is that really what you wanted? I would say that's an error in the profile (it was probably just ignored by previous versions of AutoYaST). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078805] libstorage-ng autoyast PartitionImpl.cc:730 THROW
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078805 http://bugzilla.suse.com/show_bug.cgi?id=1078805#c1 --- Comment #1 from Arvin Schnell <aschnell(a)suse.com> --- Creating a partition and setting the ID to ID_UNKNOWN (256) does not work. AutoYaST must set it to some reasonable value. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078825] New: salt-ssh failing with Leap-15.0 client
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078825 Bug ID: 1078825 Summary: salt-ssh failing with Leap-15.0 client Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: All 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: bmaryniuk(a)suse.com Found By: Development Blocker: --- Steps To Reproduce: 1. have a Leap 15.0 machine to be managed 2. have a salt-ssh setup on a Leap 42.3 with salt-ssh-1511785846.8f81bee8d8-5.1.x86_64 3. # salt-ssh mkchb test.ping Actual Results: ... File "/var/tmp/.root_526868_salt/py2/salt/payload.py", line 17, in <module> import salt.crypt File "/var/tmp/.root_526868_salt/py2/salt/crypt.py", line 54, in <module> import salt.utils.rsax931 File "/var/tmp/.root_526868_salt/py2/salt/utils/rsax931.py", line 88, in <module> libcrypto = _init_libcrypto() File "/var/tmp/.root_526868_salt/py2/salt/utils/rsax931.py", line 79, in _init_libcrypto raise OSError("Failed to initialize OpenSSL library (OPENSSL_init_crypto failed)") OSError: Failed to initialize OpenSSL library (OPENSSL_init_crypto failed) by adding some debug code, I found that it uses libcrypto.so.1.1 and libcrypto.OPENSSL_init_crypto returns 0 instead of 1 maybe related to the openssl-1.1 switch? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1072651] New: [Build 20171212] openQA test fails in vim
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1072651 Bug ID: 1072651 Summary: [Build 20171212] openQA test fails in vim Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC URL: http://openqa.opensuse.org/tests/558616/modules/vim/st eps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the missing vim-data is probably related to the vim build failure https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/… ## Observation openQA test in scenario opensuse-Tumbleweed-NET-ppc64-minimalx@ppc64 fails in [vim](http://openqa.opensuse.org/tests/558616/modules/vim/steps/5) ## Reproducible Fails since (at least) Build [20171212](http://openqa.opensuse.org/tests/558616) (current job) ## Expected result Last good: [20171212](http://openqa.opensuse.org/tests/558356) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?distri=opensuse&flavor=NET&… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1078713] yast2 module bootloader internal error
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078713 http://bugzilla.suse.com/show_bug.cgi?id=1078713#c8 Sebastian Parschauer <sebastian.parschauer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sebastian.parscha | |uer(a)suse.com) | --- Comment #8 from Sebastian Parschauer <sebastian.parschauer(a)suse.com> --- (In reply to Josef Reidinger from comment #7) > Sebastion - are you aware about any such change that can make parted to stop > seeing this diagnostic partition? Nope. Parted does not magically delete it. Must have been deleted by another tool. The moving of the extended partition from #4 to #3 is not done by parted. When deleting #3 which starts at a sector after #4, then the extended partition stays at #4. I thought this might be related to BLKRRPART but deleting #3 with fdisk also doesn't move #4 to #3. Can't reproduce with parted or fdisk. The only explanation with parted would be deleting the extended partition as well and recreating it as #3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1071578] New: FTBFS: openSUSE:Factory/kadu fails to build
by bugzilla_noreply＠novell.com 01 Feb '18

01 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1071578 Bug ID: 1071578 Summary: FTBFS: openSUSE:Factory/kadu fails to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package kadu fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 2