--17085984301.c0A90f6C.9161
Date: Thu, 22 Feb 2024 10:40:30 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220195

            Bug ID: 1220195
           Summary: Embedded Perl Interpreter Messes up Locale Environment of Calling Process
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: shundhammer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since about the summer of 2023, the Perl version that comes with Tumbleweed
changes the locale environment of a process initializing an embedded Perl
interpreter to use only 7-bit ASCII (encoding "ANSI_X3.4-1968"), so special
characters in languages like Japanese, German, Czech (and probably many mor=
e)
are broken: They are replaced by a question mark '?' each.

This affects GNU gettext translations as well as file output.

We experienced this in YaST, where it was reported as bug #1216689, and it =
was
only after months of investigation and about 100 comments in Bugzilla that =
we
found the cause.

In our case, the symptom was that messages from libstorage-ng and from Perl
modules had broken special characters, but those from our embedded Ruby, fr=
om
the Qt UI and from the NCurses UI were correct.

We finally found a workaround that appears to work for us: After initializi=
ng
the embedded Perl interpreter, we are now switching back to the global loca=
le
with

  uselocale( LC_GLOBAL_LOCALE );

For a summary and some screenshots, see the PR with this fix:

  https://github.com/yast/yast-perl-bindings/pull/31

More details at the original bug #1216689.

We found that there was a major difference in the Perl source code's locale=
.c
between the versions we have in Leap 15.5 and recent Tumbleweed. We could
roughly it down to sometime between perl-5.26.1 (Leap 15.5) not showing the
problem and perl-38.2 (TW from 02/2024) where it definitely appears, probab=
ly
perl-36 as well.

The perl change log says they improved the locale handling for multi-thread=
ing;
that might be where this started.

We are not sure if this is an issue for just using Perl in the regular mode
(not as an embedded interpreter); we had the symptoms in our Perl code using
GNU gettext translations as well.

I will attach some minimalistic test programs for easier investigation.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17085984301.c0A90f6C.9161
Date: Thu, 22 Feb 2024 10:40:30 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220195

          Summary
          Embedded Perl Interpreter Messes up Locale Environment of Cal=
ling Process

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          shundhammer@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since about the summer of 2023, the Perl version that comes =
with Tumbleweed
changes the locale environment of a process initializing an embedded Perl
interpreter to use only 7-bit ASCII (encoding "ANSI_X3.4-1968"), =
so special
characters in languages like Japanese, German, Czech (and probably many mor=
e)
are broken: They are replaced by a question mark '?' each.

This affects GNU gettext translations as well as file output.

We experienced this in YaST, where it was reported as bug #1216689, and it was
only after months of investigation and about 100 comments in Bugzilla that =
we
found the cause.

In our case, the symptom was that messages from libstorage-ng and from Perl
modules had broken special characters, but those from our embedded Ruby, fr=
om
the Qt UI and from the NCurses UI were correct.

We finally found a workaround that appears to work for us: After initializi=
ng
the embedded Perl interpreter, we are now switching back to the global loca=
le
with

  uselocale( LC_GLOBAL_LOCALE );

For a summary and some screenshots, see the PR with this fix:

  https://gi=
thub.com/yast/yast-perl-bindings/pull/31

More details at the original bug #1216689.

We found that there was a major difference in the Perl source code's locale=
.c
between the versions we have in Leap 15.5 and recent Tumbleweed. We could
roughly it down to sometime between perl-5.26.1 (Leap 15.5) not showing the
problem and perl-38.2 (TW from 02/2024) where it definitely appears, probab=
ly
perl-36 as well.

The perl change log says they improved the locale handling for multi-thread=
ing;
that might be where this started.

We are not sure if this is an issue for just using Perl in the regular mode
(not as an embedded interpreter); we had the symptoms in our Perl code using
GNU gettext translations as well.

I will attach some minimalistic test programs for easier investigation.</pr=
e>

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17085984301.c0A90f6C.9161--


--17086801953.3A98.11159
Date: Fri, 23 Feb 2024 09:23:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220249

            Bug ID: 1220249
           Summary: E: pam-file-unauthorized (Badness: 10) /usr/lib64/security/pam_systemd_loadkey.so
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hi Secteam,

This new PAM module introduced in systemd v255 needs to be reviewed.

Here's the full warning:

> [  369s] systemd.x86_64: E: pam-file-unauthorized (Badness: 10) /usr/lib6=
4/security/pam_systemd_loadkey.so (sha256 file digest default filter:774e32=
bca722bc244bab2cc24e6a5d30b6c5a222c7081ea31259972317fedbb9 shell filter:<fa=
iled-to-calculate> xml filter:<failed-to-calculate>)
> [  369s] Packaging new PAM modules requires a review and whitelisting by =
the SUSE
> [  369s] security team. If the package is intended for inclusion in any S=
USE product
> [  369s] please open a bug report to request review of the package by the=
 security
> [  369s] team.

And a description of functionality brought by this new PAM module can be fo=
und
in the NEWS file:

  * A new pam_systemd_loadkey.so PAM module is now available, which will
    automatically fetch the passphrase used by cryptsetup to unlock the
    root file system and set it as the PAM authtok. This enables, among
    other things, configuring auto-unlock of the GNOME Keyring / KDE
    Wallet when autologin is configured.

Note that the PAM module is not yet integrated in the spec file so it's not
automatically added on package installation/update.

Thanks.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17086801953.3A98.11159
Date: Fri, 23 Feb 2024 09:23:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220249

          Summary
          E: pam-file-unauthorized (Badness: 10) /usr/lib64/security/pa=
m_systemd_loadkey.so

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          fbui@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hi Secteam,

This new PAM module introduced in systemd v255 needs to be reviewed.

Here's the full warning:

> [  369s] systemd.x86_64: E: pam-file-unauthorize=
d (Badness: 10) /usr/lib64/security/pam_systemd_loadkey.so (sha256 file dig=
est default filter:774e32bca722bc244bab2cc24e6a5d30b6c5a222c7081ea312599723=
17fedbb9 shell filter:<failed-to-calculate> xml filter:<failed-to-=
calculate>)
> [  369s] Packaging new PAM modules requires a review and whitelisting =
by the SUSE
> [  369s] security team. If the package is intended for inclusion in an=
y SUSE product
> [  369s] please open a bug report to request review of the package by =
the security
> [  369s] team.

And a description of functionality brought by this new PAM module can be fo=
und
in the NEWS file:

  * A new pam_systemd_loadkey.so PAM module is now available, which will
    automatically fetch the passphrase used by cryptsetup to unlock the
    root file system and set it as the PAM authtok. This enables, among
    other things, configuring auto-unlock of the GNOME Keyring / KDE
    Wallet when autologin is configured.

Note that the PAM module is not yet integrated in the spec file so it's not
automatically added on package installation/update.

Thanks.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17086801953.3A98.11159--


body:
--17086892452.637EE882.11633
Date: Fri, 23 Feb 2024 11:54:05 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220270

            Bug ID: 1220270
           Summary: Leap 15.6 many haskell build failures after haskell maintenance update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

(from investigation by Max Lin)

