Can somebody cancel the bigloo build? It's been running for several days and is obviously off in the weeds. I'll investigate.

On Mon, Jan 23, 2023 at 05:44:16PM +0100, Tomas Hrcka wrote: > Things still needing rebuilding > https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html What is the significance of packages that appear on this list? ocaml-mysql appears there, and it does not look like a rebuild was attempted: https://koji.fedoraproject.org/koji/packageinfo?packageID=ocaml-mysql

On Mon, Jan 23, 2023 at 07:50:19PM +0100, Dan Horák wrote: > On Mon, 23 Jan 2023 18:44:00 +0000 > "Richard W.M. Jones" <rjones(a)redhat.com&gt; wrote: > > > On Mon, Jan 23, 2023 at 05:44:16PM +0100, Tomas Hrcka wrote: > > > Things still needing rebuilding > > > https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html > > >   > > > > What is the significance of packages that appear on this list? > > > > ocaml-mysql appears there, and it does not look like a rebuild > > was > > attempted: > > https://koji.fedoraproject.org/koji/packageinfo?packageID=ocaml-mysql > > this situation usually means the build failed in the "create SRPM > from > dist-git" phase Looking at my own packages, e.g. yaksa had a build attempt that seems to hang: https://koji.fedoraproject.org/koji/buildinfo?buildID=2135007

Zbyszek _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote: > I have some packages failed. > One of them libtins. Problem is that: > > error: 'uint32_t' is not a member of 'std'; > > Is it normal? Is it GCC 13 change? See https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes Some libstdc++ headers included <cstdint> in older versions as an implementation detail but no longer do. Including stdint.h will introduce ::uint32_t type among others, but not std::uint32_t, if you use the latter, you need to include <cstdint>.

On 24/01/2023 07:28, Jeff Law wrote: > > > On 1/24/23 00:16, Jakub Jelinek wrote: > > On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote: > > > I have some packages failed. > > > One of them libtins. Problem is that: > > > > > > error: 'uint32_t' is not a member of 'std'; > > > > > > Is it normal? Is it GCC 13 change? > > > > See > > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes > > Some libstdc++ headers included <cstdint> in older versions > > as an implementation detail but no longer do. > > > > Including stdint.h will introduce ::uint32_t type among others, > > but not std::uint32_t, if you use the latter, you need to > > include <cstdint>. > I've got a partial list of packages affected by the ongoing header > cleanups in libstdc++: mapnik was affected as well but I fixed it last night.

On 1/24/23 00:16, Jakub Jelinek wrote: > See > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes > Some libstdc++ headers included <cstdint> in older versions > as an implementation detail but no longer do. > > Including stdint.h will introduce ::uint32_t type among others, > but not std::uint32_t, if you use the latter, you need to > include <cstdint>. I've got a partial list of packages affected by the ongoing header cleanups in libstdc++:

<somewhat_offtopic> On Tue, Jan 24, 2023 at 7:29 AM Jeff Law <jeffreyalaw(a)gmail.com&gt; wrote: > On 1/24/23 00:16, Jakub Jelinek wrote: > > See > > https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes > > Some libstdc++ headers included <cstdint> in older versions > > as an implementation detail but no longer do. > > > > Including stdint.h will introduce ::uint32_t type among others, > > but not std::uint32_t, if you use the latter, you need to > > include <cstdint>. > I've got a partial list of packages affected by the ongoing header > cleanups in libstdc++: I am in favor of header cleanups, and moving forward with new(er) gcc versions, but I wonder that if in the future the Fedora gcc change proposal can reference the porting changes rather than referring only to the main gcc docs as an additional heads up (in this case, I skimmed the gcc 13 changes page, but you had to follow yet another link for porting issues to see the library header changes (and I did not go looking there, my bad)).

While it may take me only a minute to recognize the issue when I see the compile failure for a missing header ("and there they go again..."), writing PRs for upstreams and getting those fixes into their release cycle may take somewhat longer (and I prefer not to carry local patches in packages when possible). Had I seen cstdint I like to think that I would have tried a rebuild with gcc 13 earlier to see what (if any) upstream(s) needed some encouragement for support gcc 13.

I have some packages failed. One of them libtins. Problem is that: error: 'uint32_t' is not a member of 'std'; Is it normal? Is it GCC 13 change? I must patch sources now? sed -i 's|stdint.h|cstdint|' include/tins/ip_address.h

