The git repo was renamed to main from master.
I cleared the AUR cache and it apparently forced a fresh git pull.
It built with the latest 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: | 104 |
Popularity: | 0.012167 |
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 .. 58 Next › Last »
The git repo was renamed to main from master.
I cleared the AUR cache and it apparently forced a fresh git pull.
It built with the latest git.
Attempting to install just now got the following:
Building freecad-git...
==> Making package: freecad-git 0.22.0.34594.ge9187412d9-1 (Fri 13 Oct 2023 03:11:44 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating FreeCAD git repo...
==> Validating source files with md5sums...
FreeCAD ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Creating working copy of FreeCAD git repo...
Cloning into 'FreeCAD'...
done.
warning: remote HEAD refers to nonexistent ref, unable to checkout
==> Starting prepare()...
==> Starting pkgver()...
grep: CMakeLists.txt: No such file or directory
fatal: ambiguous argument 'd29fd7d..HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
/var/tmp/pamac-build-mac/freecad-git/PKGBUILD: line 72: 24266 + : syntax error: operand expected (error token is "+ ")
==> ERROR: A failure occurred in pkgver().
Aborting...
@FabioLolix I removed the whole freecad-git
folder under .cache/yay/
and verified on install the the current PKGBUILD is 0.22.0.34522.gd8636dd058-1
. Same error. I wonder if this is related to locales. My system is a good mix. And the test shows that this is a comma/period issue.
@AUR_user I've just completed the build using devtools and was fine, clean your package building cache
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.
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.
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
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.