After a recent haskell package updated in SLE15-SP5-Update via
https://build.opensuse.org/package/show/SUSE:SLE-15-SP6:GA/patchinfo.32273
, haskell package in Leap 15.6(actually was in Backports:SLE-15-SP6
project) has started being failed or being unresolvable state[1][2],
it seems "ghc" has not got rebuild with that maint update like rebuild
with newer ghc-aeson, etc., that is my thought I'm not sure it's
correct though, and I also realize I can't take package from Factory
directly because the Factory ones has the profling enabled(?). Could
you please have a look those build fails/unresolvables in
openSUSE:Backports:SLE-15-SP6 ?

[1]
https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP6?ar=
ch_x86_64=3D1&defaults=3D0&failed=3D1&repo_standard=3D1
[2]
https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP6?ar=
ch_x86_64=3D1&defaults=3D0&repo_standard=3D1&unresolvable=3D1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17086892452.637EE882.11633
Date: Fri, 23 Feb 2024 11:54:05 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220270

          Summary
          Leap 15.6 many haskell build failures after haskell maintenan=
ce update

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          lubos.kocman@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

(from investigation by Max Lin)

After a recent haskell package updated in SLE15-SP5-Update via
https://build.opensuse.org/package/show/SUSE:SLE-15-SP6:GA/patc=
hinfo.32273
, haskell package in Leap 15.6(actually was in Backports:SLE-15-SP6
project) has started being failed or being unresolvable state[1][2],
it seems "ghc" has not got rebuild with that maint update like re=
build
with newer ghc-aeson, etc., that is my thought I'm not sure it's
correct though, and I also realize I can't take package from Factory
directly because the Factory ones has the profling enabled(?). Could
you please have a look those build fails/unresolvables in
openSUSE:Backports:SLE-15-SP6 ?

[1]
https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-=
SP6?arch_x86_64=3D1&defaults=3D0&failed=3D1&repo_standard=3D1</=
a>
[2]
https://build.opensuse.org/project/monitor/openSUSE:Backports:SL=
E-15-SP6?arch_x86_64=3D1&defaults=3D0&repo_standard=3D1&unresol=
vable=3D1

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17086892452.637EE882.11633--

pkgs: ghc-aws ghc-dbus ghc-feed ghc-free ghc-lens ghc-vty ghc-wreq ghc-zip ghcid hledger


body:
Gecko/20100101
Firefox/122.0
Build Identifier:=20

The latest updates broke the Filesystem sharing feature of KVM/QEMU. The re=
ason
seems to be the location of `virtiofsd`. The current location on my machine=
 is
`/usr/libexec/virtiofsd/virtiofsd` instead of `/usr/libexec/virtiofsd`. This
causes AppArmor to deny permission to execute the file.

Reproducible: Always

Steps to Reproduce:
1. Configure a VM that uses the Filesystem feature with the `virtiofs` driv=
er
2. Attempt to start the VM
Actual Results:=20=20
An error message:

```
Error starting domain: internal error: virtiofsd died unexpectedly

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 71=
, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 10=
7, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py&qu=
ot;, line 57,
in newfn
    ret =3D fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/domain.py", li=
ne 1425, in
startup
    self._backend.create()
  File "/usr/lib64/python3.11/site-packages/libvirt.py", line 137=
9, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: virtiofsd died unexpectedly

```

Expected Results:=20=20
The VM starts successfully.

Excerpt from `/var/log/libvirt/qemu/{vm-name}-fs0-virtiofsd.log`:

```
libvirt:  error : cannot execute binary /usr/libexec/virtiofsd/virtiofsd:
Permission denied
```

Excerpt from `/etc/apparmor.d/usr.sbin.virtqemud`:

```
/usr/{lib,lib64,lib/qemu,libexec}/virtiofsd PUx,
```

Workaround: Add the following line to `/etc/apparmor.d/usr.sbin.virtqemud`

```
/usr/{lib,lib64,lib/qemu,libexec}/virtiofsd/virtiofsd PUx,
```

Permanent solution: The location of `virtiofsd` should be
`/usr/libexec/virtiofsd`

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17088751010.ccD3.13112--

summary: Filesystem virtiofs fails to start with "internal error: virtiofsd died unexpectedly"


--17089563725.e4e1.14768
Date: Mon, 26 Feb 2024 14:06:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220367

            Bug ID: 1220367
           Summary: weblate has runtime dependency on python2 (/usr/bin/python)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

> zypper info --requires weblate

Information for package weblate:
--------------------------------
Repository     : Main Repository (OSS)
Name           : weblate
Version        : 5.3.1-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 174.9 MiB
=E2=80=A6
Requires       : [67]
    /bin/bash
    /usr/bin/python3
    /usr/bin/env
    python3-gobject-Gdk
    gpg2
    git
    postgresql
    cron
    python3-gobject-cairo
    /usr/bin/python            <---


body:
--17090441534.f1DAaDB.17197
Date: Tue, 27 Feb 2024 14:29:13 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220464

            Bug ID: 1220464
           Summary: GCC 14: elfutils package fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: michal.jires-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: matz-at-suse.com, mjambor-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Building elfutils with GCC 14 fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/elfutils/standard/x86_64

Due to:
elfstrmerge.c: In function =E2=80=98main=E2=80=99:
elfstrmerge.c:450:32: error: =E2=80=98calloc=E2=80=99 sizes specified with =
=E2=80=98sizeof=E2=80=99 in the
earlier argument and not in the later argument [-Werror=3Dcalloc-transposed=
-args]
  450 |   newscnbufs =3D calloc (sizeof (void *), newshnums);
      |                                ^~~~
elfstrmerge.c:450:32: note: earlier argument should specify number of eleme=
nts,
later size of each element

Builds with:

Index: elfutils-0.190/tests/elfstrmerge.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-

summary: GCC 14: elfutils package fails


body:
--17090537030.C3fa4Cde.17793
Date: Tue, 27 Feb 2024 17:08:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220490

            Bug ID: 1220490
           Summary: GCC 14: gdb package fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: michal.jires-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mjambor-at-suse.com, tdevries-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Building gdb with GCC 14 fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/gdb/standard/x86_64

Due to:

gdb-13.2/gdb/configure: line 418: test: too many arguments
configure: error: 18086
gdb-13.2/gdb/configure: line 307: return: Specific: numeric argument requir=
ed
gdb-13.2/gdb/configure: line 317: exit: Specific: numeric argument required
gdb-13.2/gdb/configure: conftest.c: In function 'main':
gdb-13.2/gdb/configure: conftest.c:54:18: error: implicit declaration of
function 'strerror'; did you mean 'Fstrerror'?
[-Wimplicit-function-declaration]
gdb-13.2/gdb/configure:    54 |                  strerror (errno));
gdb-13.2/gdb/configure:       |                  ^~~~~~~~
gdb-13.2/gdb/configure:       |                  Fstrerror
gdb-13.2/gdb/configure: conftest.c:75:9: error: implicit declaration of
function 'strcmp' [-Wimplicit-function-declaration]
gdb-13.2/gdb/configure:    75 |     if (strcmp ("librpm.so",
"/lib64/librpm.so.10") !=3D 0)
gdb-13.2/gdb/configure:       |         ^~~~~~
gdb-13.2/gdb/configure: conftest.c:41:1: note: include '<string.h>' or prov=
ide
a declaration of 'strcmp'
gdb-13.2/gdb/configure:    40 | #include <errno.h>
gdb-13.2/gdb/configure:   +++ |+#include <string.h>
gdb-13.2/gdb/configure:    41 |

