Package Details: furtherance 25.3.0-1

Git Clone URL: https://aur.archlinux.org/furtherance.git (read-only, click to copy)
Package Base: furtherance
Description: Track your time without being tracked
Upstream URL: https://github.com/unobserved-io/Furtherance
Licenses: GPL-3.0-or-later
Submitter: bordam
Maintainer: mhdi
Last Packager: mhdi
Votes: 3
Popularity: 0.000000
First Submitted: 2022-04-01 21:07 (UTC)
Last Updated: 2025-03-10 06:22 (UTC)

Latest Comments

« First ‹ Previous 1 2

Aftermath commented on 2023-05-11 10:50 (UTC) (edited on 2023-05-11 10:52 (UTC) by Aftermath)

I'm receiving this error during compilation:

error[E0004]: non-exhaustive patterns: `chrono::format::Fixed::TimezoneOffsetDoubleColon` and `chrono::format::Fixed::TimezoneOffsetTripleColon` not covered
   --> /home/arash/.cache/yay/furtherance-git/src/build/cargo-home/registry/src/github.com-1ecc6299db9ec823/chrono_locale-0.1.1/src/lib.rs:253:21
    |
253 |                 let ret = match spec {
    |                                 ^^^^ patterns `chrono::format::Fixed::TimezoneOffsetDoubleColon` and `chrono::format::Fixed::TimezoneOffsetTripleColon` not covered
    |
note: `chrono::format::Fixed` defined here
   --> /home/arash/.cache/yay/furtherance-git/src/build/cargo-home/registry/src/github.com-1ecc6299db9ec823/chrono-0.4.24/src/format/mod.rs:221:5
    |
171 | pub enum Fixed {
    | --------------
...
221 |     TimezoneOffsetDoubleColon,
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^ not covered
...
227 |     TimezoneOffsetTripleColon,
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^ not covered
    = note: the matched value is of type `chrono::format::Fixed`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
    |
322 ~                     }
323 ~                     chrono::format::Fixed::TimezoneOffsetDoubleColon | chrono::format::Fixed::TimezoneOffsetTripleColon => todo!()
    |

For more information about this error, try `rustc --explain E0004`.
error: could not compile `chrono_locale` due to previous error
warning: build failed, waiting for other jobs to finish...
[14/15] Generating data/com.lakoliu.Furtherance.appdata.xml with a custom command
FAILED: src/furtherance 
/bin/sh /home/arash/.cache/yay/furtherance-git/src/furtherance/build-aux/cargo.sh /home/arash/.cache/yay/furtherance-git/src/build /home/arash/.cache/yay/furtherance-git/src/furtherance src/furtherance plain furtherance
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: furtherance-git-exit status 4

Both with furtherance and furtherance-git.

It can't build chrono_locale v0.1.1.

bordam commented on 2022-09-16 20:23 (UTC) (edited on 2022-09-16 20:23 (UTC) by bordam)

@DeedleFake Fixed

mmoya commented on 2022-09-16 09:59 (UTC)

The file will be generated as part as the build process, but it has to be present to avoid meson complaint.

It's enough with doing a touch Cargo.lock before calling arch-meson.

DeedleFake commented on 2022-09-16 03:04 (UTC)

Since the latest update, I get

Furtherance-1.5.4/meson.build:31:0: ERROR: File Cargo.lock does not exist.

when building.

bordam commented on 2022-08-18 18:20 (UTC)

@halcek done

halcek commented on 2022-07-25 11:39 (UTC)

@musiclover Can you please add ‘aarch64’ to the list of supported architectures? It works fine, and having it listed would be more convenient for installation on these platforms.

« First ‹ Previous 1 2