Arch Linux User Repository

Note to the lovers of AUR helpers : It looks like dependency resolution is a complex topic. Despite all package relations being properly declared in the Flutter packages, most AUR helpers seem to have trouble resolving the dependency chain between the package bases aur/flutter and aur/flutter-artifacts-google-bin. This is not my fault and I cannot do anything about it.

It looks like the initial installation works fine using aur/paru. Sadly aur/paru does not reach at building updates for the package.

On the other hand aur/yay properly reaches at both installing and updating this package, even though it builds the package 15 times (!!!) again and again.

If you use aur/paru, consider to simply execute pacman -R flutter && pacman -Rns flutter to clean up the previous installation of both package bases.

• https://github.com/Jguer/yay/issues/2413
• https://github.com/Morganamilo/paru/issues/1173

If you build both package bases using makepkg -sfC and later on install all build outputs using pacman -U, both the installation and the updates work like a charm.

I'm very sorry for the inconvenience, but sadly there's nothing I can do about this.

Huge update to the Flutter AUR package :

The previous implementation basically did a user installation of Flutter - downloaded the custom Dart SDK, CI artifacts from Chromium CI and had to be kept in user R/W access in order to have the Flutter Cache Manager working.

These times are now over - a clean and (almost) completely rewritten PKGBUILD which now uses clean dependency declarations, system Dart and Gradle and for sure no more user R/W installation directory.

This AUR entry is now a split package. Installing aur/flutter will still bundle the entire toolchain you knew from before. The other way round, if you don't need everything - e.g. when depending on Flutter as a build dependency in another package, you can choose to only depend on what you need.

The following split packages are available :

• flutter : meta package containing all other split packages

• flutter-common : the common files for Flutter needed for all use cases

• flutter-devel : your option of choice as a developer - ships the Flutter tool and all required templates to e.g. create a new project

• flutter-tool : The pure Flutter tool. Use as depends to build your package.

• flutter-target-linux : The Flutter Linux build files. Use as depends to build your package.

• flutter-target-web : The Flutter web build files. Use as depends to build web apps (e.g. fluffychat-web does this).

• flutter-target-android : The Flutter Android build files. Use if you want to develop Android apps.

• flutter-gradle : The Flutter Gradle wrapper. Populated from system Gradle.

• flutter-intellij-patch : a tiny patch to make the IntelliJ Flutter plugin work with the new package.

• flutter-material-fonts-google-bin : Mandatory fonts package, planned to have a system-installed drop-in replacement soon.

• flutter-engine-common-google-bin : Shared part of the Flutter engine - downloaded from Google servers.

• flutter-sky-engine-google-bin : Flutter sky engine - downloaded from Google servers.

• flutter-engine-linux-google-bin : Linux part of the Flutter engine - downloaded from Google servers.

• flutter-engine-web-google-bin : Web part of the Flutter engine - downloaded from Google servers.

• flutter-engine-android-google-bin : Android part of the Flutter engine - downloaded from Google servers.

• flutter-gradle-google-bin : The Flutter Gradle wrapper - downloaded from Google servers.

Stay tuned for non google-bin versions of the engine, they are in coming !

Since almost everything is written from scratch and heavy patches are applied to use the system packages as dependencies, there might still be bugs occurring. Please report them otherwise I can't fix them !

@PolarianDev dart included in any flutter archive. Their versions are tightly coupled. The system version of dart can theoretically be updated earlier than flutter, this can break flutter or lead to unexpected errors. Don't use system dart if installing flutter

I have realised that during the building of flutter in a clean chroot, you are downloading the dart sdk directly without adding it as a dependency of the package, dart is within the community repository:

https://archlinux.org/packages/community/x86_64/dart/

Is there a reason for this?

This package is not stable. Every time I attempt to update this package, it complains in the same way that it does for @xeruf.

What gives?

error: failed to commit transaction (conflicting files)
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.10-candidate.1 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.10-candidate.1 exists in filesystem
flutter: /opt/flutter/packages/flutter_tools/lib/src/migrations/cocoapods_script_symlink.dart exists in filesystem
Errors occurred, no packages were upgraded.

The sha256sum for flutter-3.3.10 is out of date.

The current sha256 for the flutter sdk is 4ab54d3f93ba6e0308b3176ab81843c9d3d44b126e27204aa96a339601d45aff

Yeah I can just blindly follow the advice, but can't this be avoided?

Also, upgrading fails due to the .git dir, does that really need to be copied into /opt at all?

error: failed to commit transaction (conflicting files)
flutter: /opt/flutter/.git/logs/refs/remotes/origin/115574-android-selection-haptics-feedback-should-respect
-android-settings exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/beta exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/dependabot/docker/dev/ci/docker_linux/ubuntu-6fec506 exi
sts in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/dependabot/github_actions/actions/checkout-3.2.0 exists 
in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/dependabot/github_actions/github/codeql-action-2.1.37 ex
ists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/fix-isCanvasKit-bool exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.2-candidate.5 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.10 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.11 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.12 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.13 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.7 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.8 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.6-candidate.9 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.0 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.1 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.2 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.3 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.4 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.5 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.6 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.7 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.8 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/flutter-3.7-candidate.9 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/fuchsia_r51 exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/revert-115009-fix_linux_remapped_capslock_throws exists 
in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/revert-116798-run_log_spew exists in filesystem
flutter: /opt/flutter/.git/logs/refs/remotes/origin/stable exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/115574-android-selection-haptics-feedback-should-respect-andr
oid-settings exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/beta exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/dependabot/docker/dev/ci/docker_linux/ubuntu-6fec506 exists i
n filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/dependabot/github_actions/actions/checkout-3.2.0 exists in fi
lesystem
flutter: /opt/flutter/.git/refs/remotes/origin/dependabot/github_actions/github/codeql-action-2.1.37 exists 
in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/fix-isCanvasKit-bool exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.2-candidate.5 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.10 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.11 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.12 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.13 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.7 exists in filesystem
flutter: /opt/flutter/.git/refs/remotes/origin/flutter-3.6-candidate.8 exists in filesystem
[...]
Errors occurred, no packages were upgraded.
removing untracked AUR files from cache...

@xeruf execute git config --global --add safe.directory /opt/flutter

OR add this lines to .gitconfig file

[safe]
    directory = /opt/flutter

After adding my user to flutterusers, I still get this:

❯ flutter doctor
fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

    git config --global --add safe.directory /opt/flutter
Doctor summary (to see all details, run flutter doctor -v):
Failed to find the latest git commit date: VersionCheckError: Command exited with code 128: git -c
log.showSignature=false log HEAD -n 1 --pretty=format:%ad --date=iso
Standard out: 
Standard error: fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

    git config --global --add safe.directory /opt/flutter

Returning 1970-01-01 01:00:00.000 instead.
[!] Flutter (Channel unknown, 0.0.0-unknown, on Arch Linux 6.0.8-arch1-1, locale en_IE.UTF-8)
    ! Flutter version 0.0.0-unknown on channel unknown at /opt/flutter
    ! Upstream repository unknown

After installation I get this confusing error:

❯ flutter run .
fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

    git config --global --add safe.directory /opt/flutter
rm: cannot remove '/opt/flutter/version': Permission denied