December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205894] [MicroOS] automatic mount deletes directories
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205894 https://bugzilla.suse.com/show_bug.cgi?id=1205894#c4 --- Comment #4 from Ignaz Forster <iforster(a)suse.com> --- (In reply to Axel Braun from comment #2) > - that still does not justify that automount of /var deletes everything.... I'll have a look at it at least, though it's likely it will end up implementing Thorsten's suggestion to just abort if the complete /var is supposed to be bind mounted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205894] [MicroOS] automatic mount deletes directories
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205894 https://bugzilla.suse.com/show_bug.cgi?id=1205894#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Axel Braun from comment #2) > So we have 2 point: > - you are saying that /var/www is the wrong place - which is the right one? There is no correct one, this depends on the use case. But everything delivered by an RPM and outside /usr will create problems. > - that still does not justify that automount of /var deletes everything.... That the package does not follow FHS does not justify it, correct, but that you mount /var on a t-u system justifies that you loose data. That's unavoidable, as t-u needs /var but you overwrite it with an outdated version. That's why I suggested to Ignaz to abort with a hard error if somebody makes this mistake and to you to only mount /var/www, not complete /var. Between, I would not follow RHEL5 documentation, that's like following SLES10 or openSUSE 10.3 documentation, completely outdated. > Current location was triggered after the discussion in boo#1204307 And in this discussion I wrote that /var/www is the same bad idea then /srv/www. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205894] [MicroOS] automatic mount deletes directories
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205894 https://bugzilla.suse.com/show_bug.cgi?id=1205894#c2 --- Comment #2 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Thorsten Kukuk from comment #1) > Axel, the correct way would be to fix your RPM to be FHS conform (FHS > clearly states, that all data below /var will be generated at runtime of the > program, not installed by a package, and that the package can scope with the > fact, that somebody deletes the files in /var), the second best option is to > only mount /var/www, not full /var. The package maintainer is following upstream to install under /var/www/html > But all this broken packages will vanish hopefully quickly anyways, as they > don't work with any of the new concepts (e.g. see > https://www.uapi-group.org). (Certificate error) https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/ht… does IMO not deny to install in /var/www. Current location was triggered after the discussion in boo#1204307 So we have 2 point: - you are saying that /var/www is the wrong place - which is the right one? - that still does not justify that automount of /var deletes everything.... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203558] New: openSUSE support for Renesas RZ/G2M
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 Bug ID: 1203558 Summary: openSUSE support for Renesas RZ/G2M Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: duy.hua-duc(a)banvien.com.vn QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I need to install openSUSE to our chip but I realize that the openSUSE-Leap-15.4-DVD-aarch64-Build243.2-Media.iso does not support our GPU driver so I can't install it. + Document about our chip: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact… + This is our GPU driver: https://github.com/renesas-rz/rz_linux-cip/tree/rz-5.10-cip1-rt1/drivers/gp… -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1205766] FTBFS: sway needs wlroots <0.16.0
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205766 https://bugzilla.suse.com/show_bug.cgi?id=1205766#c9 --- Comment #9 from Michael Vetter <mvetter(a)suse.com> --- > So the solution with having an wlroots10 is actually nice. But those packages will only live a short time. Once sway, cage and other deps have migrated to the new version these old ones can die. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205766] FTBFS: sway needs wlroots <0.16.0
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205766 https://bugzilla.suse.com/show_bug.cgi?id=1205766#c8 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|sleep_walker(a)opensuse.org |mvetter(a)suse.com Flags| |needinfo?(llyyr.public@gmai | |l.com) --- Comment #8 from Michael Vetter <mvetter(a)suse.com> --- Sway is on it's way to Factory: https://build.opensuse.org/request/show/1039280 But I see https://build.opensuse.org/package/show/X11:Wayland/wlroots10 is not there yet, nor was a request sent. @llyyrr do you plan to do this and maintain it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205737] New: USB passthrough not working for Win 7 client in Virtualbox 7.04
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 Bug ID: 1205737 Summary: USB passthrough not working for Win 7 client in Virtualbox 7.04 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: timothyadams(a)ymail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863110 --> http://bugzilla.opensuse.org/attachment.cgi?id=863110&action=edit /var/log/virtualbox.log Symptoms are similar to those reported in Bug 1204331. https://bugzilla.opensuse.org/show_bug.cgi?id=1204331 When I start either of two USB scanners in the Win 7 client, I get the Windows error: * * * One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. The location of the device is shown in bold type. * USB Root hub (12 ports) - Unknown Device * * * As it may help in troubleshooting, I'd better mention that the 6.1.38 bug referred to in: https://forums.opensuse.org/showthread.php/576712-VirtualBox-with-enabled-U… was not present with 6.1.38 in kubuntu. In kubuntu, 6.1.38 passthrough worked fine. I need to use these scanners, so have restored an earlier snapshot and locked virtualbox files at version 6.1.40. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1205923] New: FTBFS: valgrind fails to build on ppc64
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205923 Bug ID: 1205923 Summary: FTBFS: valgrind fails to build on ppc64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The issue was identified while debugging https://bugzilla.opensuse.org/show_bug.cgi?id=1205401 https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/valgrind fails to build on ppc64 Build log available at https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205401] [Build 20221113] Error: Cannot update the dynamic configuration policy - no /sbin/netconfig
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205401 https://bugzilla.suse.com/show_bug.cgi?id=1205401#c14 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |scc-bugs(a)suse.de --- Comment #14 from Stefan Hundhammer <shundhammer(a)suse.com> --- Then AFAICS we need to start with suseconnect-ng to get all this untangled. Reassigning to the SCC team. SCC team: The part of this that is relevant for you is last part of comment #13: suseconnect-ng fails to build (-buildmode=c-shared not supported on linux/ppc64) * nothing provides glibc < 2.36 needed by valgrind > osc r openSUSE:Factory:PowerPC -r standard -a ppc64 -v valgrind standard ppc64 valgrind failed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205766] FTBFS: sway needs wlroots <0.16.0
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205766 https://bugzilla.suse.com/show_bug.cgi?id=1205766#c7 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter(a)suse.com --- Comment #7 from Michael Vetter <mvetter(a)suse.com> --- Hi guys, sorry for the late response. I was on vacation. > This was an oversight on my part when submitting the wlroots package. Actually it is every release the same dance :) Usually wlroots is released and each of their releases is incompatible since forever. Usually I'm in touch with the developers and package wlroots locally but don't submit it to Factory yet. Then after a couple of days/weeks they release the new sway which requires, and is only compatible, with the new wlroots. Earlier this was no problem since I was the only maintainer of these packages. Now more people seem to be interested and want to update it as soon as possible. Shortly before I was going on vacation I already had the wlroots update packaged but not submitted. When the submission came I decided to accept it (but intended not to forward it to Factory yet, so that was my mistake) to not discourage contributors. Pretty quickly after Sway put their underlying functions in the wlroots package other project started to use it. Which also leads to build fails on those projects since they are usually not so well coordinated with the release cycle of the sway/wlroots upstream projects. X11:Wayland/cage is such an example. (Someone opened a compat PR at https://github.com/Hjdskes/cage/pull/244 though, I'll have to look into that one). So the solution with having an wlroots10 is actually nice. I accepted https://build.opensuse.org/request/show/1039263 and declined https://build.opensuse.org/request/show/1038372 due to better solution + proper changelog now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0