Arch Linux User Repository

@ca_bi Excellent to hear, thanks for the quick feedback!

The dependencies should have been (and probably have been) downloaded in the prepare step, unless you manually removed the --offline flag (or didn't put it back after removing it), cargo should refuse to connect in the build step. :)

I think I'll try to bump the pkgrel number next time I do some changes like that, maybe this (the absence of it) was what prompted yay to try to do the install with an outdated cache - I only very sporadically work on AUR packaging so I'm never quite sure what the 100% correct procedures are, sorry for the bumpy ride there. :D

@simonrepp thx for the tip.

I did this:

$ yay -R faircamp
$ rm -rf .cache/yay/faircamp
$ yay -S faircamp
# cleanBuild: All

The install process worked now fine without problems. (I have the feeling that updating like this is just installing without the --offline flag. ;) )

For me it looks like that the cargo package lightningcss is somehow new in this version.

Deleting the cargo-cache ~/.cargo/ also force cargo to download all required crates. ;)

For me it works now ... maybe it helps the next one with a similar problem.

@ca_bi Thanks for the report!

Could you give the install process another shot by a) doing a fresh/clean install with yay (with a clean cache, however that is done) and/or b) installing the package from scratch without yay?

The reason I'm asking is that I've previously received reports about the install not working that ultimately were connected to the AUR install tool used rather than the package itself, and given I've received feedback that the current PKGBUILD installed fine for someone else, I first want to rule out that this is again an install tool problem.

As for removing --offline: The main reason for some of the recent changes to the PKGBUILD was to allow the package to install in an offline environment (this is in fact recommended/requested by the AUR packaging guidelines), therefore removing --offline should only be a last resort if we can't find any other solutions (but I think we will! :)).

For version 1.4.0-1 I get the error message while updating:

==> Starting build()...
error: no matching package named `lightningcss` found
location searched: registry `crates-io`
required by package `faircamp v1.4.0 (/home/carsten/.cache/yay/faircamp/src/faircamp)`
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag.
==> ERROR: A failure occurred in build().
    Aborting...

In the PKGBUILD file is the --offline mode enabled. When I remove the argument from the build command, I can update faircamp.

before: cargo build --features libvips --locked --offline --release
after: cargo build --features libvips --locked --release

@dreieck The report about the broken build process I got seems to have been related to a local system issue, therefore the revert has been un-reverted again. :) (Sorry for the back and forth)

@dreieck I reverted my changes from yesterday (asides the update to the new version) for now as someone (elsewhere) reported them to be breaking the build process. I'd like to unrevert and fix them going forward, but right now in the middle of the release I'd rather keep things working and come back when I have the time and energy for it. Thanks again for the support!

Thank you for the heads-up @dreieck o/

I just now consulted https://wiki.archlinux.org/title/Rust_package_guidelines to implement the improvements you pointed out, and also adopted a few other things in there (depending on 'cargo' rather than 'rust', setting recommended environment variables for build).

I currently don't have any arch-based system at my disposal to test these changes (I'm just maintaining the package for potential users since a while now) - if you find time to do a quick check after these updates, I'd much appreciate it. In any case, thanks again!

(ps. I also applied these same changes in faircamp-git)

This package downloads stuff in build(). This should not happen.

Please move the downloads that cannot be put into the source array into the prepare() function, so that build() can run in an offline environment after source preparation.

Regards and thanks for the package!

==> Starting build()...
    Updating crates.io index
    Updating git repository `https://codeberg.org/simonrepp/enolib-rs`
  Downloaded actix-codec v0.5.2
  Downloaded anyhow v1.0.94
  Downloaded alloc-stdlib v0.2.2
[...]
  Downloaded bytestring v1.4.0
warning: spurious network error (3 tries remaining): [28] Timeout was reached (download of `actix-http v3.10.0` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (3 tries remaining): [28] Timeout was reached (failed to download any data for `actix-files v0.6.6` within 30s)
  Downloaded pin-project-lite v0.2.15
  Downloaded actix-router v0.5.3
[...]
  Downloaded alac v0.5.0
  Downloaded 96 crates (15.2 MB) in 2m 08s (largest was `alac` at 5.4 MB)