October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191220] New Let's Encrypt certificate cannot be verify in Mono
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191220 https://bugzilla.suse.com/show_bug.cgi?id=1191220#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- https://defiant.thkukuk.de should return the SSL certificate chain from letsencrypt (currently does not seem to) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191220] New Let's Encrypt certificate cannot be verify in Mono
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191220 https://bugzilla.suse.com/show_bug.cgi?id=1191220#c2 --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- dup of bug 1190858 the letsencrypt ca expiry... openssl should handle it fine, but it depends on how the chain cert management -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191220] New Let's Encrypt certificate cannot be verify in Mono
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191220 https://bugzilla.suse.com/show_bug.cgi?id=1191220#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- This looks like the same problem as all non-webbrowser based tools we have: kukuk@f05:~> curl https://defiant.thkukuk.de curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. kukuk@f05:~> wget https://defiant.thkukuk.de --2021-10-01 13:26:31-- https://defiant.thkukuk.de/ Resolving defiant.thkukuk.de (defiant.thkukuk.de)... fd21:4d9a:50d0:b2ba:172:17:0:1, 172.17.0.1 Connecting to defiant.thkukuk.de (defiant.thkukuk.de)|fd21:4d9a:50d0:b2ba:172:17:0:1|:443... failed: Verbindungsaufbau abgelehnt. Connecting to defiant.thkukuk.de (defiant.thkukuk.de)|172.17.0.1|:443... connected. ERROR: cannot verify defiant.thkukuk.de's certificate, issued by ��CN=R3,O=Let's Encrypt,C=US��: Unable to locally verify the issuer's authority. To connect to defiant.thkukuk.de insecurely, use `--no-check-certificate'. Same if you use ldap, imap, or other tools with this certificate. firefox, chrome, other webbrowsers and Android have no problem, only non-webbrowsers on SLE15 SP3 and Tumbleweed. But e.g. Fedora and Ubuntu have the same problems, webbrowser works, wget/curl not. So no idea what's wrong here. There is an old bug report from me about this already for SLE15 somewhere. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174936] [doc] 6 Installation of Virtualization Components - Documentation does not mention differences between using Wicked and NetworkManager
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1174936 https://bugzilla.suse.com/show_bug.cgi?id=1174936#c6 Tom�� Ba��ant <tbazant(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS Flags| |needinfo?(jfehlig(a)suse.com) --- Comment #6 from Tom�� Ba��ant <tbazant(a)suse.com> --- To me this one boils down to creating a new section "Managing network bridges with YNetwork Manager" inspired by the section "Setting up a bridge with NetworkManager" at https://www.happyassassin.net/posts/2014/07/23/bridged-networking-for-libvi… @Jim, agree? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191025] New: openSUSE Leap 15.3 OBS KVM/Qemu image with old 15.1 repositories
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191025 Bug ID: 1191025 Summary: openSUSE Leap 15.3 OBS KVM/Qemu image with old 15.1 repositories Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: General Assignee: adrian.schroeter(a)suse.com Reporter: abergmann(a)suse.com QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- The qcow2 KVM/Qemu image has some issues with the defined channels. The system is running on openSUSE Leap 15.3, but the configured repositories are linked against openSUSE Leap 15.1. Download from: https://openbuildservice.org/download/other/ localhost:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.3" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.3" PRETTY_NAME="openSUSE Leap 15.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" localhost:~ # cat /etc/zypp/repos.d/openSUSE\:Leap\:15.1.repo [openSUSE:Leap:15.1] enabled=1 autorefresh=0 baseurl=http://download.opensuse.org/distribution/leap/15.1/repo/oss/ localhost:~ # cat /etc/zypp/repos.d/openSUSE\:Leap\:15.1\:Update.repo [openSUSE:Leap:15.1:Update] enabled=1 autorefresh=0 baseurl=http://download.opensuse.org/update/leap/15.1/oss/ localhost:~ # cat /etc/zypp/repos.d/OBS\:Server\:2.10.repo [OBS:Server:2.10] enabled=1 autorefresh=0 baseurl=http://download.opensuse.org/repositories/OBS:/Server:/2.10/openSUS… Only the backports and sle repositories are configured correctly. * repo-backports-debug-update - http://download.opensuse.org/update/leap/15.3/backports_debug/ * repo-backports-update - http://download.opensuse.org/update/leap/15.3/backports/ * repo-sle-debug-update - http://download.opensuse.org/debug/update/leap/15.3/sle/ * repo-sle-update - http://download.opensuse.org/update/leap/15.3/sle/ -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190369] New: obs returns incorrect repositiory data forcing all downloads through the API
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190369 Bug ID: 1190369 Summary: obs returns incorrect repositiory data forcing all downloads through the API Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: build process Assignee: mls(a)suse.com Reporter: william.brown(a)suse.com QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- I noticed that during builds with branched/devel packages, that all downloads were being forced through the OBS API. Examples are devel:languages:rust/rust and home:firstyear:branches:devel:languages:rust/rust. Observing the build XML (./.osc/_buildinfo-openSUSE_Tumbleweed-x86_64.xml) during a local osc build, I noted that repositories were set to "dod". IE: <bdep name="file" version="5.40" release="1.13" arch="x86_64" project="openSUSE:Tumbleweed" repository="dod"/> This causes the package to miss on the download URL, and then forces a full download from the API. However, doing an osc co openSUSE:Factory/<pkg> works correctly and returns valid repo locations (./.osc/_buildinfo-standard-x86_64.xml): <bdep name="libtevent-devel" version="0.10.2" release="1.7" arch="x86_64" project="openSUSE:Factory" repository="standard"/> I have previously been advised that using the API is not recommended due to load on OBS, so I'm wondering if this behaviour is a flaw or bug? -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1190628] Vagrant: ssh works, but rsync fails
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190628 https://bugzilla.suse.com/show_bug.cgi?id=1190628#c10 --- Comment #10 from Dan ��erm��k <dcermak(a)suse.com> --- (In reply to Damien Radtke from comment #9) > Ahh, I think what I'm seeing is an issue introduced in the latest release of > Vagrant. With this workaround, `vagrant rsync` worked for me: > https://github.com/hashicorp/vagrant/issues/12344#issuecomment-835386483 > > My guess then is that the other boxes I tried support SHA1, but the latest > releases of openSUSE don't, hence the connection error. > > Apologies for the noise! No worries at all! I'm very glad to see that people are using these :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189453] Broken readline support in libcom_err
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1189453 https://bugzilla.suse.com/show_bug.cgi?id=1189453#c5 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Jan Kara <jack(a)suse.com> --- The fix has landed in Factory. Closing the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190797] nls_utf8.ko is missing in Leap 15.3, although CONFIG_NLS_UTF8=m is set
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190797 https://bugzilla.suse.com/show_bug.cgi?id=1190797#c4 Akihiro Suda <suda.kyoto(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suda.kyoto@gmail. | |com) | --- Comment #4 from Akihiro Suda <suda.kyoto(a)gmail.com> --- (In reply to Fabian Vogt from comment #3) > According to > https://lore.kernel.org/lkml/20210808162453.1653-1-pali@kernel.org/, > nls_utf8 will probably be dropped in the future. It seems to be necessary > only for specific filesystems. Yes, I know, but the patch isn't merged into the upstream yet. > What's your use case which needs this module? Mounting SMB with non-ASCII file names. > I'll prepare SRs for TW and Leap. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190797] nls_utf8.ko is missing in Leap 15.3, although CONFIG_NLS_UTF8=m is set
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190797 https://bugzilla.suse.com/show_bug.cgi?id=1190797#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suda.kyoto(a)gmail.com Flags| |needinfo?(suda.kyoto@gmail. | |com) --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- According to https://lore.kernel.org/lkml/20210808162453.1653-1-pali@kernel.org/, nls_utf8 will probably be dropped in the future. It seems to be necessary only for specific filesystems. What's your use case which needs this module? I'll prepare SRs for TW and Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 0