@AUR_user I've just completed the build using devtools and was fine, clean your package building cache
Search Criteria
Package Details: freecad-git 0.22.0.36999.ged77603af9-1
Package Actions
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) |
Dependencies (39)
- boost-libs
- coin (coin-gitAUR)
- fmt (fmt-gitAUR)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- medAUR (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR)
- openmpi (openmpi-gitAUR)
- pyside6
- pyside6-tools
- python-matplotlib (python-matplotlib-gitAUR)
- python-packaging
- python-pivy
- python-ply
- python-yaml (python-yaml-gitAUR)
- qt6-5compat
- qt6-base (qt6-base-gitAUR, qt6-base-headlessAUR)
- qt6-svg
- qt6-tools
- Show 19 more dependencies...
Required by (4)
- freecad-a2plus-git (requires freecad)
- freecad-cadquery-git (requires freecad)
- freecad-fcgear-git (requires freecad)
- openmc-git (requires freecad)
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 58 Next › Last »
FabioLolix commented on 2023-10-01 09:55 (UTC)
AUR_user commented on 2023-10-01 09:21 (UTC) (edited on 2023-10-01 09:23 (UTC) by AUR_user)
For me it's failing with an error during the tests. Anyone else got this?
======================================================================
FAIL: testCalculiXSteel (TestMaterialsApp.MaterialTestCases.testCalculiXSteel)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/user/.cache/yay/freecad-git/src/FreeCAD/build/Mod/Material/TestMaterialsApp.py", line 166, in testCalculiXSteel
self.assertEqual(properties["Density"], "7900.00 kg/m^3")
AssertionError: '7900,00 kg/m^3' != '7900.00 kg/m^3'
- 7900,00 kg/m^3
? ^
+ 7900.00 kg/m^3
? ^
----------------------------------------------------------------------
Ran 1184 tests in 55.978s
FAILED (failures=1, skipped=2)
==> ERROR: A failure occurred in check().
Aborting...
-> error making: freecad-git-exit status 4
-> Failed to install the following packages. Manual intervention is required:
freecad-git - exit status 4
edit: Nevermind, just read the pinned comment.
drmacro commented on 2023-09-27 13:07 (UTC)
For some days now the update has failed to include the integrated Assembly workbench.
When FreeCAD is started it complains about a missing rc file.
This is correct since the .../Mod/Assembly directory does not exist.
It builds fine, just the particular directory is missing. (If the the directory is copied from another distro (in my case I have a build on Debian that produces the directory), the error goes away and the workbench is available.
adrianinsaval commented on 2023-03-12 15:09 (UTC)
btw I have automated builds for archlinux and have a custom repo: https://github.com/adrianinsaval/pacman-repo/releases/tag/archlinux-x86_64
obviously these are not official releases and you are essentially trusting me with root access to your system here so use at your own risk. The entire build process is open though
adrianinsaval commented on 2023-03-12 14:55 (UTC)
For manajro users if the build suddenly stops working it usually is because the pkgbuild has been adapted to a recent arch update that hasn't reached you yet, archlinux is obviously priority here so for those cases it's up to you to rollback the pkgbuild to the previous state and make it work. In this page there is functionality to check what recent changes have been made to the pkgbuild: https://aur.archlinux.org/cgit/aur.git/log/?h=freecad-git rollback the changes in your local copy as necessary up to the last time it was working on manjaro, eventually manjaro will catch up and you will need the latest pkgbuild again.
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.
drmacro commented on 2023-03-11 17:37 (UTC)
As of 12:41 EST it doesn not work in Manjaro:
Not working for me on Manjaro unfortunately:
could not satisfy dependencies: - unable to satisfy dependency 'verdict' required by freecad-git
pespin commented on 2023-03-09 23:18 (UTC) (edited on 2023-03-09 23:19 (UTC) by pespin)
I tried building today and it compiled fine but failed during test checking:
======================================================================
FAIL: test01 (PathTests.TestPathToolController.TestPathToolController)
Verify ToolController template roundtrip.
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/pespin/.cache/yay/freecad-git/src/FreeCAD/build/Mod/Path/PathTests/TestPathToolController.py", line 96, in test01
self.assertRoughly(tc0.Tool.Diameter, tc1.Tool.Diameter)
File "/home/pespin/.cache/yay/freecad-git/src/FreeCAD/build/Mod/Path/PathTests/PathTestUtils.py", line 37, in assertRoughly
self.assertTrue(math.fabs(f1 - f2) < error, "%f != %f" % (f1, f2))
AssertionError: False is not true : 1.750000 != 1.700000
----------------------------------------------------------------------
Ran 1105 tests in 49.550s
I had to build the package again but editing it and comment the check part. After that everything went fine and I can start freecad.
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.