Not working for me on Manjaro unfortunately:
could not satisfy dependencies:
- unable to satisfy dependency 'verdict' required by freecad-git
Git Clone URL: | https://aur.archlinux.org/freecad-git.git (read-only, click to copy) |
---|---|
Package Base: | freecad-git |
Description: | A general purpose 3D CAD modeler - git checkout |
Upstream URL: | https://www.freecad.org/ |
Licenses: | LGPL |
Conflicts: | freecad, freecad-appimage, freecad-appimage-git |
Provides: | freecad |
Submitter: | gborzi |
Maintainer: | greyltc (adrianinsaval) |
Last Packager: | adrianinsaval |
Votes: | 106 |
Popularity: | 0.82 |
First Submitted: | 2012-03-03 13:46 (UTC) |
Last Updated: | 2024-04-30 00:29 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 58 Next › Last »
Not working for me on Manjaro unfortunately:
could not satisfy dependencies:
- unable to satisfy dependency 'verdict' required by freecad-git
it should work now
the build works locally for me, but is also failing on my automated binary builds on a clean system, which suggests we are missing some dependency on the PKGBUILD but I have it installed on my local pc. This all seems to have started with the upgrade to vtk 9.2 would appreciate any help identifying the missing dependency
Current build as of today using "yay" failed:
================================================= Now run 'cmake --build /home/pespin/.cache/yay/freecad-git/src/FreeCAD/build' to build FreeCAD ================================================= -- Configuring done CMake Error at /usr/lib/cmake/vtk/VTK-targets.cmake:555 (set_target_properties): The link interface of target "VTK::nlohmannjson" contains: nlohmann_json::nlohmann_json but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Call Stack (most recent call first): /usr/lib/cmake/vtk/vtk-config.cmake:138 (include) cMake/FreeCAD_Helpers/SetupSalomeSMESH.cmake:29 (find_package) CMakeLists.txt:60 (SetupSalomeSMESH) CMake Error at /usr/lib/cmake/vtk/VTK-targets.cmake:1943 (set_target_properties): The link interface of target "VTK::verdict" contains: Verdict::verdict but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Call Stack (most recent call first): /usr/lib/cmake/vtk/vtk-config.cmake:138 (include) cMake/FreeCAD_Helpers/SetupSalomeSMESH.cmake:29 (find_package) CMakeLists.txt:60 (SetupSalomeSMESH) -- Generating done CMake Generate step failed. Build files cannot be regenerated correctly. ==> ERROR: A failure occurred in build(). Aborting...
Attempts build today fail:
-- Found Python: /usr/bin/python3.10 (found version "3.10.8") found components: Interpreter
-- Configuring done
CMake Error at src/Mod/Draft/CMakeLists.txt:317 (ADD_CUSTOM_TARGET):
Cannot find source file:
/var/tmp/pamac-build-mac/freecad-git/src/FreeCAD/src/Mod/Draft/DraftLayer.py
Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .h
.hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc
-- Generating done
CMake Generate step failed. Build files cannot be regenerated correctly.
==> ERROR: A failure occurred in build().
Aborting...
sorry, that's fixed now
Please take /usr/share/doc and NOT /usr/doc. Thanks Roman Volák
try now, the test where failing if you didn't have freecad already installed, it should work now
Having an issue with trying to install this package. It looks like it is going back to a file not found error for /usr/share/freecad/Mod/Arch/Presets/ifc_contexts_IFC4.json but I am not sure where this is intended to be coming from. Is someone able to assist me with what is going on?
Latest fails during the test phase, apparently in the FEM module tests.
Pinned Comments
adrianinsaval commented on 2023-03-12 14:50 (UTC)
If the check fails there is little I can do about it as it most likely needs to be fixed upstream, in such cases report those upstream (maybe wait a day or two as sometimes it's quickly solved upstream) or skip the check with
makepkg --nocheck
if you don't care about the functionality that is being reported as failing in the check.