Package Details: vapoursynth-plugin-adaptivegrain-git 0.2.1.24.gcde9f66-1

Git Clone URL: https://aur.archlinux.org/vapoursynth-plugin-adaptivegrain-git.git (read-only, click to copy)
Package Base: vapoursynth-plugin-adaptivegrain-git
Description: Reimplementation of the adaptive grain mask as a Vapoursynth plugin
Upstream URL: https://git.kageru.moe/kageru/adaptivegrain
Licenses: MIT
Conflicts: vapoursynth-plugin-adaptivegrain
Provides: vapoursynth-plugin-adaptivegrain
Submitter: kageru
Maintainer: kageru
Last Packager: kageru
Votes: 2
Popularity: 0.175202
First Submitted: 2020-02-26 22:05
Last Updated: 2020-04-11 17:02

Latest Comments

deko commented on 2020-05-16 18:04

   Compiling adaptivegrain-rs v0.2.2 (/path/to/vapoursynth-plugin-adaptivegrain-git/src/adaptivegrain)
error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/lib.rs:1:1
  |
1 | #![feature(test)]
  | ^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
error: could not compile `adaptivegrain-rs`.

To learn more, run the command again with --verbose.

jholmer commented on 2020-04-04 15:01

Thanks, that did seem to fix it.

kageru commented on 2020-04-03 20:30

I think keeping --locked is preferable because it leads to reproducible builds. The issue here was that I didn’t properly fix the dependencies in Cargo.toml. Some were missing the minor version which caused them to be updated freely.

I changed that and pushed a new version. Can you try again?

jholmer commented on 2020-04-03 12:21

I am consistently receiving the following error on trying to update or clean install this package:

error: the lock file /home/soichiro/.cache/yay/vapoursynth-plugin-adaptivegrain-git/src/adaptivegrain/Cargo.lock needs to be updated but --locked was passed to prevent this

Guessing the --locked flag should be removed from the command in PKGBUILD?

sl1pkn07 commented on 2020-02-27 09:35

done for me

kageru commented on 2020-02-27 08:55

I changed the makedep from rustup to cargo. The default provider for cargo is rust which does not require additional toolchain configuration. If this still fails on your system, either perform the rust setup steps as described in the wiki, or manually replace rustup with rust, whichever works better for your use case.

kageru commented on 2020-02-27 07:07

It seems like the build fails if you’ve never built any rust projects on the system (thus not having a default toolchain set). I don’t see other PKGBUILDS configuring this for the user, so I’ll ask around how other maintainers address this.

In the meantime, the toolchain has to be set manually as described in https://wiki.archlinux.org/index.php/Rust#Rustup

Deshikenichi commented on 2020-02-27 00:52

error: no default toolchain configured

sl1pkn07 commented on 2020-02-27 00:02

Hi

error: no default toolchain configured