rubygem-net-ssh failed to build from source in Fedora rawhide/f41 https://koji.fedoraproject.org/koji/taskinfo?taskID=120747741 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild Please fix rubygem-net-ssh at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, rubygem-net-ssh will be orphaned. Before branching of Fedora 42, rubygem-net-ssh will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 2042669 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 2042670 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 2042671 [details] state.log
FEDORA-2024-ea6aa546d1 (rubygem-net-ssh-7.3.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ea6aa546d1
FEDORA-2024-ea6aa546d1 (rubygem-net-ssh-7.3.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
The update which closed this did not contain a build for f41, which means that f41 systems still use the old f40 build. Is this intentional? Are there plans to issue an update with a fixed build for f41 or is this not necessary or maybe even problematic in any way? It feels a bit odd to have packages which are not build against f41 on my f41 system but I don on know enough about that (in general and about ruby and this package in particular) to say that is really a serious issue. Looking forward to any feedback and to learn about this. Thanks in advance and thanks for maintaining this package :)
Thanks for the heads up. I have built the updated rubygem-net-ssh for f41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3d10084800
Thanks for the quick update! I'd like to help with testing once it is in the testing repository. However, I don't know where this lib is actually used, just that it is required by vagrant. Do you happen to know which purpose it specifically has? Otherwise I'll just try some basic vagrant operations and give feedback based on that I guess...
(In reply to David Auer from comment #6) > The update which closed this did not contain a build for f41 Well, this was reported as part of F41 mass rebuild, while it is technically still related to Rawhide (see the `Version` field). The subject is a bit unfortunate IMHO. There should have been created F41 clone along the line, but there are some gaps in our processes ... >, which means > that f41 systems still use the old f40 build. Is this intentional? Yes. I don't think the build failure should be issue for our users. > Are there > plans to issue an update with a fixed build for f41 or is this not necessary > or maybe even problematic in any way? Not really from my side (see bellow), but obviously Troy has helped here. Thanks 😉 > It feels a bit odd to have packages which are not build against f41 on my > f41 system but I don on know enough about that (in general and about ruby > and this package in particular) to say that is really a serious issue. > Looking forward to any feedback and to learn about this. You are right, it looks odd, but the mass rebuild (which has triggered this particular ticket) is mainly driven by GCC updates, which are not particularly relevant for plain Ruby packages. Other reasons of mass rebuilds are of course to catch FTBFS packages and therefore ensure the distribution is in good shape. Generally, older packages are not necessarily problem, as long as they run. Of course they might not include some new (maybe security related) configurations, etc. (In reply to David Auer from comment #8) > Thanks for the quick update! I'd like to help with testing once it is in the > testing repository. For the time being, you have to use `dnf update --enablerepo=updates-testing`. But it might take some time to have the package in the repository. I believe the "compose" is done once a day. You can also try to experiment with `--advisories` DNF option. Last option is to grab the package directly from Koji (the build system): https://koji.fedoraproject.org/koji/packageinfo?packageID=10483 > However, I don't know where this lib is actually used, > just that it is required by vagrant. Do you happen to know which purpose it > specifically has? Otherwise I'll just try some basic vagrant operations and > give feedback based on that I guess... If the package is just indirect dependency, I believe that the feedback such as "I have tested this package indirectly as a dependency of Vagrant and everything seems to work" is valuable. Of course if you had some more specific use case directly for the package, that would be even better 😉 BTW thanks for reaching out! I appreciate you have risen the question 👍
Another user reported that the update actually fixed an issue for them, so I guess that was a good idea all along. Thanks for the quick action and good information here!