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 !

Hello again, I have tried to install the package in three ways: using the package manager (GUI), cloning and doing makepkg -sifC and using trizen (the last one is the one I use in most cases, it always works well for me). In all three cases the same error results that I have been reporting.

Please, group all flutter packages into one single group called flutter, so we can uninstall easily with one command like sudo pacman -Rns flutter...

Getting the same circular dependency error if I try to install flutter (yay -S flutter), but aur/flutter installs fine.

Trying to install with yay gives me a circular dependency error over and over again:

 -> aur dep warn:flutter-engine-common-google-bin flutter-sky-engine-google-bin circular dependencies not allowed
 -> aur dep warn:flutter-engine-common-google-bin flutter-material-fonts-google-bin circular dependencies not allowed

@juaji May I as how you built the package ? Did you use the -fC flags (force rebuild and clean source tree) when calling makepkg ?

Hi, unfortunately error I previuosly reported still occurs. Again I include the crash report.

BTW I also removed Gradle cache (by doing rm -rf ~/.gradle) as suggested.

Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.

## command

flutter --version

## exception

_TypeError: Null check operator used on a null value

#0      _gitCommitDate (package:flutter_tools/src/version.dart:387:4)
#1      _FlutterVersionGit.frameworkCommitDate (package:flutter_tools/src/version.dart:495:37)
#2      FlutterVersion.toString (package:flutter_tools/src/version.dart:225:99)
#3      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:347:30)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#5      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
<asynchronous suspension>
#6      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
<asynchronous suspension>
#7      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#8      main (package:flutter_tools/executable.dart:90:3)
<asynchronous suspension>

## flutter doctor

[☠] Flutter (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at
      https://github.com/flutter/flutter/issues.
    ✗ Null check operator used on a null value
    • #0      FlutterValidator._getFlutterUpstreamMessage (package:flutter_tools/src/doctor.dart:701:86)
      #1      FlutterValidator.validate (package:flutter_tools/src/doctor.dart:568:20)
      #2      Doctor.startValidatorTasks.<anonymous closure> (package:flutter_tools/src/doctor.dart:272:72)
      #3      asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:111:32)
      #4      _rootRun (dart:async/zone.dart:1399:13)
      #5      _CustomZone.run (dart:async/zone.dart:1301:19)
      #6      _runZoned (dart:async/zone.dart:1826:10)
      #7      runZonedGuarded (dart:async/zone.dart:1814:12)
      #8      runZoned (dart:async/zone.dart:1760:12)
      #9      asyncGuard (package:flutter_tools/src/base/async_guard.dart:109:3)
      #10     Doctor.startValidatorTasks (package:flutter_tools/src/doctor.dart:264:9)
      #11     DoctorText._validatorTasks (package:flutter_tools/src/doctor.dart:784:60)
      #12     DoctorText._validatorTasks (package:flutter_tools/src/doctor.dart)
      #13     DoctorText._runDiagnosis (package:flutter_tools/src/doctor.dart:788:53)
      #14     DoctorText.text (package:flutter_tools/src/doctor.dart:780:36)
      #15     DoctorText.text (package:flutter_tools/src/doctor.dart)
      #16     _createLocalCrashReport (package:flutter_tools/runner.dart:262:51)
      #17     _handleToolError (package:flutter_tools/runner.dart:224:31)
      <asynchronous suspension>
      #18     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
      <asynchronous suspension>
      #19     main (package:flutter_tools/executable.dart:90:3)
      <asynchronous suspension>


[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /home/luisd/Android/Sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /opt/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/google-chrome-stable

[✓] Linux toolchain - develop for Linux desktop
    • clang version 16.0.6
    • cmake version 3.28.3
    • ninja version 1.11.1
    • pkg-config version 2.1.0

[✓] Android Studio (version 2022.3)
    • Android Studio at /opt/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Manjaro Linux 6.0.19-4-MANJARO
    • Chrome (web)    • chrome • web-javascript • Google Chrome 123.0.6312.58

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Build currently fails with:

BUILD SUCCESSFUL in 18s
1 actionable task: 1 executed
~/flutter/src
/startdir/PKGBUILD: line 240: unzip: command not found
==> ERROR: A failure occurred in prepare().

I fixed it by adding unzip to makedepends.

You might need to empty your Gradle cache with the recent update. This can usually be done by rm -rf ~/.gradle. Beware not to delete anything you don't want to and ensure you didn't configure the Gradle cache to be populated at a different place.

Reason is that I had to patch Flutter not to write Gradle files to its installation folder but rather use a workaround to use the user Gradle cache dir.

@akitokatayose @juaji Could you check whether the error still occurs ? I forgot to bundle a particular version file (the engine version json) and the tool hence fell back onto git version. This should now be fixed with pkgrel=8.