Builds with:

Index: gdb.spec_dir/gdb-13.2/gdb/configure
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-

summary: GCC 14: gdb package fails


--17090811990.2c9Ef.18177
Date: Wed, 28 Feb 2024 00:46:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220496

            Bug ID: 1220496
           Summary: Unable to install "The openSUSEway desktop environment pattern" from Tumbleweed installer
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Patterns
          Assignee: dimstar-at-opensuse.org
          Reporter: pedroalexandresilva9-at-hotmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 873064
  --> https://bugzilla.suse.com/attachment.cgi?id=3D873064&action=3Dedit
The error message shown in the installer

Attempting a fresh install of the latest release of Tumbleweed, selecting t=
he
aforementioned pattern leads to the error show in the image attached to this
bug report. No other desktop environment pattern shows any error of this so=
rt.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17090811990.2c9Ef.18177
Date: Wed, 28 Feb 2024 00:46:39 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220496

          Summary
          Unable to install "The openSUSEway desktop environment p=
attern" from Tumbleweed installer

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Patterns

          Assignee
          dimstar@opensuse.org

          Reporter
          pedroalexandresilva9@hotmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 873064 [details]</=
span>
The error message shown in the installer

Attempting a fresh install of the latest release of Tumbleweed, selecting t=
he
aforementioned pattern leads to the error show in the image attached to this
bug report. No other desktop environment pattern shows any error of this so=
rt.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17090811990.2c9Ef.18177--


--17091094490.B70ac.18651
Date: Wed, 28 Feb 2024 08:37:29 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220514

            Bug ID: 1220514
           Summary: VUL-0: CVE-2024-1892: python-Scrapy: parts of API are vulnerable to a ReDoS attack
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/395399/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: dmueller-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: andrea.mattiazzo-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Parts of the Scrapy API were found to be vulnerable to a ReDoS attack. Hand=
ling
a malicious response could cause extreme CPU and memory usage during the
parsing of its content, due to the use of vulnerable regular expressions for
that parsing.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-1892
https://www.cve.org/CVERecord?id=3DCVE-2024-1892
https://huntr.com/bounties/271f94f2-1e05-4616-ac43-41752389e26b
https://docs.scrapy.org/en/latest/news.html#scrapy-2-11-0-2023-09-18

Patch:
https://github.com/scrapy/scrapy/commit/479619b340f197a8f24c5db45bc068fb875=
5f2c5
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17091094490.B70ac.18651
Date: Wed, 28 Feb 2024 08:37:29 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220514

          Summary
          VUL-0: CVE-2024-1892: python-Scrapy: parts of API are vulnera=
ble to a ReDoS attack

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          URL
          https://smash.suse.de/issue/395399/

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          dmueller@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          andrea.mattiazzo@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Parts of the Scrapy API were found to be vulnerable to a ReD=
oS attack. Handling
a malicious response could cause extreme CPU and memory usage during the
parsing of its content, due to the use of vulnerable regular expressions for
that parsing.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-1892
https://www.cv=
e.org/CVERecord?id=3DCVE-2024-1892
https://huntr.com/bounties/271f94f2-1e05-4616-ac43-41752389e26b
https://docs.scrapy.org/en/latest/news.html#scrapy-2-11-0-2023-09-18<=
/a>

Patch:
https://github.com/scrapy/scrapy/commit/479619b340f197a8f=
24c5db45bc068fb8755f2c5

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17091094490.B70ac.18651--


--17091111664.2db9C4.18756
Date: Wed, 28 Feb 2024 09:06:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220524

            Bug ID: 1220524
           Summary: Files in virtualbox shared folder  (on the guest) show wrong timestamp
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: suse.junky@t-online.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On my openSUSE Tumbleweed system (bare metal)

Operating System: openSUSE Tumbleweed 20240225
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.6-1-default (64-bit)
Graphics Platform: X11

I use virtualbox

# zypper se -si virtual*
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version               | Arch   |
Repository
---+------------------------+---------+-----------------------+--------+---=
---------------
i  | virtualbox             | package | 7.0.14-3.1            | x86_64 |
(System Packages)
i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2   | x86_64 |
(System Packages)
i+ | virtualbox-qt          | package | 7.0.14-3.1            | x86_64 |
(System Packages)
#

One guest is an openSUSE Tumbleweed 20240225 system with

# zypper se -si virtualbox*
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version             | Arch   |
Repository
---+------------------------+---------+---------------------+--------+-----=
-------------
i+ | virtualbox-guest-tools | package | 7.0.14-3.1          | x86_64 | (Sys=
tem
Packages)
i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (Sys=
tem
Packages)
#

The host shares a directory (/mnt/Lokal/VM_share) with the guest.

On the host system I have (in my home directory) a file

> ls -la *.jpg
-rw-r--r


--17091256952.7BafF.19596
Date: Wed, 28 Feb 2024 13:08:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220564

            Bug ID: 1220564
           Summary: openSUSE TW bash package does not build with GCC 14
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: werner-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

