Package Details: celeste 0.8.3-1

Git Clone URL: https://aur.archlinux.org/celeste.git (read-only, click to copy)
Package Base: celeste
Description: GUI file synchronization client that can sync with any cloud provider
Upstream URL: https://github.com/hwittenborn/celeste
Licenses: GPL-3.0-or-later
Submitter: yochananmarqos
Maintainer: yochananmarqos (rhysperry111)
Last Packager: yochananmarqos
Votes: 3
Popularity: 0.55
First Submitted: 2023-02-09 16:47 (UTC)
Last Updated: 2024-07-26 16:58 (UTC)

Latest Comments

1 2 Next › Last »

claymorwan commented on 2024-10-16 14:01 (UTC)

Kinda odd question but y'all know how to stop the Celeste game to overwrite the app's icon

yochananmarqos commented on 2024-07-16 00:40 (UTC)

@lukeemhigh: It builds fine in a clean chroot and is not related to packaging.

Your error message tells you what the problem is.

lukeemhigh commented on 2024-07-15 20:07 (UTC)

Im getting the following error when trying to upgrade the package:

==> Sources are ready.
celeste-0.8.3-1: parsing pkg list...
==> Making package: celeste 0.8.3-1 (lun 15 lug 2024, 22:03:46)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
cargo build --release
error: package `clap v4.5.7` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.73.0-nightly
Either upgrade to rustc 1.74 or newer, or use
cargo update -p clap@4.5.7 --precise ver
where `ver` is the latest version of `clap` supporting rustc 1.73.0-nightly
error: Recipe `build` failed on line 4 with exit code 101
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'celeste-0.8.3-1':

I've checked my rustc version and it should be 1.79.0:

$ rustc --version                                                                        
rustc 1.79.0 (129f3b996 2024-06-10)

That1Calculator commented on 2024-04-17 22:32 (UTC)

As the patch for #195 has had commit(s) added to it, the sha256sum has changed to de56b1fca8eb825a82560feccdacee9e440416d791ba5ca510d6520fc6ee905a, but for something like a patch that can change, I think that it should be SKIP in the PKGBUILD

yochananmarqos commented on 2024-03-03 16:07 (UTC)

@Fafou34130: Fixed, thanks for the heads up.

Fafou34130 commented on 2024-03-03 11:39 (UTC) (edited on 2024-03-03 11:40 (UTC) by Fafou34130)

Hi,

I am getting the following error

''' error[E0635]: unknown feature stdsimd --> /usr/src/debug/celeste/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.3/src/lib.rs:99:42 | 99 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))] | ^^^^^^^

Compiling log v0.4.19 Compiling quote v1.0.32 For more information about this error, try rustc --explain E0635. error: could not compile ahash (lib) due to 1 previous error warning: build failed, waiting for other jobs to finish... error: Recipe build failed on line 4 with exit code 101 ==> ERROR: A failure occurred in build(). Aborting... '''

dario commented on 2023-07-24 17:09 (UTC)

Yes, it works. Thank you.

yochananmarqos commented on 2023-07-24 15:39 (UTC)

@dario: It's fixed with 0.5.4.

dario commented on 2023-07-23 17:55 (UTC)

Thank you. Unfortunately I am not experienced with Rust build system. At the moment I am busy sorting out a bunch of unrelated stuff. From a quick search on the Internet it looks like a common issue. I will look into it when I have the time.

yochananmarqos commented on 2023-07-23 17:51 (UTC)

@dario: I've created an upstream issue: https://github.com/hwittenborn/celeste/issues/119

1 2 Next › Last »