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 noticed that for me too. I just downloaded the source from the flutter webpage. You just extract it and set the path to the flutter/bin directory you put it in, and it just works. You don't even need dart. I guess I won't use this package until it's fixed.

@KI9N

after use dart-sdk-dev, now it report

Unexpected Kernel SDK Version 415669e260 (expected d946408c55).

@abend: yeah this has to be rethought, or someone needs to take over... having flutter as a broken package is definitely not sustainable.. :/

The dependency tree is completely broken with that split that was done. All AUR flutter dependencies use the same git url.

It's now working for me. As highlighted below in @KI9N's comment below the culprit is in extra/dart, substituting which with aur/dart-sdk-dev has resolved the dependency conflict for me.

It is rather simple to reproduce this using the following procedure on the CLI.

paru -Rs flutter dart

paru -S dart-sdk-dev

mkdir flutterbuild
cd !$

git clone https://aur.archlinux.org/flutter.git
cd flutter;makepkg -sfC;cd -

git clone https://aur.archlinux.org/flutter-artifacts-google-bin.git
cd flutter-artifacts-google-bin;makepkg -sfC;cd -

sudo pacman -U $(find . -name \*.zst | tr '\n' ' ')

FIX FOR THE ERROR:

Unexpected Kernel Format Version 117 (expected 114)

1. Install the aur/dart-sdk-dev package! (DO NOT USE extra/dart)

2. Rebuild and reinstall aur/flutter

@kral_kazisvet @duonqfs @sotoleni @CareAgain

I tried to install this package after the rewrite and it simply doesn't work. I get the same error as @alephaleph. No, I didn't use any AUR helper. I downloaded the repo manually and installed this with makepkg -si along with https://aur.archlinux.org/packages/flutter-engine-common-google-bin installed the same way.

To "fix" this, I simply installed the package from the latest commit before the rewrite, and lo and behold, it works just fine. Link: https://aur.archlinux.org/cgit/aur.git/commit/?h=flutter&id=2942f591ec73f3a8c132cd77a1331507dc581475

splitting the package turned out to be, at least for me, the worst mistake you could make, a source of perennial problems every time Android studio updates its internal plugins or when a new version of flutter appears on the repositories.

Leaving this aside, I'll explain how I solved the dependency problems between the various packages (I use Manjaro):

1. remove flutter and everything related
2. check that you have the aur/dart-dev-sdk package and not extra/dart: with the latter flutter does not compile because it says that the Dart SDK is missing
3. install trizen as pamac frontend

Then, install the packages in this order:

1. trizen -s flutter-devel flutter-tool flutter-common flutter-intellij-patch
2. trizen -s flutter-material-fonts-google-bin flutter-sky-engine-google-bin flutter-engine-common-google-bin
3. trizen -s flutter-engine-android-google-bin flutter-engine-linux-google-bin flutter-engine-web-google-bin
4. trizen -s flutter-gradle-google-bin flutter-target-android flutter-target-linux flutter-target-web

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

Unexpected Kernel Format Version 117 (expected 114)