Package Details: ffsend 0.2.76-1

Git Clone URL: https://aur.archlinux.org/ffsend.git (read-only, click to copy)
Package Base: ffsend
Description: Easily and securely share files from the command line. A Send client.
Upstream URL: https://gitlab.com/timvisee/ffsend
Keywords: firefox send
Licenses: GPL3
Submitter: timvisee
Maintainer: timvisee
Last Packager: timvisee
Votes: 13
Popularity: 0.000000
First Submitted: 2019-03-27 17:09 (UTC)
Last Updated: 2022-06-20 08:52 (UTC)

Latest Comments

1 2 Next › Last »

m040601 commented on 2025-05-31 10:24 (UTC) (edited on 2025-05-31 10:36 (UTC) by m040601)

@timvisee, many thanks for keeping up this project and maintaining the PKGBUILD's for Arch.

This tool is definetly very much appreciated by many not so loud people.

Regarding the gitlab v. github (official) repos.

Could you please clarify this situation relevant for the PKGBUILDs maintenance ?? Especially the "ffsend-bin" one, 

https://aur.archlinux.org/packages/ffsend
https://aur.archlinux.org/packages/ffsend-git
https://aur.archlinux.org/packages/ffsend-bin

Maybe add 1 or 2 additional sentences to the READMEs to make it 100% crystal clear.

You state the "official" "canonical" repo/homepage is, gitlab,

 Upstream URL:   https://gitlab.com/timvisee/ffsend

There is indeded repo activity there

2025-02-04 f5b606f timvisee        Remove and invalidate snapcraft credentials              >
2025-02-04 60b3df0 timvisee        Use new SNAPCRAFT_STORE_CREDENTIALS variable             >
2025-02-04 0b32f4f timvisee        Bump version to 0.2.76                                   >

The latest tag in gitlab is "0.2.77". You seem to have a type in this commit from February,

Author:     timvisee <[email protected]>
AuthorDate: Tue Feb 4 21:00:28 2025 +0100
Commit:     timvisee <[email protected]>
CommitDate: Tue Feb 4 21:00:28 2025 +0100

    Bump version to 0.2.76
---

 [[package]]
 name = "ffsend"
-version = "0.2.76"
+version = "0.2.77"

But you have not released a "precompiled binary" on gitlab in the last 6 years, 

Showing 1 release on timvisee/ffsend.

Name  Tag     Created
      v0.0.7  about 6 years ago

Am I correct ??? I am talking about the precompiled binary 0.2.77 on gitlab. Not the "tag" 0.2.77.

In the meantime you have this other github "mirror" I suppose, In that github README it simply "lists" the gitlab URL , 

https://gitlab.com/timvisee/ffsend

But then you released a 'precompiled binary" on github, without releasing one in gitlab ??? Which is somehow confusing, 

releases

TITLE           TYPE    TAG NAME  PUBLISHED
ffsend v0.2.77  Latest  v0.2.77   about 3 months ago
ffsend v0.2.76          v0.2.76   about 2 years ago

Thanks in advance.

ThunderSquirrel commented on 2025-04-16 15:40 (UTC)

Adding options=(!lto) fixes the build.

pauper commented on 2023-09-10 22:41 (UTC) (edited on 2023-09-10 22:42 (UTC) by pauper)

Fails to build for me with a clean chroot: 

      /usr/bin/ld: /build/ffsend/src/ffsend-v0.2.76/target/release/deps/ffsend-585952f564175871: hidden symbol `GFp_ia32cap_P' isn't defined
      /usr/bin/ld: final link failed: bad value
      collect2: error: ld returned 1 exit status

      = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
      = note: use the `-l` flag to specify native libraries to link
      = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

    warning: `ffsend` (bin "ffsend") generated 2 warnings
    error: could not compile `ffsend` (bin "ffsend") due to previous error; 2 warnings emitted

nikost74 commented on 2023-05-27 11:46 (UTC)

I have successfully built this package on aarch64 architecture as well.

m040601 commented on 2022-06-20 11:01 (UTC) (edited on 2022-06-20 11:14 (UTC) by m040601)

@timvisee

Just a big thank you for all the work done with "send" and "ffsend".

Here in the AUR, maintaining the PKGBUILD's and on Gitlab developing the tools.

After hearing about it on Mozilla some years ago, I had forgotten about it.

I only got reminded again about "Send" and "FFsend" when using Libredirect, https://github.com/libredirect/libredirect. (Tip, "Libredirect is also extremely interesting and important for Firefox users)

"Ffsend" is very very usefull and underrated, especially for command line lovers. Pitty it's not better known. Here, and outside Archlinux. Hope this gets more votes. And can make it to Archlinux official packages one day.

"Send" also definetly needs more publicity and mention that can be used with Libredirect, https://reddit.rtrace.io/v50xzf. The decentralized and federation nature of it is a killer feature.

kauron commented on 2022-01-27 18:55 (UTC) (edited on 2022-01-28 08:30 (UTC) by kauron)

Edit: Disregard this comment. I got confused and mixed up the server and client (send vs ffsend).

Does anyone know which version is the latest one? Or, in other words, which repo is the canonical one for ffsend?

Gitlab has 0.2.74 as the latest (3 months ago) and Github has v3.4.16 (10 days ago). On top of that, the tags on both hosting services don't seem to match (version-wise), and it seems that only Gitlab's CI updates this package.

timvisee commented on 2021-08-31 13:35 (UTC)

@alerque Thanks for the comprehensive suggestion on what to change. I've fixed these issues in the ffsend repository, and the PKGBUILDs (for this, and my other Rust projects) will be updated with the next release.

alerque commented on 2021-08-31 09:12 (UTC)

This package should not be specifying the Rust version like it is. The [community] package for rust has a newer version than the minimum and Arch does not support partial upgrades, hence it can be assumed everybody will have at least what is in the official repo.

Actually please review the Arch Rust package guidelines because there are several relevant points this packaging is missing out on. Please just use makedepends=(cargo). The extra export lines will also fix any potential issues for rustup users that have the nightly toolchain set as default. The guidelines also specify how to prefetch dependencies to enable offline and reproducible builds, how to test, and more.

Another point, please don't add the opt-depends for bash-completion. The Shell package guidelines explain why, but this package provides completions, it is not useful to depend of a package which isn't required for the functionality.

mqs commented on 2019-12-28 23:33 (UTC)

if you're using rustup, you can try to patch in a rust-toolchain file[1] which contains your preferred toolchain(e.g. stable-1.40.0) and rustup will make sure to use it. I just don't know if you can make that a range... A workaround here would be to update that patch accordingly with each version to match the current stable branch or else to just pin it to 1.32.

[1] https://doc.rust-lang.org/nightly/edition-guide/rust-2018/rustup-for-managing-rust-versions.html

1 2 Next › Last »