Package Details: cura-git 4.8.beta.r99.g5ab4062ce-1

Git Clone URL: https://aur.archlinux.org/cura-git.git (read-only, click to copy)
Package Base: cura-git
Description: A full software solution for 3D printing aimed at RepRaps and the Ultimaker.
Upstream URL: https://github.com/Ultimaker/Cura
Keywords: 3dprint cura ultimaker
Licenses: GPL3
Conflicts: cura
Provides: cura
Submitter: ad1217
Maintainer: None
Last Packager: ad1217
Votes: 15
Popularity: 0.000225
First Submitted: 2014-11-24 06:53 (UTC)
Last Updated: 2020-11-09 02:19 (UTC)

Pinned Comments

ad1217 commented on 2018-02-14 18:10 (UTC) (edited on 2020-03-01 18:53 (UTC) by ad1217)

This is a VCS package, which means that when you build it, it will set the pkgver based on the latest version in the upstream repo. The only thing bumping version numbers here does is make people who already have it installed see that it needs updating (assuming they use an AUR helper). Bumping it here frequently is both pointless, as anyone can just rebuild the package(s) to get the latest, and annoying, since the git repo updates many times a day. If you want to get the latest, I'd suggest running something like 

<your-AUR-helper> -Sy {cura-fdm-materials,cura-binary-data,curaengine,libarcus,uranium,cura}-git
to rebuild this and all related packages.

Generally, I will only update these packages when something changes in the build process such that they don't work, dependencies change, or a major version is released.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

lewis2e commented on 2020-03-19 13:29 (UTC)

I am getting the issue described here, whereby the software is stuck at the welcome screen: https://community.ultimaker.com/topic/28928-cura-41-stuck-at-welcome-screen-buttons-are-missing/ Going to have to use the AppImage version instead.

remspoor commented on 2020-01-01 13:56 (UTC)

As i wanted to know if the preview function crashes cura by installing this -git version i stumbled upon this error when starting:

Traceback (most recent call last):
  File "/usr/bin/cura", line 15, in <module>
    import sentry_sdk
ModuleNotFoundError: No module named 'sentry_sdk'

This was solved by installing aur/python-sentry_sdk maybe consider adding the dependency.

ad1217 commented on 2019-12-05 04:07 (UTC)

@m1tch Added to the appropriate packages. Thanks for the heads up!

m1tch commented on 2019-12-04 15:58 (UTC)

To be able to run cura I needed to install python-cryptography python-certifi and python-requests. Please consider adding those to the dependencies.

bluehood commented on 2019-06-14 09:51 (UTC)

Cannot install package due to a breakage in libarcus-git -- also reported to the proper page.

ad1217 commented on 2018-02-14 18:10 (UTC) (edited on 2020-03-01 18:53 (UTC) by ad1217)

This is a VCS package, which means that when you build it, it will set the pkgver based on the latest version in the upstream repo. The only thing bumping version numbers here does is make people who already have it installed see that it needs updating (assuming they use an AUR helper). Bumping it here frequently is both pointless, as anyone can just rebuild the package(s) to get the latest, and annoying, since the git repo updates many times a day. If you want to get the latest, I'd suggest running something like 

<your-AUR-helper> -Sy {cura-fdm-materials,cura-binary-data,curaengine,libarcus,uranium,cura}-git
to rebuild this and all related packages.

Generally, I will only update these packages when something changes in the build process such that they don't work, dependencies change, or a major version is released.

GPereira commented on 2018-02-14 16:07 (UTC)

Please update the version number regularly, or orphan it. The idea of this packages is to always have the latest versions @ad1217

ad1217 commented on 2018-02-13 23:11 (UTC)

@GPereira: I've bumped the version numbers for this and related packages ({cura-fdm-materials,cura-binary-data,curaengine,libarcus,uranium,cura}-git), but they are git packages, and were still building/running properly. They don't need to be updated constantly.

ad1217 commented on 2017-10-19 07:46 (UTC) (edited on 2017-11-08 05:34 (UTC) by ad1217)

@bpietras Seems to be a known issue: https://github.com/Ultimaker/Cura/issues/2596. Workaround is to either downgrade QT or use the AppImage for now. Edit: Seems to be fixed

bpietras commented on 2017-10-13 08:30 (UTC)

A qt update seems to have broken this. After updating both cura-git & uranium, the package makes without issue. QMake version 3.1 Using Qt version 5.9.2 in /usr/lib cura [...] 2017-10-13 09:25:08,875 - DEBUG - UM.Qt.Bindings.Theme.load [231]: Loaded theme /usr/share/cura/resources/themes/cura-light 2017-10-13 09:25:19,249 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles [hung]

« First ‹ Previous 1 2 3 4 5 6 Next › Last »