GCC 14 treats implicit function declarations as errors (see
https://gcc.gnu.org/gcc-14/porting_to.html for more details) and this
causes our bash package to fail when being built - as can be seen for
example in
https://build.opensuse.org/package/show/devel:gcc:next:testing/bash

There are two issues:

1. Upstream bash needs patch from
   https://lists.gnu.org/archive/html/bug-bash/2023-02/msg00000.html to
   be built with GCC 14.  (See also https://bugs.gentoo.org/920521 and
=20=20
https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/b/bash.md?ref_=
type=3Dheads
)

2. On top of that, the Tumbleweed package needs an adjustment to the
   patch in bash-4.2-nscdunmap.dif that we carry, which needs an
   additional include of sys/mman.h.

The two above changes made the build pass in
https://build.opensuse.org/package/show/home:jamborm:gcc14test/bash
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17091256952.7BafF.19596
Date: Wed, 28 Feb 2024 13:08:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220564

          Summary
          openSUSE TW bash package does not build with GCC 14

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mjambor@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          werner@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

GCC 14 treats implicit function declarations as errors (see
https://gcc.gnu.org/=
gcc-14/porting_to.html for more details) and this
causes our bash package to fail when being built - as can be seen for
example in
https://build.opensuse.org/package/show/devel:gcc:next:testing/bash

There are two issues:

1. Upstream bash needs patch from
   https://lists.gnu.org/archive/html/bug-bash/2023-02/msg00000.html=
 to
   be built with GCC 14.  (See also https://bugs.gentoo.org/920521 and
=20=20
https://gitlab.com/fweimer-rh/fedora-modernc/-/blo=
b/main/pkg/b/bash.md?ref_type=3Dheads
)

2. On top of that, the Tumbleweed package needs an adjustment to the
   patch in bash-4.2-nscdunmap.dif that we carry, which needs an
   additional include of sys/mman.h.

The two above changes made the build pass in
https://build.opensuse.org/package/show/home:jamborm:gcc14test/bash

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17091256952.7BafF.19596--


--17091317312.6a9fAaf.19908
Date: Wed, 28 Feb 2024 14:48:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220574

            Bug ID: 1220574
           Summary: [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now errors)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: mjambor-at-suse.com
          Reporter: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Meta issue that will track all packages that fail with gcc14 package except=
 for
those that are tracked in bug#1220571 - i.e. those that cannot be worked ar=
ound
by turning new errors back to warnings.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17091317312.6a9fAaf.19908
Date: Wed, 28 Feb 2024 14:48:51 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220574

          Summary
          [META] GCC 14 package failures that cannot be worked around w=
ith -fpermissive (that are not results of warnings that are now errors)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          mjambor@suse.com

          Reporter
          mjambor@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Meta issue that will track all packages that fail with gcc14=
 package except for
those that are tracked in bug#1220571 - i.e. those that can=
not be worked around
by turning new errors back to warnings.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17091317312.6a9fAaf.19908--


body:
--17091948251.99BdF93.21230
Date: Thu, 29 Feb 2024 08:20:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220604

            Bug ID: 1220604
           Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 122.0.6261.94
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: Andreas.Stieger-at-gmx.de, m.szczepaniak.000-at-gmail.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The Stable channel has been updated to 122.0.6261.94 for Mac,Linux and
122.0.6261.94/.95 to Windows which will roll out over the coming days/weeks=
. A
full list of changes in this build is available in the Log.

The Extended Stable channel has been updated to 122.0.6261.94 for Mac and
122.0.6261.95 for Windows which will roll out over the coming days/weeks.

 Security Fixes and Rewards

This update includes 4 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

High CVE-2024-1938: Type Confusion in V8. Reported by
5f46f4ee2e17957ba7b39897fb376be8 on 2024-02-11

High CVE-2024-1939: Type Confusion in V8. Reported by Bohan Liu
(@P4nda20371774) of Tencent Security Xuanwu Lab on 2024-02-05

References:
https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-des=
ktop_27.html
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17091948251.99BdF93.21230
Date: Thu, 29 Feb 2024 08:20:25 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220604

          Summary
          VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities =
fixed in 122.0.6261.94

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          gmbr3@opensuse.org

          Reporter
          thomas.leroy@suse.com

          QA Contact
          security-team@suse.de

          CC
          Andreas.Stieger@gmx.de, m.szczepaniak.000@gmail.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The Stable channel has been updated to 122.0.6261.94 for Mac=
,Linux and
122.0.6261.94/.95 to Windows which will roll out over the coming days/weeks=
. A
full list of changes in this build is available in the Log.

The Extended Stable channel has been updated to 122.0.6261.94 for Mac and
122.0.6261.95 for Windows which will roll out over the coming days/weeks.

 Security Fixes and Rewards

This update includes 4 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

High CVE-2024-1938: Type Confusion in V8. Reported by
5f46f4ee2e17957ba7b39897fb376be8 on 2024-02-11

High CVE-2024-1939: Type Confusion in V8. Reported by Bohan Liu
(@P4nda20371774) of Tencent Security Xuanwu Lab on 2024-02-05

References:
https://chromereleases.googleblog.com/2024/02/stab=
le-channel-update-for-desktop_27.html

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17091948251.99BdF93.21230--

pkgs: chromium ungoogled-chromium


--17092075739.04ccBecA.22217
Date: Thu, 29 Feb 2024 11:52:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220666

            Bug ID: 1220666
           Summary: VUL-0: CVE-2024-22871: clojure: denial of service (DoS) via the clojure.core$partial$fn__5920 function.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/395778/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mvetter-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: stoyan.manolov-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an attacker to ca=
use
a denial of service (DoS) via the clojure.core$partial$fn__5920 function.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22871
https://www.cve.org/CVERecord?id=3DCVE-2024-22871
https://hackmd.io/%40fe1w0/rymmJGida
https://bugzilla.redhat.com/show_bug.cgi?id=3D2266785
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17092075739.04ccBecA.22217
Date: Thu, 29 Feb 2024 11:52:53 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220666

          Summary
          VUL-0: CVE-2024-22871: clojure: denial of service (DoS) via t=
he clojure.core$partial$fn__5920 function.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          URL
          https://smash.suse.de/issue/395778/

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          mvetter@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          stoyan.manolov@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an=
 attacker to cause
a denial of service (DoS) via the clojure.core$partial$fn__5920 function.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22871
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-22871
https://hackmd.io/%40fe1w0=
/rymmJGida
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2266785

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17092075739.04ccBecA.22217--


--17092086121.fb6C.22274
Date: Thu, 29 Feb 2024 12:10:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220668

            Bug ID: 1220668
           Summary: kamoso fails to show any UI (on GNOME system)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: gp-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Starting kamoso via the command line I see

  QQmlApplicationEngine failed to load component
  qrc:/qml/Main.qml:154:22: Type ImagesView unavailable
  qrc:/qml/ImagesView.qml:13:1: module "org.kde.purpose" is not installed

in the console and then ... nothing, until I stop it via <Ctrl>-<C>.

This is kamoso-23.08.4-1.2.x86_64 on current Tumbleweed with a GNOME
desktop.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17092086121.fb6C.22274
Date: Thu, 29 Feb 2024 12:10:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220668

          Summary
          kamoso fails to show any UI (on GNOME system)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Applications

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          gp@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Starting kamoso via the command line I see

  QQmlApplicationEngine failed to load component
  qrc:/qml/Main.qml:154:22: Type ImagesView unavailable
  qrc:/qml/ImagesView.qml:13:1: module "org.kde.purpose" is not i=
nstalled

in the console and then ... nothing, until I stop it via <Ctrl>-<C=
>.

This is kamoso-23.08.4-1.2.x86_64 on current Tumbleweed with a GNOME
desktop.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17092086121.fb6C.22274--


--17092225592.04E967AF.23149
Date: Thu, 29 Feb 2024 16:02:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220708

            Bug ID: 1220708
           Summary: Warning: The unit file, source configuration file or drop-ins of apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: gp-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Running "zypper dup" on Tumbleweed yesterday, I got the following
confusing warnings at the end of the process, both related to AppArmor:

%posttrans(apparmor-abstractions-3.1.7-3.1.noarch) script output:
Warning: The unit file, source configuration file or drop-ins of
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload
units.

%posttrans(apparmor-profiles-3.1.7-3.1.noarch) script output:
Warning: The unit file, source configuration file or drop-ins of
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
Running post-transaction scripts=20

It's not clear what, or whether there is anything, actually to do for
me as operator here.

Intuitively, should such a restart happen automatically? Or am I really
expected to copy&paste&run those two commands?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17092225592.04E967AF.23149
Date: Thu, 29 Feb 2024 16:02:39 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220708

          Summary
          Warning: The unit file, source configuration file or drop-ins=
 of apparmor.service changed on disk. Run 'systemctl daemon-reload' to relo=
ad units.

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          AppArmor

          Assignee
          suse-beta@cboltz.de

          Reporter
          gp@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Running "zypper dup" on Tumbleweed yesterday, I go=
t the following
confusing warnings at the end of the process, both related to AppArmor:

%posttrans(apparmor-abstractions-3.1.7-3.1.noarch) script output:
Warning: The unit file, source configuration file or drop-ins of
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload
units.

%posttrans(apparmor-profiles-3.1.7-3.1.noarch) script output:
Warning: The unit file, source configuration file or drop-ins of
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
Running post-transaction scripts=20

It's not clear what, or whether there is anything, actually to do for
me as operator here.

Intuitively, should such a restart happen automatically? Or am I really
expected to copy&paste&run those two commands?

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17092225592.04E967AF.23149--


--17092619520.a95FB72.24031
Date: Fri, 1 Mar 2024 02:59:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220724

            Bug ID: 1220724
           Summary: emacs-x11 and emacs-nox packages break clang
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dmk-at-dmk.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

When emacs is installed, clang++ cannot find the C++ library.

To reproduce this:

1.  Install emacs.  It does not matter whether you install the X or non-X
version.

2.  Install clang.

3.  Try to compile and link a C++ program.

```
$ clang++ hello.cpp
/usr/bin/ld: cannot find -lstdc++: No such file or directory
clang++: error: linker command failed with exit code 1 (use -v to see
invocation)
$
```

The problem:

The latest stable, released version of gcc is gcc13.  I have this installed=
.=20
When clang++ is run, it looks for the latest gcc it can find, to use its C++
library.

However, both the emacs-x11 and emacs-nox packages depend on gcc14, which is
unstable and unreleased.

```
$ zypper info --requires emacs-x11 | grep 14
    libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit)
$ zypper info --requires emacs-nox | grep 14
    libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit)
$
```

Consequently, installing emacs causes gcc14 to be installed.  Clang++ then
finds this and tries to use it.

```
$ clang++ -v
clang version 17.0.6
Target: x86_64-suse-linux
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/13
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14
Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14
Candidate multilib: .;@m64
Selected multilib: .;@m64
$
```

Since emacs does not require the C++ library, that is not installed.  Clang=
++
tries to use gcc14 and finds libc++ missing.

How to fix this:

There is an unacceptable workaround.  It is possible to work around the pro=
blem
by installing libstdc++6-devel-gcc14 .  The reason this is unacceptable is =
that
then, a stable, released clang depends on an unstable, unreleased gcc
installation.  It would not be possible to trust the binaries compiled and
linked by this configuration.

I see a few possible ways to fix it in acceptable ways.  Any one of them wo=
uld
work.

1.  Do not make emacs-x11 and emacs-nox depend on a gcc14 library.

2.  Install unstable, unreleased versions of gcc in a different location so
clang++ cannot find them.

3.  Modify the clang package not to find unstable, unreleased versions of g=
cc.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17092619520.a95FB72.24031
Date: Fri, 1 Mar 2024 02:59:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220724

          Summary
          emacs-x11 and emacs-nox packages break clang

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dmk@dmk.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

When emacs is installed, clang++ cannot find the C++ library.

To reproduce this:

1.  Install emacs.  It does not matter whether you install the X or non-X
version.

2.  Install clang.

3.  Try to compile and link a C++ program.

```
$ clang++ hello.cpp
/usr/bin/ld: cannot find -lstdc++: No such file or directory
clang++: error: linker command failed with exit code 1 (use -v to see
invocation)
$
```

The problem:

The latest stable, released version of gcc is gcc13.  I have this installed=
.=20
When clang++ is run, it looks for the latest gcc it can find, to use its C++
library.

However, both the emacs-x11 and emacs-nox packages depend on gcc14, which is
unstable and unreleased.

```
$ zypper info --requires emacs-x11 | grep 14
    libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit)
$ zypper info --requires emacs-nox | grep 14
    libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit)
$
```

Consequently, installing emacs causes gcc14 to be installed.  Clang++ then
finds this and tries to use it.

```
$ clang++ -v
clang version 17.0.6
Target: x86_64-suse-linux
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/13
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14
Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14
Candidate multilib: .;@m64
Selected multilib: .;@m64
$
```

Since emacs does not require the C++ library, that is not installed.  Clang=
++
tries to use gcc14 and finds libc++ missing.

How to fix this:

There is an unacceptable workaround.  It is possible to work around the pro=
blem
by installing libstdc++6-devel-gcc14 .  The reason this is unacceptable is =
that
then, a stable, released clang depends on an unstable, unreleased gcc
installation.  It would not be possible to trust the binaries compiled and
linked by this configuration.

I see a few possible ways to fix it in acceptable ways.  Any one of them wo=
uld
work.

1.  Do not make emacs-x11 and emacs-nox depend on a gcc14 library.

2.  Install unstable, unreleased versions of gcc in a different location so
clang++ cannot find them.

3.  Modify the clang package not to find unstable, unreleased versions of g=
cc.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17092619520.a95FB72.24031--


--17093178301.eD99DeD.26814
Date: Fri, 1 Mar 2024 18:30:30 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220809

            Bug ID: 1220809
           Summary: dcmtk-devel should probably require libxml2-devel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

grep -i libxml2 $(rpm -ql dcmtk-devel |grep -i cmake)
grep: /usr/lib64/cmake/dcmtk: Is a directory
/usr/lib64/cmake/dcmtk/DCMTKTargets.cmake:  INTERFACE_LINK_LIBRARIES
"DCMTK::dcmdata;DCMTK::ofstd;DCMTK::oflog;/usr/lib64/libz.so;/usr/lib64/lib=
xml2.so"
/usr/lib64/cmake/dcmtk/DCMTKTargets.cmake:  INTERFACE_LINK_LIBRARIES
"DCMTK::ofstd;DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;DCMTK::dcmimage;/=
usr/lib64/libxml2.so"
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17093178301.eD99DeD.26814
Date: Fri, 1 Mar 2024 18:30:30 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220809

          Summary
          dcmtk-devel should probably require libxml2-devel

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mrueckert@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

grep -i libxml2 $(rpm -ql dcmtk-devel |grep -i cmake)
grep: /usr/lib64/cmake/dcmtk: Is a directory
/usr/lib64/cmake/dcmtk/DCMTKTargets.cmake:  INTERFACE_LINK_LIBRARIES
"DCMTK::dcmdata;DCMTK::ofstd;DCMTK::oflog;/usr/lib64/libz.so;/usr/lib6=
4/libxml2.so"
/usr/lib64/cmake/dcmtk/DCMTKTargets.cmake:  INTERFACE_LINK_LIBRARIES
"DCMTK::ofstd;DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;DCMTK::dcmim=
age;/usr/lib64/libxml2.so"

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17093178301.eD99DeD.26814--


--17094144200.df90B5.27374
Date: Sat, 2 Mar 2024 21:20:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220818

            Bug ID: 1220818
           Summary: ImageMagick and ImageMagick-config-7-SUSE file conflict
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: db@mail25.net
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Was running `zypper dup`

The following product is going to be upgraded:
  openSUSE Tumbleweed  20240229-0 -> 20240301-0

The following package is going to be REMOVED:
  ImageMagick-config-7-SUSE

After downloading all packages I got this error:
> Verifying ...............................................................=
.............................................................[done]
> Preparing ...............................................................=
.............................................................[done]
> Problem occurred during or after installation or removal of packages:
> Executing the transaction failed because of the following problems:
>     file /etc/ImageMagick-7 from install of ImageMagick-7.1.1.29-1.1.x86_=
64 conflicts with file from package ImageMagick-config-7-SUSE-7.1.1.26-1.6.=
x86_64

> > sudo  zypper pa | grep ImageMag
> i  | @System                          | ImageMagick                      =
                          | 7.1.1.26-1.6                                   =
      | x86_64
> v  | openSUSE-Tumbleweed-Main-OSS     | ImageMagick                      =
                          | 7.1.1.29-1.1                                   =
      | x86_64
> i+ | @System                          | ImageMagick-config-7-SUSE        =
                          | 7.1.1.26-1.6                                   =
      | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-devel                =
                          | 7.1.1.29-1.1                                   =
      | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-devel-32bit          =
                          | 7.1.1.29-1.1                                   =
      | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-doc                  =
                          | 7.1.1.29-1.1                                   =
      | noarch
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-extra                =
                          | 7.1.1.29-1.1                                   =
      | x86_64

I'm using `techpreview.ZYPP_SINGLE_RPMTRANS=3D1`.

Not actually a problem for me, I just removed ImageMagick and
ImageMagick-config-7-SUSE packages before updating but I thought maybe this=
 is
a relevant bug.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17094144200.df90B5.27374
Date: Sat, 2 Mar 2024 21:20:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220818

          Summary
          ImageMagick and ImageMagick-config-7-SUSE file conflict

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          db@mail25.net

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Was running `zypper dup`

The following product is going to be upgraded:
  openSUSE Tumbleweed  20240229-0 -> 20240301-0

The following package is going to be REMOVED:
  ImageMagick-config-7-SUSE

After downloading all packages I got this error:
> Verifying ......................................=
...........................................................................=
...........[done]
> Preparing ............................................................=
................................................................[done]
> Problem occurred during or after installation or removal of packages:
> Executing the transaction failed because of the following problems:
>     file /etc/ImageMagick-7 from install of ImageMagick-7.1.1.29-1.1.x=
86_64 conflicts with file from package ImageMagick-config-7-SUSE-7.1.1.26-1=
.6.x86_64

> > sudo  zypper pa | grep ImageMag
> i  | @System                          | ImageMagick               =
                                 | 7.1.1.26-1.6                            =
             | x86_64
> v  | openSUSE-Tumbleweed-Main-OSS     | ImageMagick                   =
                             | 7.1.1.29-1.1                                =
         | x86_64
> i+ | @System                          | ImageMagick-config-7-SUSE =
                                 | 7.1.1.26-1.6                            =
             | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-devel             =
                             | 7.1.1.29-1.1                                =
         | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-devel-32bit       =
                             | 7.1.1.29-1.1                                =
         | x86_64
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-doc               =
                             | 7.1.1.29-1.1                                =
         | noarch
>    | openSUSE-Tumbleweed-Main-OSS     | ImageMagick-extra             =
                             | 7.1.1.29-1.1                                =
         | x86_64

I'm using `techpreview.ZYPP_SINGLE_RPMTRANS=3D1`.

Not actually a problem for me, I just removed ImageMagick and
ImageMagick-config-7-SUSE packages before updating but I thought maybe this=
 is
a relevant bug.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17094144200.df90B5.27374--


body:
--17095050073.33EB9B3.27631
Date: Sun, 3 Mar 2024 22:30:07 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220821

            Bug ID: 1220821
           Summary: Cannot install musescore in 16.6 alpha
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: llrainey15-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Problem: the to be installed musescore-4.2.1-bp156.1.1.x86_64 requires
'(alsa-plugins-pulse if pulseaudio)', but this requirement cannot be provid=
ed
  not installable providers:
alsa-plugins-pulse-1.2.7.1-150500.1.1.x86_64[os-repo-oss]

VM3:~ #  zypper in musescore
Loading repository data...
Warning: Repository 'Update repository of openSUSE Backports' metadata expi=
red
since 2023-09-29 04:08:32 CDT.
Warning: Repository 'Update Repository (Non-Oss)' metadata expired since
2023-09-21 07:47:58 CDT.
Warning: Repository 'Update repository of openSUSE Backports' metadata expi=
red
since 2023-09-29 04:08:32 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned =
on
    (zypper lr), otherwise manually refresh the repository (zypper ref). If
this
    does not solve the issue, it could be that you are using a broken mirro=
r or
    the server has actually discontinued to support the repository.

Reading installed packages...
Resolving package dependencies...

Problem: the to be installed musescore-4.2.1-bp156.1.1.x86_64 requires
'(alsa-plugins-pulse if pulseaudio)', but this requirement cannot be provid=
ed
  not installable providers:
alsa-plugins-pulse-1.2.7.1-150500.1.1.x86_64[os-repo-oss]
=C2=A0Solution 1: Following actions will be done:
  deinstallation of pulseaudio-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-lang-17.0-150600.1.1.noarch
  deinstallation of pulseaudio-module-bluetooth-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-module-lirc-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-module-zeroconf-17.0-150600.1.1.x86_64
=C2=A0Solution 2: Following actions will be done:
  deinstallation of pipewire-alsa-1.0.3-150600.1.1.x86_64
  deinstallation of pipewire-1.0.3-150600.1.1.x86_64
  deinstallation of pipewire-lang-1.0.3-150600.1.1.noarch
  deinstallation of wireplumber-0.4.17-150600.1.1.x86_64
  deinstallation of wireplumber-lang-0.4.17-150600.1.1.noarch
  deinstallation of wireplumber-zsh-completion-0.4.17-150600.1.1.x86_64
=C2=A0Solution 3: do not install musescore-4.2.1-bp156.1.1.x86_64
=C2=A0Solution 4: break musescore-4.2.1-bp156.1.1.x86_64 by ignoring some o=
f its
dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
VM3:~ #
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17095050073.33EB9B3.27631
Date: Sun, 3 Mar 2024 22:30:07 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220821

          Summary
          Cannot install musescore in 16.6 alpha

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          x86-64

          OS
          SUSE Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          llrainey15@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Problem: the to be installed musescore-4.2.1-bp156.1.1.x86_6=
4 requires
'(alsa-plugins-pulse if pulseaudio)', but this requirement cannot be provid=
ed
  not installable providers:
alsa-plugins-pulse-1.2.7.1-150500.1.1.x86_64[os-repo-oss]

VM3:~ #  zypper in musescore
Loading repository data...
Warning: Repository 'Update repository of openSUSE Backports' metadata expi=
red
since 2023-09-29 04:08:32 CDT.
Warning: Repository 'Update Repository (Non-Oss)' metadata expired since
2023-09-21 07:47:58 CDT.
Warning: Repository 'Update repository of openSUSE Backports' metadata expi=
red
since 2023-09-29 04:08:32 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned =
on
    (zypper lr), otherwise manually refresh the repository (zypper ref). If
this
    does not solve the issue, it could be that you are using a broken mirro=
r or
    the server has actually discontinued to support the repository.

Reading installed packages...
Resolving package dependencies...

Problem: the to be installed musescore-4.2.1-bp156.1.1.x86_64 requires
'(alsa-plugins-pulse if pulseaudio)', but this requirement cannot be provid=
ed
  not installable providers:
alsa-plugins-pulse-1.2.7.1-150500.1.1.x86_64[os-repo-oss]
=C2=A0Solution 1: Following actions will be done:
  deinstallation of pulseaudio-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-lang-17.0-150600.1.1.noarch
  deinstallation of pulseaudio-module-bluetooth-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-module-lirc-17.0-150600.1.1.x86_64
  deinstallation of pulseaudio-module-zeroconf-17.0-150600.1.1.x86_64
=C2=A0Solution 2: Following actions will be done:
  deinstallation of pipewire-alsa-1.0.3-150600.1.1.x86_64
  deinstallation of pipewire-1.0.3-150600.1.1.x86_64
  deinstallation of pipewire-lang-1.0.3-150600.1.1.noarch
  deinstallation of wireplumber-0.4.17-150600.1.1.x86_64
  deinstallation of wireplumber-lang-0.4.17-150600.1.1.noarch
  deinstallation of wireplumber-zsh-completion-0.4.17-150600.1.1.x86_64
=C2=A0Solution 3: do not install musescore-4.2.1-bp156.1.1.x86_64
=C2=A0Solution 4: break musescore-4.2.1-bp156.1.1.x86_64 by ignoring some o=
f its
dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
VM3:~ #

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17095050073.33EB9B3.27631--

summary: Cannot install musescore in 16.6 alpha


body:
--17096483024.f288c424B.32406
Date: Tue, 5 Mar 2024 14:18:22 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220977

            Bug ID: 1220977
           Summary: GCC 14: libXaw3d package fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: michal.jires-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: werner-at-suse.com
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Building libXaw3d with GCC 14 fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/libXaw3d/standard/x86_64

Due to (exhaustive list of errors):

MultiSink.c: In function 'SetValues':
MultiSink.c:595:18: error: passing argument 1 of 'SetTabs' from incompatible
pointer type [-Wincompatible-pointer-types]
  595 |         SetTabs( w, w->text_sink.tab_count, w->text_sink.char_tabs =
);
      |                  ^
      |                  |
      |                  MultiSinkObject {aka struct _MultiSinkRec *}
MultiSink.c:99:21: note: expected 'Widget' {aka 'struct _WidgetRec *'} but
argument is of type 'MultiSinkObject' {aka 'struct _MultiSinkRec *'}
   99 | static void SetTabs(Widget, int, short *);
      |                     ^~~~~~

See the meta bug#1220571 for more info.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17096483024.f288c424B.32406
Date: Tue, 5 Mar 2024 14:18:22 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220977

          Summary
          GCC 14: libXaw3d package fails

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 Applications

          Assignee
          screening-team-bugs@suse.de

          Reporter
          michal.jires@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          werner@suse.com

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Building libXaw3d with GCC 14 fails here:
https://build.opensuse.org/packag=
e/live_build_log/openSUSE:Factory:Staging:Gcc7/libXaw3d/standard/x86_64

Due to (exhaustive list of errors):

MultiSink.c: In function 'SetValues':
MultiSink.c:595:18: error: passing argument 1 of 'SetTabs' from incompatible
pointer type [-Wincompatible-pointer-types]
  595 |         SetTabs( w, w->text_sink.tab_count, w->text_sink.char=
_tabs );
      |                  ^
      |                  |
      |                  MultiSinkObject {aka struct _MultiSinkRec *}
MultiSink.c:99:21: note: expected 'Widget' {aka 'struct _WidgetRec *'} but
argument is of type 'MultiSinkObject' {aka 'struct _MultiSinkRec *'}
   99 | static void SetTabs(Widget, int, short *);
      |                     ^~~~~~

See the meta bug#1220571 for more info.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17096483024.f288c424B.32406--

summary: GCC 14: libXaw3d package fails


--17096652341.d4D96.720
Date: Tue, 5 Mar 2024 19:00:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1220993

            Bug ID: 1220993
           Summary: GPG Keys expired in package openSUSE-build-key for alternative architectures
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: ada.lovelace-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This week, I have received an interesting question by Fedora regarding the =
GPG
key for openSUSE Tumbleweed on s390x:
https://github.com/rpm-software-management/mock/issues/1334#issuecomment-19=
76327235

The question was, whether we are using different keys.
I found our package openSUSE-build-key.

The GPG keys for s390x, PPC and RISCV are expired since years...
Isn't that a security risk? Why are the systems not crying because of that?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17096652341.d4D96.720
Date: Tue, 5 Mar 2024 19:00:34 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1220993

          Summary
          GPG Keys expired in package openSUSE-build-key for alternativ=
e architectures

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          ada.lovelace@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This week, I have received an interesting question by Fedora=
 regarding the GPG
key for openSUSE Tumbleweed on s390x:
https://github.com/rpm-software-management/mock/issues=
/1334#issuecomment-1976327235

The question was, whether we are using different keys.
I found our package openSUSE-build-key.

The GPG keys for s390x, PPC and RISCV are expired since years...
Isn't that a security risk? Why are the systems not crying because of that?=

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17096652341.d4D96.720--


body:
--17097083473.B1ba3CB.1425
Date: Wed, 6 Mar 2024 06:59:07 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1221008

            Bug ID: 1221008
           Summary: GCC 14: musepack package fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: michal.jires-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Building musepack with GCC 14 fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/musepack/standard/x86_64

Due to (exhaustive list of errors):

musepack_src_r475/libmpcpsy/ans.c: In function =E2=80=98NS_Analyse=E2=80=99:
musepack_src_r475/libmpcpsy/ans.c:291:120: error: passing argument 10 of
=E2=80=98FindOptimalANS=E2=80=99 from incompatible pointer type [-Wincompat=
ible-pointer-types]
  291 |         FindOptimalANS ( MaxBand, MSflag, ANSspec_L, ANSspec_M,
m->NS_Order_L, m->SNR_comp_L, m->FIR_L, smr.L, smr.M, m->SCF_Index_L, Trans=
ient
);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                              ~^~~~~~~~~~~~~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               int *
musepack_src_r475/libmpcpsy/ans.c:160:40: note: expected =E2=80=98const int=
 (*)[3]=E2=80=99 but
argument is of type =E2=80=98int *=E2=80=99
  160 |                  const int             scf [] [3],
      |                  ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
musepack_src_r475/libmpcpsy/ans.c:296:120: error: passing argument 10 of
=E2=80=98FindOptimalANS=E2=80=99 from incompatible pointer type [-Wincompat=
ible-pointer-types]
  296 |         FindOptimalANS ( MaxBand, MSflag, ANSspec_R, ANSspec_S,
m->NS_Order_R, m->SNR_comp_R, m->FIR_R, smr.R, smr.S, m->SCF_Index_R, Trans=
ient
);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                              ~^~~~~~~~~~~~~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               int *

musepack_src_r475/mpcenc/mpcenc.c: In function =E2=80=98Quantisierung=E2=80=
=99:
musepack_src_r475/mpcenc/mpcenc.c:692:61: error: passing argument 1 of
=E2=80=98QuantizeSubbandWithNoiseShaping=E2=80=99 from incompatible pointer=
 type
[-Wincompatible-pointer-types]
  692 |                 QuantizeSubbandWithNoiseShaping ( subq[Band].L,
subx[Band].L, *resL, errorL [Band], m->FIR_L [Band] );
      |                                                   ~~~~~~~~~~^~
      |                                                             |
      |                                                             mpc_int=
16_t
* {aka short int *}
In file included from
/home/abuild/rpmbuild/BUILD/musepack_src_r475/mpcenc/mpcenc.c:27:
musepack_src_r475/mpcenc/mpcenc.h:258:56: note: expected =E2=80=98unsigned =
int *=E2=80=99 but
argument is of type =E2=80=98mpc_int16_t *=E2=80=99 {aka =E2=80=98short int=
 *=E2=80=99}
  258 | void   QuantizeSubbandWithNoiseShaping ( unsigned int* qu_output, c=
onst
float* input, const int res, float* errors, const float* FIR );
      |                                          ~~~~~~~~~~~~~~^~~~~~~~~
musepack_src_r475/mpcenc/mpcenc.c:695:77: error: passing argument 1 of
=E2=80=98QuantizeSubband=E2=80=99 from incompatible pointer type [-Wincompa=
tible-pointer-types]
  695 |                                 QuantizeSubband                 (
subq[Band].L, subx[Band].L, *resL, errorL [Band], MAX_NS_ORDER );
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
~~~~~~~~~~^~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    mpc_int16_t * {aka short int *}
musepack_src_r475/mpcenc/mpcenc.h:257:56: note: expected =E2=80=98unsigned =
int *=E2=80=99 but
argument is of type =E2=80=98mpc_int16_t *=E2=80=99 {aka =E2=80=98short int=
 *=E2=80=99}
  257 | void   QuantizeSubband                 ( unsigned int* qu_output, c=
onst
float* input, const int res, float* errors, const int maxNsOrder );
      |                                          ~~~~~~~~~~~~~~^~~~~~~~~
musepack_src_r475/mpcenc/mpcenc.c:702:61: error: passing argument 1 of
=E2=80=98QuantizeSubbandWithNoiseShaping=E2=80=99 from incompatible pointer=
 type
[-Wincompatible-pointer-types]
  702 |                 QuantizeSubbandWithNoiseShaping ( subq[Band].R,
subx[Band].R, *resR, errorR [Band], m->FIR_R [Band] );
      |                                                   ~~~~~~~~~~^~
      |                                                             |
      |                                                             mpc_int=
16_t
* {aka short int *}
musepack_src_r475/mpcenc/mpcenc.c:705:77: error: passing argument 1 of
=E2=80=98QuantizeSubband=E2=80=99 from incompatible pointer type [-Wincompa=
tible-pointer-types]
  705 |                                 QuantizeSubband                 (
subq[Band].R, subx[Band].R, *resR, errorL [Band], MAX_NS_ORDER);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
~~~~~~~~~~^~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    mpc_int16_t * {aka short int *}

See the meta bug#1220571 for more info.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17097083473.B1ba3CB.1425
Date: Wed, 6 Mar 2024 06:59:07 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1221008

          Summary
          GCC 14: musepack package fails

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          michal.jires@suse.com

          QA Contact
          qa-bugs@suse.de

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Building musepack with GCC 14 fails here:
https://build.opensuse.org/packag=
e/live_build_log/openSUSE:Factory:Staging:Gcc7/musepack/standard/x86_64

Due to (exhaustive list of errors):

musepack_src_r475/libmpcpsy/ans.c: In function =E2=80=98NS_Analyse=E2=80=99:
musepack_src_r475/libmpcpsy/ans.c:291:120: error: passing argument 10 of
=E2=80=98FindOptimalANS=E2=80=99 from incompatible pointer type [-Wincompat=
ible-pointer-types]
  291 |         FindOptimalANS ( MaxBand, MSflag, ANSspec_L, ANSspec_M,
m->NS_Order_L, m->SNR_comp_L, m->FIR_L, smr.L, smr.M, m->SCF_In=
dex_L, Transient
);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                              ~^~~~~~~~~~~~~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               int *
musepack_src_r475/libmpcpsy/ans.c:160:40: note: expected =E2=80=98const int=
 (*)[3]=E2=80=99 but
argument is of type =E2=80=98int *=E2=80=99
  160 |                  const int             scf [] [3],
      |                  ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
musepack_src_r475/libmpcpsy/ans.c:296:120: error: passing argument 10 of
=E2=80=98FindOptimalANS=E2=80=99 from incompatible pointer type [-Wincompat=
ible-pointer-types]
  296 |         FindOptimalANS ( MaxBand, MSflag, ANSspec_R, ANSspec_S,
m->NS_Order_R, m->SNR_comp_R, m->FIR_R, smr.R, smr.S, m->SCF_In=
dex_R, Transient
);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                              ~^~~~~~~~~~~~~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                                               int *

musepack_src_r475/mpcenc/mpcenc.c: In function =E2=80=98Quantisierung=E2=80=
=99:
musepack_src_r475/mpcenc/mpcenc.c:692:61: error: passing argument 1 of
=E2=80=98QuantizeSubbandWithNoiseShaping=E2=80=99 from incompatible pointer=
 type
[-Wincompatible-pointer-types]
  692 |                 QuantizeSubbandWithNoiseShaping ( subq[Band].L,
subx[Band].L, *resL, errorL [Band], m->FIR_L [Band] );
      |                                                   ~~~~~~~~~~^~
      |                                                             |
      |                                                             mpc_int=
16_t
* {aka short int *}
In file included from
/home/abuild/rpmbuild/BUILD/musepack_src_r475/mpcenc/mpcenc.c:27:
musepack_src_r475/mpcenc/mpcenc.h:258:56: note: expected =E2=80=98unsigned =
int *=E2=80=99 but
argument is of type =E2=80=98mpc_int16_t *=E2=80=99 {aka =E2=80=98short int=
 *=E2=80=99}
  258 | void   QuantizeSubbandWithNoiseShaping ( unsigned int* qu_output, c=
onst
float* input, const int res, float* errors, const float* FIR );
      |                                          ~~~~~~~~~~~~~~^~~~~~~~~
musepack_src_r475/mpcenc/mpcenc.c:695:77: error: passing argument 1 of
=E2=80=98QuantizeSubband=E2=80=99 from incompatible pointer type [-Wincompa=
tible-pointer-types]
  695 |                                 QuantizeSubband                 (
subq[Band].L, subx[Band].L, *resL, errorL [Band], MAX_NS_ORDER );
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
~~~~~~~~~~^~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    mpc_int16_t * {aka short int *}
musepack_src_r475/mpcenc/mpcenc.h:257:56: note: expected =E2=80=98unsigned =
int *=E2=80=99 but
argument is of type =E2=80=98mpc_int16_t *=E2=80=99 {aka =E2=80=98short int=
 *=E2=80=99}
  257 | void   QuantizeSubband                 ( unsigned int* qu_output, c=
onst
float* input, const int res, float* errors, const int maxNsOrder );
      |                                          ~~~~~~~~~~~~~~^~~~~~~~~
musepack_src_r475/mpcenc/mpcenc.c:702:61: error: passing argument 1 of
=E2=80=98QuantizeSubbandWithNoiseShaping=E2=80=99 from incompatible pointer=
 type
[-Wincompatible-pointer-types]
  702 |                 QuantizeSubbandWithNoiseShaping ( subq[Band].R,
subx[Band].R, *resR, errorR [Band], m->FIR_R [Band] );
      |                                                   ~~~~~~~~~~^~
      |                                                             |
      |                                                             mpc_int=
16_t
* {aka short int *}
musepack_src_r475/mpcenc/mpcenc.c:705:77: error: passing argument 1 of
=E2=80=98QuantizeSubband=E2=80=99 from incompatible pointer type [-Wincompa=
tible-pointer-types]
  705 |                                 QuantizeSubband                 (
subq[Band].R, subx[Band].R, *resR, errorL [Band], MAX_NS_ORDER);
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
~~~~~~~~~~^~
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    |
      |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    mpc_int16_t * {aka short int *}

See the meta bug#1220571 for more info.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17097083473.B1ba3CB.1425--

summary: GCC 14: musepack package fails