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 !

I got the same error when compiling of alephaleph (commented on 2024-04-22 08:14 (CEST))

Unexpected Kernel Format Version 117 (expected 114)

@ivanhercaz Don't choose flutter-bin to satisfy depends for this package. It is a monolithic package intended to be used on its own. Even if you did manage to build this package, it is currently not working. See multiple comments before yours.

Hi! First of all, thank you for the package and for the pinned comment about the problem with the problem when resolving the dependency chain (this one).

In my case, I use Manjaro and pamac. Removing the package and installing it again using pamac doesn't works:

1. pamac remove flutter
2. pamac build flutter

It returns again the same dependency problems. So I confirm everything was removed, then run yay -S flutter and in the installation wizard:

• I chose flutter-bin for all questions about the two packages that provides the dependency target and flutter-tools package.
• Then I chose "A" to clean all the package before compilation.
• Then I chose "N" to not show any diff, but I imagine this decision doesn't involves any change in the process (sorry, first time using yay!).
• Then, confirms to continue with the installation when notice me about the new package to install: lld-16.0.6-1. Same for unionfs-fuse-3.4.1.
• Then asks me for sudo password.
• Warns me about conflicts between flutter-bin and flutter-common.
• Warns me about a not resolving dependency, flutter-tool=3.19.6, for flutter-devel. Chose "n" to not omit.
• Again warns about flutter-tool, dependency of flutter-devel, and flutter-target-[linux|android|web], dependencies of flutter. Asks me to omit them, I chose "N".
• Finally, the installation breaks...

I leave the process written here in case it is helpful to debug this. If I achieve to install it again, I will update the comment.

Edit: okay, I think I misunderstood the fixed message, I just see this comment. I will try it.

Edit: at least to me, makepkg -sfC and pacman -U doesn't works. With makepkg it builds all the packages to be installed, but then using pacman I was installing one by one in the order they require, but there are missing packages. I will try it in the future, but by the moment I decided to use the installation method provided by the VSCode's extension.

Same issue when flutter run in version 3.19.6

Upon upgrading to flutter 3.19.6, builds are always failing. This is irrespective of the deployment method, in relation to WithTheBraid's pinned comment from 2024-03-28 00:44 (UTC).

$ flutter --version
Flutter 3.19.6 • channel  • https://github.com/flutter/flutter.git
Framework • revision archlinuxaur (unknown (arch linux aur package)) • 2038-01-19
03:14:08
Engine • revision c4cd48e18646
Tools • Dart 3.3.3 • DevTools 2.31.1

$ flutter doctor                   
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel , 3.19.6, on Arch Linux 6.8.7-arch1-1, locale en_AU.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2023.2)
[✓] IntelliJ IDEA Community Edition (version 2021.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

E.g, following is the execution log as captured for a new project on AndroidStudio.

Launching lib/main.dart on Linux in debug mode...
Building Linux application...
Unhandled exception:
Unexpected Kernel Format Version 117 (expected 114)
#0      BinaryBuilder.readComponent.<anonymous closure> (package:kernel/binary/ast_from_binary.dart:692)
#1      Timeline.timeSync (dart:developer/timeline.dart:173)
#2      BinaryBuilder.readComponent (package:kernel/binary/ast_from_binary.dart:679)
#3      _InitializationFromSdkSummary._prepareSummary (package:front_end/src/fasta/incremental_compiler.dart:2503)
#4      _InitializationFromUri.initialize (package:front_end/src/fasta/incremental_compiler.dart:2577)
<asynchronous suspension>
#5      IncrementalCompiler._ensurePlatformAndInitialize (package:front_end/src/fasta/incremental_compiler.dart:1383)
<asynchronous suspension>
#6      IncrementalCompiler.computeDelta.<anonymous closure> (package:front_end/src/fasta/incremental_compiler.dart:270)
<asynchronous suspension>
#7      CompilerContext.clear (package:front_end/src/fasta/compiler_context.dart:139)
<asynchronous suspension>
#8      IncrementalCompiler.compile (package:vm/incremental_compiler.dart:77)
<asynchronous suspension>
#9      FrontendCompiler.compile (package:frontend_server/frontend_server.dart:610)
<asynchronous suspension>
#10     listenAndCompile.<anonymous closure> (package:frontend_server/frontend_server.dart:1303)
<asynchronous suspension>
the Dart compiler exited unexpectedly.
the Dart compiler exited unexpectedly.
the Dart compiler exited unexpectedly.

Flutter itself built fine with 0 warnings, but Flutter applications currently fail to build with

ERROR: Target kernel_snapshot failed: Exception

Quick internet search points to incompatibility between Flutter SDK and Flutter Engine, but I am not sure as pkgvers seem to be identical.

Also same problem as @CareAgain reported with flutter run, most likely same root cause.

I have the same problem with the last update:

Unhandled exception: Unexpected Kernel Format Version 117 (expected 114)

flutter clean and flutter pub get --> not work
flutter pub cache repair --> not work

Do you have any ideas?

Trying to update to 3.19.6-1 and I get the following whenever I flutter run:

Unhandled exception:
Unexpected Kernel Format Version 117 (expected 114)
#0      BinaryBuilder.readComponent.<anonymous closure> (package:kernel/binary/ast_from_binary.dart:692)
#1      Timeline.timeSync (dart:developer/timeline.dart:173)
#2      BinaryBuilder.readComponent (package:kernel/binary/ast_from_binary.dart:679)
#3      _InitializationFromSdkSummary._prepareSummary (package:front_end/src/fasta/incremental_compiler.dart:2503)
#4      _InitializationFromUri.initialize (package:front_end/src/fasta/incremental_compiler.dart:2577)
...

kso: yes. We're all getting shenanigans with this package (I've already seen the "layer.error" error when trying to install it). It goes worse and worse with each new release patch. What worked for me was the steps mentionned by the maintainer:

In all cases, building the two pkgbase repos using makepkg -s[fC] and a manual installation of all output packages using pacman -U works.