Opened a discussion thread on the AUR subforum regarding the test failures: https://bbs.archlinux.org/viewtopic.php?pid=2021620#p2021620
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: | 104 |
Popularity: | 0.012686 |
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-waylandAUR, glew-osmesa-gitAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- medAUR (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR, opencascade-rcAUR, opencascade-f3dAUR)
- 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-headlessAUR, qt6-base-gitAUR)
- 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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 58 Next › Last »
Kunda commented on 2022-02-11 17:00 (UTC)
Kunda commented on 2022-02-10 15:41 (UTC) (edited on 2022-02-10 15:42 (UTC) by Kunda)
Has anyone figured out why the tests fail? It looks like a permissions issue.
@adrianinsaval thought it may have been an issue with fakeroot? But we're not so sure. Here are the upstream discussions:
https://forum.freecadweb.org/viewtopic.php?f=4&t=66140
https://forum.freecadweb.org/viewtopic.php?f=4&t=66141
Separate issue but relevant: https://forum.freecadweb.org/viewtopic.php?f=4&t=66137
Kunda commented on 2022-02-08 18:06 (UTC)
@greyltc upstream py3.10 fix https://github.com/FreeCAD/FreeCAD/pull/5503
drmacro commented on 2022-02-04 18:20 (UTC)
Using "pip install PyQtWebEngine" and I still get the same pugixml not found.
So, is "HEAD needs new dep: PySide2.QtWebEngineWidgets" covered by the above or am I just not understanding what this is supposed to fix?
Kunda commented on 2022-02-04 16:14 (UTC)
@greyltc heads up, latest HEAD needs new dep: PySide2.QtWebEngineWidgets
Kunda commented on 2022-01-24 16:54 (UTC)
@greyltc pivy/python3.10 upstream issue: https://github.com/coin3d/pivy/issues/88
Kunda commented on 2022-01-24 15:10 (UTC) (edited on 2022-01-24 17:03 (UTC) by Kunda)
@C0rn3j at least one test theoretically should be fixed: https://github.com/FreeCAD/FreeCAD/commit/3dfdc6804f3931b27ebb526d3d87b200874d2a7c
could you and @Wolfenmond and anyone else retest the build (with check()
) enabled and report back if there are any other tests that are failing?
drmacro commented on 2022-01-15 16:12 (UTC)
Using the workaround mentioned by K4LCIFER this package does compile successfully. But, because of the Python 3.10 and pivy issues features of FreeCAD do not work.
C0rn3j commented on 2022-01-11 09:52 (UTC)
Got the same issue as @Wolfenmond and couldn't find it reported upstream, so I did - https://tracker.freecadweb.org/view.php?id=4825
K4LCIFER commented on 2022-01-06 02:11 (UTC) (edited on 2022-01-06 05:53 (UTC) by K4LCIFER)
Since there still seems to be a lot of issues with check()
, I would like to reiterate a workaround for anyone encountering issues, which is to install freecad with the --nocheck
flag in makepkg
to skip check()
. You can also run yay
with the --nocheck
flag by passing a makepkg
flag to yay
with yay
's --mflags
option, for example:
yay --mflags --nocheck -S freecad-git
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.