Package Details: orca-slicer-unstable-bin 2.3.0.rc-1

Git Clone URL: https://aur.archlinux.org/orca-slicer-unstable-bin.git (read-only, click to copy)
Package Base: orca-slicer-unstable-bin
Description: G-code generator for 3D printers (all versions including alpha, beta, release candidates and stable versions)
Upstream URL: https://github.com/SoftFever/OrcaSlicer
Keywords: orca, orcaslicer, slicer
Licenses: AGPL3
Conflicts: orca-slicer
Provides: orca-slicer
Submitter: sem.z
Maintainer: sem.z
Last Packager: sem.z
Votes: 6
Popularity: 1.53
First Submitted: 2024-03-12 14:11 (UTC)
Last Updated: 2025-03-11 15:27 (UTC)

Pinned Comments

sem.z commented on 2024-04-12 06:20 (UTC)

I decided to not update to dev/nightly builds, because it is impossible to keep up, sometimes they got updated multiple times a day, so this package is always broken due to failed checksum. Please do not flag out of date if there is a new dev/nightly build, I will continue to update to alpha, beta, release candidates and stable versions as promised.

Latest Comments

1 2 Next › Last »

jersey2391 commented on 2025-03-04 18:18 (UTC) (edited on 2025-03-04 20:16 (UTC) by jersey2391)

Hi! Not sure if it's the right place to post this. I'm totally new to Arch. I wanted to use Orca Slicer. I was successfully using the AppImage v2.2.0 under PopOS (Ubuntu based). Now, I wanted to dip my toes in AUR with "stable" version of this package but it wasn't working (due to NVidia, Wayland and stuff...). I then tried the AppImage directly and it did not work either. However, when I tried the AppImage V2.3.0 (same as linked here, both Ubuntu and base AppImage) it worked (almost) flawlessly. I only needed to install libwebkit2gtk manually and everything was working fine. Wanting to use the AUR, I reached for this package here, but it doesn't work. So, no idea what I did wrong (or if something is "broken" under my specific config)

TL;DR This package doesn't work (NVidia + Wayland stuff), while OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.0-beta2.AppImage + libwebkit2gtk works just fine.

EDIT After some digging, turns out that there is a bit of code inside the ./AppRun script inside the AppImage that deal with this. However this PKGBUILD by-pass this script and run only the bin. Not sure of the way forwards though.

pr0m1x commented on 2024-11-06 03:34 (UTC)

@jacobtheeldest I've found that I don't need to uninstall the old copy, just clear the cache and install it.

rm -rf .cache/paru/clone/orca-slicer-unstable-bin/
paru -S orca-slicer-unstable-bin

jacobtheeldest commented on 2024-10-29 14:30 (UTC)

@sem.z I am not complaining and I appreciate you maintaining this package. My comment was to mention an issue I encountered and I updated it with a fix that worked for me in case others had the same issue.

The problem is that pkgver is compared alphanumerically which puts "2.2.0.rc-1" after "2.2.0-1". Since you asked, the epoch variable exists so a pkgbuild maintainer can address this exact issue: https://wiki.archlinux.org/title/PKGBUILD#epoch

Again, thank you for everything you do as the maintainer of this package.

sem.z commented on 2024-10-28 17:36 (UTC)

@jacobtheeldest, that's how devs version program, what can I do.

jacobtheeldest commented on 2024-10-28 15:39 (UTC) (edited on 2024-10-28 15:54 (UTC) by jacobtheeldest)

There is a mismatch with versioning order. yay reports orca-slicer-unstable-bin: local (2.2.0.rc-1) is newer than AUR (2.2.0-1)

I was able to install it after uninstalling my copy and clearing yay's cache:

yay -R orca-slicer-unstable-bin
rm -rf ~/.cache/yay/orca-slicer-unstable-bin
yay -S orca-slicer-unstable-bin

uberben commented on 2024-06-16 14:30 (UTC)

It looks like the URL needs updating again. Now that 2.1.0 is in beta, it is hosted at https://github.com/SoftFever/OrcaSlicer/releases/download/v2.1.0-beta/OrcaSlicer_Linux_V2.1.0-beta.AppImage

faith_healer commented on 2024-04-12 17:32 (UTC)

@sem.z I am :D Okay, nvm, I'll be updating manually :)

sem.z commented on 2024-04-12 17:14 (UTC)

@faith_healer, also if there is a new alpha/beta version, I would publish it, and than same or next day there would be new dev version, nobody even going to try alpha/beta.

sem.z commented on 2024-04-12 17:11 (UTC)

@faith_healer, it would be more correct to create new package of dev builds without checksum. Not going to do that right now, maybe in future. It was a mistake to publish dev builds here, because I stated in description "all versions including alpha, beta, release candidates and stable versions".

1 2 Next › Last »