Bug 2045255

Created attachment 1853797 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Created attachment 1853798 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Created attachment 1853799 [details]
state.log

This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 37.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2022-03-22).

A week before the mass branching of Fedora 38 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 36 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

I think I can look at this now.  Hopefully just new compiler versions.

*** Bug 2098683 has been marked as a duplicate of this bug. ***

This Bugzilla was ASSIGNED on 2022-04-26 but nothing happened. We are past Fedora 37 Beta Freeze and this package does not even install. What is the plan wrt this package? Can it please be removed from the distribution until this is solved?

The plan was to upgrade to the new releases - which depend on rust-sodiumoxide. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2121490 I have been working on the dependencies for that.  The new releases build and install on my dev system - which has the rust packages built and in my private repo.

I could work a little on why the old release no longer builds to unstick the works.  Is that a better idea?

> Is that a better idea?

I don't know. I guess either works. Thanks for the update.

I have some backported patches for the 21.1 C code.  It now builds running build steps in mock container from terminal, BUT not from rpmbuild -bc.  I think I should go ahead and push those changes for f37 (but not rawhide).  I can always merge from rawhide if the rust stuff for 21.2 becomes available.

What about vendoring the rust-sodiumoxide  packages in cjdns until they are ready?

Thanks. I'd just push the workaround to f37 and rawhide both and revert it later when rust-sodiumoxide is available.

Sigh.  Now the bundle libuv won't build with gcc-12.  I could try to patch for current libuv again, but that didn't work well last time (compiled, but the event handling doesn't seem to be compatible).

The Fedora Engineering Steering Committee has approved [1] to retire the remaining non-installable packages still depending on Python 3.10 from Fedora 37 and Rawhide 1-2 days before the final freeze. We plan to retire this package this Sunday: 2022-10-02. If you wish to fix this package for time for Fedora 37 GA, please request a freeze exception [2].

[1] https://pagure.io/fesco/issue/2876
[2] https://qa.fedoraproject.org/blockerbugs/propose_bug

I have Caleb, the upstream author, working on the build problem.  I don't want to hold up the freeze, but if there is anyway to avoid retiring cjdns, I would appreciate it.  I am getting close, I promise!

Proposed as a Freeze Exception for 38-beta by Fedora user sdgathman using the blocker tracking app because:

 I have Caleb, the upsteam author, help me debug the build problem.  We are making progress.

No info needed from me.

But changing the exception request from Feodra 38 Beta to Fedora 37 Final.

Discussed during the 2022-10-03 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made:

"The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update."

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-10-03/f37-blocker-review.2022-10-03-16.00.log.txt

Do you have a work-in-progress state of the spec file I can try poking?

Pushed to rawhide.  You'll need the rust dependencies, which are all straight rust2rpm - but I have review requests open for them.  I am using locally built rust packages at https://gathman.org/linux/f37/  The gathmnan-release package has repo.  (OT: I am not sure if a local repo package should stick keys in /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-gathman - so you'll have to copy/link it there for use with mock.)  I am building for f37.

I have a f37 vm set up for Caleb - I'm sure you have your own, but can supply if needed.

How can I help to move the package reviews forward? Fabio seems to be on top of things there.

Fabio says I've somehow "opted out" of %rpmautospec for rust-libsodium-sys.  I will rerun rust2rpm now and see if it works any different.

I have approved rust-libsodium-sys and will push some fixes with a follow-up commit once it's imported.
The other three pending review requests are still waiting for input from their submitters.

At this point, I'd feel much safer if we retired the package for now before F37 repos are frozen, and reintroduced it with a bodhi update once ready. Is that OK? It creates a bit of a mess in dist git history, but other than that should be quite safe.

Note that F37 repos are already frozen since last week, and that you will need releng intervention to retire packages.

Yes, but this has a freeze exception. The problem is we don't know what is the real deadline.

The f35 package installs and runs in f37 and f38.  The python subpackages can be built separately as noarch with Latest Python.  Does that help?

Recent findings from Caleb:

     Only happens in your build env
     And only happens if it's built BY the Rust build-script, invoking nodejs directly is fine
     Happens with or without your CFLAGS
     But if your CFLAGS are duplicated many times, the error message is also duplicated

We are trying clang.  It looks like I have to master Rust enough to modify build.rs

(In reply to Stuart D Gathman from comment #29)
> The f35 package installs and runs in f37 and f38.  The python subpackages
> can be built separately as noarch with Latest Python.  Does that help?

Not really, as long as the old Python subpackages are in the repository (and we cannot remove them without removing all of them).

The target date for Fedora 37 final shifted to 15 November.

Do you still anticipate getting the rust dependencies in Fedora in time for Fedora 37 release?

(In reply to Miro Hrončok from comment #33)
> Do you still anticipate getting the rust dependencies in Fedora in time for
> Fedora 37 release?

Doesn't look like it.  If package gets retired - what happens to the EPEL packages (which still build)?
I am going to make one more try with same upstream release as f35 which doesn't have the Rust dependencies.  I can't remember if I tried just removing -Werror from build scripts.

It would only be retired in f37 and f38. If it is in EPEL, it stays there.

I can build cjdns in f38,f37,f36 by this procedure:
mock -r fedora-3X-x86_64 cjdns-21.1-7.fc38.src.rpm
... fails on a randomly selected Linking step.  Build script output is "eaten" by rpmbuild and sent somewhere, maybe /dev/null

mock -r fedora-3X-x86_64 --shell
su - mockbuild
cd build/BUILD/cjdns-21.1
NO_TEST=1  CJDNS_RELEASE_VERSION="cjdns=21.1-7.fc38" ./do
... builds correctly with build script output visible

cd ../../SPECS
rpmbuild -bi --short-circuit cjdns.spec
rpmbuild -bb --short-circuit cjdns.spec

Now I can add the rpms to my personal repo.  But that doesn't fix the FTBFS for Fedora.  What is going on with rpmbuild?  Why did it start eating the output of the build script in f36?  I suspect it has something to do with nodejs, as that changed with f36 and the build script is nodejs.

- one part of the problem is missing BuildRequires: gcc-c++
- also for debugging purposes it would be useful to switch off "parallel build", so it's easier to correlate possible error messages to what is going on

Had BR g++.  And changing to gcc-c++ doesn't change anything.  Yes, the issue seems to be related to parallel build - but I have no clue how to turn off for make.js.

https://github.com/cjdelisle/cjdns/blob/master/node_build/builder.js#L786 contains the logic to set the parallelism. I would try replacing it with "1" ...

Thanks.  With that patch, it now consistently fails on cjdroute2.c.  This is much more helpful.  The other reported failing files were red herrings, arguably an error reporting bug.  I am now trying the lastest version on github.

Latest version adds at least 9 more rust crypto dependencies not packaged for Fedora.  :-(

Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 38.

Thanks for taking care of it!

FEDORA-2023-a36f5521d0 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a36f5521d0

FEDORA-2023-a36f5521d0 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a36f5521d0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a36f5521d0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2023-353bcc3d35 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-353bcc3d35`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-353bcc3d35

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2023-353bcc3d35 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2023-a36f5521d0 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.