Arch Linux User Repository

TL;DR

Upgrade using aur/yay might take very long and works inefficiently.

Upgrade using aur/paru requires the -d flag.

This is not my fault.

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 without additional flags. Please use paru -Syud (whereas the -d is the relevant flag) to upgrade 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.

• flutter-dart-google-bin : The Flutter original Dart SDK - downloaded from Google servers. This is helpful if the extra/dart package is not available in the right version on your distro or remix.

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 !

same

resolved with

$ mv /opt/flutter/packages/flutter_tools/.packages /opt/flutter/packages/flutter_tools/.packages.old

But I experience a LOT of

warning: directory permissions differ on $
filesystem: 775  package: 755

I experienced basic packages missing on my projects (incorrect URI), idk if it's related but I was able to correct that with flutter pub/packages get and a lot of restart/reloads

I get the followeing:

error: failed to commit transaction (conflicting files) flutter: /opt/flutter/packages/flutter_tools/.packages exists in filesystem Errors occurred, no packages were upgraded.

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.flutter/releases/

(solved) I cannot get to update flutter. having conflict error. Is it because I did >flutter upgrade ?

error: failed to commit transaction (conflicting files) flutter: /opt/flutter/.github/ISSUE_TEMPLATE/1_activation.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/2_bug.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/3_feature_request.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/4_performance_others.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/5_performance_speed.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/6_infrastructure.md exists in filesystem flutter: /opt/flutter/.github/ISSUE_TEMPLATE/config.yml exists in filesystem flutter: /opt/flutter/dev/benchmarks/complex_layout/ios/Flutter/Debug.xcconfig exists in filesystem flutter: /opt/flutter/dev/benchmarks/complex_layout/ios/Flutter/Release.xcconfig exists in filesystem flutter: /opt/flutter/dev/benchmarks/complex_layout/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings exists in filesystem ...

EDIT: OK just delete the directory and a clean install solves the issue.

yay -S flutter-group-pacman-hook
chgrp -R flutterusers /opt/flutter
chmod g+w /opt/flutter
sudo usermod -a -G flutterusers $USER

Is not enough to execute flutter as non-root, someone getted it to work here?

flutter 
        create $PROJECT
        doctor

Failed to open or create the artifact cache lockfile: "FileSystemException: Cannot open file, path = '/opt/flutter/bin/cache/lockfile' (OS Error: Permission denied, errno = 13)"
Please ensure you have permissions to create or open /opt/flutter/bin/cache/lockfile
Failed to open or create the lockfile

@solstice, you can use this pacman hook to achieve the same thing:

https://aur.archlinux.org/packages/flutter-group-pacman-hook/

You forgot to add a post_upgrade() in .install:

chgrp -R flutterusers /opt/flutter
chmod g+w /opt/flutter

Otherwise, an upgrade will cause problem

If you're getting issues with installing dependencies like the following:

-> Could not find all required packages:
    lib32-libva (Wanted by: flutter -> lib32-libglvnd-git -> lib32-mesa-aco-git)
    lib32-libxext (Wanted by: flutter -> lib32-libglvnd-git)
    lib32-libxext (Wanted by: flutter -> lib32-libglvnd-git -> lib32-mesa-aco-git -> lib32-libdrm-git -> lib32-cairo-git)
...
...
...

I've made a PR to the maintainer with a fix here:

https://github.com/frealgagu/archlinux.flutter/pull/2

@btimofeev: flutter needs to be run as root, or you can use a hook like mine (flutter-group-pacman-hook) to declare a group having the permissions to use it (it defaults to fultterusers group as it is the example in the PKGBUILD)