It is a failed build. If you walk through the .spec file you could find ExclusiveArch: s390x x86_64, plus the build for x86_64 (Search at the end of the spec file).Hello,Please refer to the .spec file in - https://build.opensuse.org/projects/Base:System/packages/s390-tools/files/s390-tools.spec?expand=1The ticket I have created is SUSE bugzilla ticket, not openSUSE. Please refer the corresponding github issue - https://github.com/ibm-s390-linux/s390-tools/issues/173There is another issue with 2.34, too - https://github.com/ibm-s390-linux/s390-tools/issues/174Regards,On Mon, Aug 26, 2024 at 9:02 AM Sarah Julia Kriesch <ada.lovelace@gmx.de> wrote:Hi Nikolay,
Thank you for the hint wirh the bug.
Can you give us the link to the openSUSE Bugzilla, that we can keep also an eye on it, please?
Best regards,
Sarah
> Gesendet: Sonntag, den 25.08.2024 um 20:40 Uhr
> Von: "Nikolay GUEORGUIEV" <nikolay.gueorguiev@suse.com>
> An: "Holger Rauch" <holger.rauch@posteo.de>
> Cc: "Raphael Groner" <projects.rg@smart.ms>, zsystems@lists.opensuse.org
> Betreff: Re: Aw: More Recent Version For s390-tools (2.31 => 2.34) on Tumbleweed
>
> Hello,
>
> Currently, I am in process upgrading s390-tools to 2.34 on Factory. There
> is a Rust compilation error during the build process. IBM are working on
> patch to fix the issue. There is workaround suggested by IBM for the moment.
>
> Kind regards,
>
> On Sun, Aug 25, 2024, 20:26 Holger Rauch <holger.rauch@posteo.de> wrote:
>
> > Hi Raphael,
> >
> > thanks for the hint regarding Fedora. Will have to look into the particular
> > patch in more detail.
> >
> > Kind regards,
> >
> > Holger
> >
> > On So, 25 Aug 2024, Raphael Groner wrote:
> >
> > > Hi Holger,
> > >
> > > FTR in Fedora, rebased successfully about two weeks ago. Be aware there
> > has
> > > been an interim patch needed for prior version 2.33.1 but don't ask me
> > for
> > > reason maybe Dan as maintainer knows better.
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2302462
> > >
> > > Regards
> > > Raphael
> > >
> > > P. S. Reception from mailing list does work now for me, finally. Thanks
> > again
> > > to Christian for the fix.
> > >
> > >
> > > Am 25.08.24, 18:00 schrieb Sarah Julia Kriesch <ada.lovelace@gmx.de>:
> > >
> > > Hi Holger,
> > >
> > > the package was in openSUSE zSystems in the past, but was changed to
> > > openSUSE Factory by the new Maintainer at SUSE.
> > >
> > > The old package maintainer had also the required permissions to
> > review and
> > > submit to openSUSE zSystems. I don't know, why the new Maintainer
> > does not
> > > want to have any contact to us and therefore did not ask for the
> > > permissions.
> > >
> > > SUSE is using an older kernel. Therefore, s390-tools are not on the
> > top
> > > priority list by the new Maintainer.
> > >
> > > I hope that makes the reasons clear.
> > > Best regards,
> > > Sarah
> > >
> > > > Gesendet: Sonntag, den 25.08.2024 um 17:46 Uhr
> > > > Von: "Holger Rauch" <holger.rauch@posteo.de>
> > > > An: zsystems@lists.opensuse.org
> > > > Betreff: More Recent Version For s390-tools (2.31 => 2.34) on
> > Tumbleweed
> > > >
> > > > Hello to all ZSystems list members,
> > > >
> > > > I've got a few questions concerning the s390-tools package:
> > > >
> > > > - According to
> > > >
> > > > https://github.com/ibm-s390-linux/s390-tools/releases
> > > >
> > > > the most current release would be 2.34, which is also intended
> > > > specifically for 6.10 kernels. As 6.10 kernels are the current
> > ones on
> > > > Tumbleweed for s390x, an upgrade seems reasonable.
> > > >
> > > > - Are there any technical reasons why the package release hasn't
> > been
> > > > upgraded since February this year, despite the fact that newer
> > kernels
> > > for
> > > > s390x have been made available?
> > > >
> > > > - As this package is intended for the base system of s390x only, I
> > wonder
> > > why
> > > > this package is built in
> > > >
> > > > openSUSE:Factory
> > > >
> > > > instead of the ZSystems-specific factory
> > > >
> > > > openSUSE:Factory:zSystems ?
> > > >
> > > > - What would be possible reasons for NOT upgrading this package to
> > its
> > > > current release 2.34 and stay with the current one 2.31 instead?
> > > >
> > > > Thanks for any additional info/clarifications.
> > > >
> > > > Kind regards,
> > > >
> > > > Holger
> > > >
> > >
> >