openSUSE:Factory - Build fail notification
Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - NumCpp: Fails to build - OOKiedokie: Fails to build - Regina-REXX: Fails to build - asusfan: Fails to build - authselect: Fails to build - cgdb: Fails to build - cinnamon-branding-openSUSE: Fails to build - ckermit: Fails to build - clustduct: Fails to build - cmpi-bindings: Fails to build - compface: Fails to build - compiz-plugins-extra: Fails to build - compsize: Fails to build - dump1090-fa: Fails to build - eciadsl-usermode: Fails to build - eekboard: Fails to build - erldash: Fails to build - fairymax: Fails to build - fdo-client: Fails to build - ffsb: Fails to build - frink: Fails to build - fritzing: Fails to build - galene: Fails to build - gammu: Fails to build - gcad3d: Fails to build - genders: Fails to build - gimp-gap: Fails to build - gnu-cobol: Fails to build - goldendict-ng: Fails to build - gqlplus: Fails to build - gtk-sharp3: Fails to build - hcode: Fails to build - hoard: Fails to build - iasimage: Fails to build - ibus-kkc: Fails to build - input-pad: Fails to build - interbench: Fails to build - kubeconform: Fails to build - lastpass-cli: Fails to build - latrace: Fails to build - ldapvi: Fails to build - leftwm: Fails to build - lemon: Fails to build - libGLC: Fails to build - libargtable2: Fails to build - libclaw: Fails to build - libcli: Fails to build - libfm: Fails to build - libisds: Fails to build - librep: Fails to build - libskk: Fails to build - libstfl: Fails to build - lmarbles: Fails to build - luvcview: Fails to build - macchina: Fails to build - maelstrom: Fails to build - manaplus: Fails to build - matrix-quaternion: Uninstallable: nothing provides libQuotientQt6.so.0.8()(64bit) needed by matrix-quaternion-0.0.95.84+git.20230827.3d7083a.x86_64 - mined: Fails to build - monitoring-plugins-mysql_health: Fails to build - moolticute: Fails to build - mozilla-zilla-slab-fonts: Fails to build - mozldap: Fails to build - mp: Fails to build - mrsh: Fails to build - ncftp: Fails to build - ncspot: Fails to build - netdate: Fails to build - nfswatch: Fails to build - nim: Fails to build - notmuch: Fails to build - obconf: Fails to build - octave-forge-tisean: Fails to build - octave-forge-vrml: Fails to build - openlierox: Fails to build - openvas-smb: Fails to build - openvino: Uninstallable: nothing provides libprotobuf-lite.so.25.4.0()(64bit) needed by libopenvino_onnx_frontend2440-2024.4.0.x86_64 - oto: Fails to build - owncloud-client: Fails to build - packETH: Fails to build - parsec: Fails to build - pcsc-gempc: Fails to build - perl-Authen-SASL-Cyrus: Fails to build - perl-DateTime-Format-Flexible: Fails to build - perl-GnuPG-Interface: Fails to build - perl-Inline-Python: Fails to build - perl-Net-AMQP-RabbitMQ: Fails to build - perl-Net-IDN-Encode: Fails to build - perl-UNIVERSAL-moniker: Fails to build - pidgin-sipe: Fails to build - pingtunnel: Fails to build - pocketsphinx: Fails to build - pongix: Fails to build - postfish: Fails to build - prelude-lml-rules: Fails to build - python-Kivy: Fails to build - python-aws-xray-sdk: Fails to build - python-dbus_fast: Fails to build - python-django-bootstrap3: Fails to build - python-django-contrib-comments: Fails to build - python-django-extensions: Fails to build - python-django-seed: Fails to build - python-django-sortedm2m: Fails to build - python-gpt4all: Fails to build - python-jenkinsapi: Fails to build - python-neovim: Fails to build - python-novaclient: Fails to build - python-pip-tools: Fails to build - python-pscript: Fails to build - python-py-gitea-opensuse-org: Fails to build - python-py-moneyed: Fails to build - qdl: Fails to build - qxmledit: Fails to build - reaim: Fails to build - rep-gtk: Fails to build - resample: Fails to build - rinetd: Fails to build - rox-filer: Fails to build - schedtool: Fails to build - scim-skk: Fails to build - scmon: Fails to build - sdcv: Fails to build - sgrep: Fails to build - sleuth: Fails to build - slrn: Fails to build - snack: Fails to build - softhsm: Fails to build - spacefm: Fails to build - sphinx: Fails to build - sphinxbase: Fails to build - sphinxbase5: Fails to build - stardict: Fails to build - taigo: Fails to build - terminus: Fails to build - thttpd: Fails to build - tint2: Fails to build - tktable: Fails to build - torsocks: Fails to build - ttf2pt1: Fails to build - upm: Fails to build - veyon: Fails to build - virt-scenario: Fails to build - vocal: Fails to build - wine-nine-standalone: Fails to build - xar: Fails to build - xbench: Fails to build - xcolors: Fails to build - xengine: Fails to build - xf86-video-fbturbo: Fails to build - xf86-video-fbturbo-live: Fails to build - xmgrace: Fails to build - xmorph: Fails to build - xroach: Fails to build - zile: Fails to build Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar@opensuse.org>
Am 30.11.24 um 00:04 schrieb DimStar / Dominique Leuenberger:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
This is a very long list. Is there the possibility that there is a pattern to this failures you already noticed (like "gcc-4711 update needs additional #include <foobar.h> now which was not needed before") that hints at an easy to do mass-job for a lazy sunday afternoon? It would be much more likely for me to say "ok, let's take on a few of these easy ones" even if I never had to do with the package and I never intend to ever use it *IF* there was information like that available ;-)
Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory.
Kind regards, DimStar / Dominique Leuenberger <dimstar@opensuse.org>
Best regards, seife -- Stefan Seyfried "Once the rockets are up, who cares where they come down? That's not my department!" says Wernher von Braun -- Tom Lehrer
Am 01.12.24 um 10:39 schrieb Stefan Seyfried via openSUSE Factory:
Am 30.11.24 um 00:04 schrieb DimStar / Dominique Leuenberger:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks.
This is a very long list. Is there the possibility that there is a pattern to this failures you already noticed (like "gcc-4711 update needs additional #include <foobar.h> now which was not needed before") that hints at an easy to do mass-job for a lazy sunday afternoon?
It would be much more likely for me to say "ok, let's take on a few of these easy ones" even if I never had to do with the package and I never intend to ever use it *IF* there was information like that available ;-)
The python313 flavor activation is one of the reasons. Unfortunately there is no common pattern, just "update to the latest upstream dealing with it". - Ben
On Sun, Dec 01, 2024 at 10:39:27AM +0100, Stefan Seyfried via openSUSE Factory wrote:
Am 30.11.24 um 00:04 schrieb DimStar / Dominique Leuenberger:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
This is a very long list. Is there the possibility that there is a pattern to this failures
sphinx is broken, and it looks like other programs are broken by sphinx (I checked notmuch which piqued my interest). Not sure why sphinx is broken all of a sudden, here's the error:
[ 73s] test.c: In function ‘test_persist_work’: [ 73s] test.c:274:58: error: passing argument 3 of ‘sphinx_build_excerpts’ from incompatible pointer type [-Wincompatible-pointer-types] [ 73s] 274 | res = sphinx_build_excerpts ( client, 1, docs, index, words, &opts ); [ 73s] | ^~~~ [ 73s] | | [ 73s] | char ** [ 73s] In file included from test.c:27: [ 73s] sphinxclient.h:252:143: note: expected ‘const char **’ but argument is of type ‘char **’ [ 73s] 252 | char ** sphinx_build_excerpts ( sphinx_client * client, int num_docs, const char ** docs, const char * index, const char * words, sphinx_excerpt_options * opts ); [ 73s] | ~~~~~~~~~~~~~~^~~~ [ 73s] test.c: In function ‘title’: [ 73s] test.c:411:24: warning: ' ' flag used with ‘%s’ gnu_printf format [-Wformat=] [ 73s] 411 | printf ( "-> % s <-\n\n", name ); [ 73s] | ^ [ 73s] make[1]: *** [Makefile:303: test.o] Error 1 [ 73s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/sphinx-2.2.11-release/api/libsphinxclient' [ 73s] make: *** [Makefile:202: all] Error 2 [ 73s] error: Bad exit status from /var/tmp/rpm-tmp.8PRywX (%build)
-- Filippo Bonazzi Security Engineer suse.com 8257 4398 947A 2DBE F21D 76E6 937A 63F0 5B36 46D9
that's another gcc14-induced compile time error... fixed in OBS SR 1227745 building the package throws oodles of compiler warnings "ISO C++17 does not allow ‘register’ storage class specifier [-Wregister]" -- probably these should be handled as well... ~ On 12/2/24 10:55, Filippo Bonazzi wrote:
On Sun, Dec 01, 2024 at 10:39:27AM +0100, Stefan Seyfried via openSUSE Factory wrote:
Am 30.11.24 um 00:04 schrieb DimStar / Dominique Leuenberger:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
This is a very long list. Is there the possibility that there is a pattern to this failures
sphinx is broken, and it looks like other programs are broken by sphinx (I checked notmuch which piqued my interest).
Not sure why sphinx is broken all of a sudden, here's the error:
[ 73s] test.c: In function ‘test_persist_work’: [ 73s] test.c:274:58: error: passing argument 3 of ‘sphinx_build_excerpts’ from incompatible pointer type [- Wincompatible-pointer-types] [ 73s] 274 | res = sphinx_build_excerpts ( client, 1, docs, index, words, &opts ); [ 73s] | ^~~~ [ 73s] | | [ 73s] | char ** [ 73s] In file included from test.c:27: [ 73s] sphinxclient.h:252:143: note: expected ‘const char **’ but argument is of type ‘char **’ [ 73s] 252 | char ** sphinx_build_excerpts ( sphinx_client * client, int num_docs, const char ** docs, const char * index, const char * words, sphinx_excerpt_options * opts ); [ 73s] | ~~~~~~~~~~~~~~^~~~ [ 73s] test.c: In function ‘title’: [ 73s] test.c:411:24: warning: ' ' flag used with ‘%s’ gnu_printf format [-Wformat=] [ 73s] 411 | printf ( "-> % s <-\n\n", name ); [ 73s] | ^ [ 73s] make[1]: *** [Makefile:303: test.o] Error 1 [ 73s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/ sphinx-2.2.11-release/api/libsphinxclient' [ 73s] make: *** [Makefile:202: all] Error 2 [ 73s] error: Bad exit status from /var/tmp/rpm-tmp.8PRywX (%build)
On Sun, Dec 01 2024, Stefan Seyfried via openSUSE Factory wrote:
Am 30.11.24 um 00:04 schrieb DimStar / Dominique Leuenberger:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
This is a very long list. Is there the possibility that there is a pattern to this failures you already noticed (like "gcc-4711 update needs additional #include <foobar.h> now which was not needed before") that hints at an easy to do mass-job for a lazy sunday afternoon?
I assume that something triggered a rebuild of a fairly big number of packages and many of those fail to build with GCC 14 because they violate C99 in ways GCC no longer permits (by default). At least I was anticipating the failure of gnu-cobol for this reason for quite some time.
It would be much more likely for me to say "ok, let's take on a few of these easy ones" even if I never had to do with the package and I never intend to ever use it *IF* there was information like that available ;-)
Please have a look at https://bugzilla.opensuse.org/show_bug.cgi?id=1220571 and the few links leading from it (and perhaps not so few depending, but often fixed, bugs). Any help with this is greatly appreciated! Martin
Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory.
Kind regards, DimStar / Dominique Leuenberger <dimstar@opensuse.org>
Best regards,
seife -- Stefan Seyfried
"Once the rockets are up, who cares where they come down? That's not my department!" says Wernher von Braun -- Tom Lehrer
On Fri, Nov 29 2024, DimStar / Dominique Leuenberger wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
[...]
- gnu-cobol: Fails to build
I have submitted https://build.opensuse.org/requests/1189424#comment-1966142 which I believe will fix this four months ago but so far it did not get reviewed. Martin
Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory.
Kind regards, DimStar / Dominique Leuenberger <dimstar@opensuse.org>
Hi, On 11/30/24 12:04 AM, DimStar / Dominique Leuenberger wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
- compsize: Fails to build sr#1227741 should fix the build issues. I also pulled in a few bug fixes from git master while I was at it.
All the best, Wolfgang
Hi, On Fri, 2024-11-29 at 23:04 +0000, DimStar / Dominique Leuenberger wrote:
- kubeconform: Fails to build
I think this is a problem in the openSUSE go toolchain. I can build locally just fine with go 1.22 and 1.23, but on OBS this fails with [ 8s] /usr/lib64/go/1.23/src/cmd/vendor/github.com/google/pprof/third_party/s vgpan/svgpan.go:10:12: pattern svgpan.js: no matching files found I filed https://bugzilla.opensuse.org/show_bug.cgi?id=1233357 on Nov the 14th but I got no replies. I am not sure how to fix the OBS build, help would be welcome. Thanks, Robert
participants (8)
-
Ben Greiner -
DimStar / Dominique Leuenberger -
Filippo Bonazzi -
Friedrich Haubensak -
Martin Jambor -
Robert Munteanu -
Stefan Seyfried -
Wolfgang Frisch