On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote: > On Mon, Jan 23, 2023 at 10:26:18PM +0000, Sérgio Basto wrote: > > > > I found more 5 with > > https://koji.fedoraproject.org/koji/tasks?owner=releng&state=active&a... > > > > 96481236 build (f38-rebuild, > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa) > > > > 96474133 build (f38-rebuild, /rpms/trace- > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080) > > > > 96404064 build (f38-rebuild, /rpms/perl- > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967) > > > > 96383273 build (f38-rebuild, > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d > > > > 96368979 build (f38-rebuild, > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1ff) > > Yes, I have canceled all those now. I started builds for all of those now.

On Mon, Jan 30, 2023 at 04:45:37PM -0800, Kevin Fenzi wrote: > On Tue, Jan 24, 2023 at 09:42:10AM +0000, Zbigniew Jędrzejewski- > Szmek wrote: > > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote: > > > On Mon, Jan 23, 2023 at 10:26:18PM +0000, Sérgio Basto wrote: > > > > > > > > I found more 5 with > > > > https://koji.fedoraproject.org/koji/tasks?owner=releng&state=active&a... > > > > > > > > 96481236         build (f38-rebuild, > > > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa) > > > > > > > > 96474133         build (f38-rebuild, /rpms/trace- > > > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080) > > > > > > > > 96404064         build (f38-rebuild, /rpms/perl- > > > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967) > > > > > > > > 96383273         build (f38-rebuild, > > > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d > > > > > > > > 96368979         build (f38-rebuild, > > > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1f > > > > f) > > > > > > Yes, I have canceled all those now. > > > > I started builds for all of those now. > > All of them have hung again after running since you started them. > > I think someone is going to need to try and build them in local > mock and > see where they are getting stuck. > > Can you cancel them again? Or would you like me to try and look and > see > what they are hung on? I cancelled them now. All five were still hung. It's up to the maintainers to figure out what is going. E.g. yaksa was hanging in tests…

Zbyszek _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On Wed, 08 Feb 2023 15:24:47 +0000 Sérgio Basto <sergio(a)serjux.com&gt; wrote: > On Tue, 2023-01-31 at 12:03 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Jan 30, 2023 at 04:45:37PM -0800, Kevin Fenzi wrote: > > > On Tue, Jan 24, 2023 at 09:42:10AM +0000, Zbigniew Jędrzejewski- > > > Szmek wrote: > > > > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote: > > > > > On Mon, Jan 23, 2023 at 10:26:18PM +0000, Sérgio Basto wrote: > > > > > > > > > > > > I found more 5 with > > > > > > https://koji.fedoraproject.org/koji/tasks?owner=releng&state=active&a... > > > > > > > > > > > > 96481236         build (f38-rebuild, > > > > > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa) > > > > > > > > > > > > 96474133         build (f38-rebuild, /rpms/trace- > > > > > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080) > > > > > > > > > > > > 96404064         build (f38-rebuild, /rpms/perl- > > > > > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967) > > > > > > > > > > > > 96383273         build (f38-rebuild, > > > > > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d > > > > > > > > > > > > 96368979         build (f38-rebuild, > > > > > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1f > > > > > > f) > > > > > > > > > > Yes, I have canceled all those now. > > > > > > > > I started builds for all of those now. > > > > > > All of them have hung again after running since you started them. > > > > > > I think someone is going to need to try and build them in local > > > mock and > > > see where they are getting stuck. > > > > > > Can you cancel them again? Or would you like me to try and look and > > > see > > > what they are hung on? > > > > I cancelled them now. All five were still hung. > > It's up to the maintainers to figure out what is going. > > E.g. yaksa was hanging in tests… > > Any news about these packages that hang on koji ? we may include opencv > package on this list. > > Last lines of build opencv on ppc64le are [1] and after we got 55385703 > (55 millions) of lines with "mashing detected" message, the log file > have 2,30G ! > > Also I see "buffer overflow detected ***: terminated cat: /symlink2- > fakechroot: No such file or directory " on fakechroot this looks weird, I am trying a local build

On Mon, Jan 23, 2023 at 07:50:19PM +0100, Dan Horák wrote: > On Mon, 23 Jan 2023 18:44:00 +0000 > "Richard W.M. Jones" <rjones(a)redhat.com&gt; wrote: > > > On Mon, Jan 23, 2023 at 05:44:16PM +0100, Tomas Hrcka wrote: > > > Things still needing rebuilding > > > https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html > > > > What is the significance of packages that appear on this list? > > > > ocaml-mysql appears there, and it does not look like a rebuild was > > attempted: > > https://koji.fedoraproject.org/koji/packageinfo?packageID=ocaml-mysql > > this situation usually means the build failed in the "create SRPM from > dist-git" phase Got it, thanks. I updated it to the latest version and submitted a build and indeed the buildroot can't be built: https://koji.fedoraproject.org/koji/taskinfo?taskID=96590546 The error is some Python / dbus / glib2 / gnutls dependency failure which makes no sense because the package is using none of those.

