Arch Linux User Repository

@GPereira: No, it isn't. 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

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: No, it isn't. 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

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.

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

@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.

@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

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]

@foxxy Thanks for mentioning it. They finally fixed it upstream, so I've now removed the patch.

Hi, Failed apply the site-packages-dir.patch when building this morning. Thanks for the package.

@jvybihal errr, it is? (uranium-git?) Not sure how you didn't have it installed.

@ad1217 thanks, I did not even had uranuim installed before. By installing it, it builds. Maybe you should add it as dependency ;)

edit: sorry, I see it is a dependency, no idea why yaourt did not install it then :/

@jvybihal your Uranium is out of date. I've just bumped a bunch of packages' versions up, updating them should fix it.