September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201803] New: Building the grep tool for PCRE2 usage
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201803 Bug ID: 1201803 Summary: Building the grep tool for PCRE2 usage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The dependencies for the software package ��grep 3.7-4.1�� contain the information ��Requires: libpcre.so.1()(64bit)��. How are the chances to support the API ��PCRE2�� (with library versions �� 10.40)? https://github.com/PCRE2Project/pcre2 https://build.opensuse.org/package/view_file/openSUSE:Factory/grep/grep.spe… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201001] New: grep manpage slightly broken (contains some "tags" instead of rendered text)
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201001 Bug ID: 1201001 Summary: grep manpage slightly broken (contains some "tags" instead of rendered text) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: schwab(a)suse.de Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- man 1 grep contains -r, --recursive [...] Note that if no file operand is given, B<grep> searches [...] and Perl-compatible regular expressions give additional functionality, and are documented in B<pcresyntax>(3) and B<pcrepattern>(3), but Note the B<grep> and B<pcresyntax>(3) and B<pcrepattern>(3) parts, which should be rendered as grep and pcresyntax(3) and pcrepattern(3) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1168447] Please build Blender with OptiX support
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1168447 https://bugzilla.suse.com/show_bug.cgi?id=1168447#c11 --- Comment #11 from Christoph Feck <cfeck(a)kde.org> --- I see that package "nvidia-optix-headers" needs to be provided by the distribution in order to get an OptiX enabled build. There is no such package. If it is an issue to host the header file, other distributions (I only checked Arch) download the header during build time from NVIDIA servers. If this is not possible with openSUSE, please close as "wontfix". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202678] okular-lang not installed by default => only english language for a french installation
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202678 https://bugzilla.suse.com/show_bug.cgi?id=1202678#c10 --- Comment #10 from Episteme PROMENEUR <epistemepromeneur(a)free.fr> --- Created attachment 861345 --> https://bugzilla.suse.com/attachment.cgi?id=861345&action=edit log created by save_y2logs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202678] okular-lang not installed by default => only english language for a french installation
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202678 https://bugzilla.suse.com/show_bug.cgi?id=1202678#c9 --- Comment #9 from Michal Filka <mfilka(a)suse.com> --- (In reply to Episteme PROMENEUR from comment #8) > Created attachment 861071 [details] > Installation log I'm sorry but we don't need the save_y2logs script itself. We need you to run the script (as root). It collects various logs all around your system and packs it into a tarball. Resulting tarball is what needs to be attached here. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200752] [Build 20220620] selinux 3.4: chcat: No translation file found for domain: 'selinux-python'
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200752 https://bugzilla.suse.com/show_bug.cgi?id=1200752#c2 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Johannes Segitz <jsegitz(a)suse.com> --- fix is in Factory -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202676] setools: excessive python deps pulled in
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202676 https://bugzilla.suse.com/show_bug.cgi?id=1202676#c6 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #6 from Johannes Segitz <jsegitz(a)suse.com> --- change is in Factory -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203027] No way of setting mount points for btrfs subvolumes in YaST
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203027 https://bugzilla.suse.com/show_bug.cgi?id=1203027#c4 --- Comment #4 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Richard Brown from comment #3) > > Users should be able to define subvolumes just the same way the installer > already does. Actually they can. The current limitations are shared by the users and by the installer. As documented here[1] a subvolume in the control file is also limited to defining "path", "copy_on_write" and "archs". With the current implementation of libstorage-ng, the mount point of a subvolume is always auto-calculated from the mount point of the file-system and the path of the subvolume. That's one of the several things that would need to be changed in order to unleash all the potential for subvolume configuration. [1] https://github.com/yast/yast-installation/blob/master/doc/control-file.md#t… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199543] Please add libjxl for JPEG XL support
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199543 https://bugzilla.suse.com/show_bug.cgi?id=1199543#c3 --- Comment #3 from Christoph Feck <cfeck(a)kde.org> --- Ignore the first part of previous comment, the tools are in a separate package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199543] Please add libjxl for JPEG XL support
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199543 https://bugzilla.suse.com/show_bug.cgi?id=1199543#c2 --- Comment #2 from Christoph Feck <cfeck(a)kde.org> --- In the meantime, libjxl was added to the Tumbleweed distribution, thank you! Would be nice to also have the cjxl and djxl commands, but I downloaded nightly builds separately. Packages, however, do not enable libjxl: - kimageformats - krita - imagemagick - ffmpeg - digikam/kolourpaint/gwenview/okular/photoqt/qview (via kimageformats?) - gthumb (?) Should I report individually for each package to inform KDE/Qt maintainers? -- You are receiving this mail because: You are on the CC list for the bug.

1 0