I wanted to resubmit one of my failed builds, but the buildroot seems to be broken currently: > Problem 1: package python3-dnf-4.14.0-2.fc38.noarch requires libmodulemd >= 2.9.3, but none of the providers can be installed > - package libmodulemd-2.14.0-5.fc38.x86_64 requires libglib-2.0.so.0()(64bit), but none of the providers can be installed > - package libmodulemd-2.14.0-5.fc38.x86_64 requires libgobject-2.0.so.0()(64bit), but none of the providers can be installed > - package dnf-4.14.0-2.fc38.noarch requires python3-dnf = 4.14.0-2.fc38, but none of the providers can be installed > - package glib2-2.74.1-3.fc38.x86_64 requires libgnutls.so.30()(64bit), but none of the providers can be installed > - conflicting requests > - nothing provides libunistring.so.2()(64bit) needed by gnutls-3.7.8-11.fc38.x86_64 > Problem 2: package python3-dnf-plugins-core-4.3.1-2.fc38.noarch requires python3-dbus, but none of the providers can be installed > - package python3-dbus-1.3.2-2.fc38.x86_64 requires libglib-2.0.so.0()(64bit), but none of the providers can be installed > - package dnf-plugins-core-4.3.1-2.fc38.noarch requires python3-dnf-plugins-core = 4.3.1-2.fc38, but none of the providers can be installed > - package glib2-2.74.1-3.fc38.x86_64 requires libgnutls.so.30()(64bit), but none of the providers can be installed > - conflicting requests > - nothing provides libunistring.so.2()(64bit) needed by gnutls-3.7.8-11.fc38.x86_64 A.FI. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On Mon, Jan 23, 2023 at 01:36:10PM -0600, Jonathan Wright via devel wrote: > I'm seeing the same errors on rawhide buildroot right now. The problem was libunistring-1.1-3.fc38 (again). We untagged it in december, but looks like no one followed up to get dependent packages rebuilt: https://pagure.io/releng/issue/11175 I have untagged it (again) for now.

kevin _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

cqrlog - Fails for some weird lazbuild issue I don't understand

On Tue, Jan 24, 2023 at 7:20 AM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote: > hobbes1069 (9): > cqrlog - Fails for some weird lazbuild issue I don't understand > flnet - Spec conditional oops. Fixed. > flrig - Needed cstdint. Fixed > freecad - Needs cstdint. Working on it. > gmsh - Needed cstdint. Fixed. > openCOLLADA - error: possibly dangling reference to a temporary. Don't > know how to fix this one. > opencascade - error: declaration of 'tbb::task& > tbb::internal::task_prefix::task()' changes meaning of 'task' > openexr - Needed cstdint. Fixed. > spnavcfg - https://github.com/FreeSpacenav/spnavcfg/issues/30 > I think I've gotten everything situated except openCOLLADA.

On Mon, Jan 23, 2023 at 6:23 PM Tomas Hrcka <thrcka(a)redhat.com&gt; wrote: > The mass rebuild was done in a side tag (f38-rebuild) and moved over to > f38. Failures can be seen at > https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html

On Mon, Jan 23, 2023 at 08:11:03PM -0500, Rafael Aquini wrote: > FYI: > > memkind failure (aarch64) seems to be koji/mock related: > > This package was updated and sucessfully built in rawhide and f37 a week > ago (01/13) > > ---8<--- > > EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M > b67a9ff69f3540e9bb559e45f9dafdf5 -D > /var/lib/mock/f38-build-40444675-4981555/root -a -u mockbuild > --capability=cap_ipc_lock > --bind=/tmp/mock-resolv._3nfqeom:/etc/resolv.conf > --bind=/dev/btrfs-control --bind=/dev/mapper/control > --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 > --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 > --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 > --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 > --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 > --setenv=SHELL=/bin/bash --setenv=HOME=/builddir > --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin > --setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007" > --setenv=PS1=<mock-chroot> \\s-\\v\\$ --setenv=LANG=C.UTF-8 > --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --noclean > --target aarch64 --nodeps /builddir/build/SPECS/memkind.spec\n', 1)] > Traceback (most recent call last): > File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py", > line 93, in trace > result = func(*args, **kw) > > --->8--- Very odd failure. :( It looks like it finished linking and then somehow systemd-nspawn crashed, but I don't see in the logs any reason why. :( I'd say try a scratch build and if that works, just resubmit it?

On 23. 01. 23 17:44, Tomas Hrcka wrote: > FTBFS bugs will be filed shortly. Is there an estimated date when this will happen?