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 !

@dvalter See comment https://aur.archlinux.org/packages/flutter#comment-933929

Checksum for 3.13.3 tarball does not match, for me it currently is 4fc057286135d4b7559db7d735a235753e273f284219b2e9d2f77aa455dd923e

It might be better to add the flutter repo in the sources of the package that needs it instead of depending on this package. You can select the exact version that you need, check localsend for an example. Of course since it's pretty big it should be cached by the user.

@cfujino As per usual, flutter releases a new version so now I can not build packages with the old version I have on my repository.

Now instead of error code 66 I get error code 4, do I even need to ask whether this is magically fixed if I update to the new version?

Maintaining a flutter package seems more pain than it is worth, and as flutter developers have ruled they are not going to help out, nobody seems to want to package flutter applications anymore, I wonder why?

So I assume you are asking to wait until flutter-3.13.4 gets released, because of the overwrite of 3.13.3?

Until then nobody can build flutter packages on Arch Linux it seems!

$ sha256sum flutter-*.tar.xz
4fc057286135d4b7559db7d735a235753e273f284219b2e9d2f77aa455dd923e  flutter-3.13.3.tar.xz
d9bbfbfb6fe3c72a29c1040235126edd0cd461e4e18556335fd1cf217c2e1473  flutter-3.13.4.tar.xz

$ tar -O -xf flutter-3.13.3.tar.xz flutter/version
3.13.4-0.0.pre.2

$ tar -O -xf flutter-3.13.4.tar.xz flutter/version
3.13.4

FWIW, it looks like v3.14.4 is available now.

But also, it does look like Google had two versions with the same v3.13.3 number: https://docs.flutter.dev/release/archive?tab=linux

...one on that page with ref == 'b0daa73', the other ref == '2524052'.

That incoherence from upstream is probably what broke the sha256sum in the PKGBUILD for v3.13.3.

Yeah, there was a breakdown in the flutter release infrastructure, that lead to the wrong commit being re-published as 3.13.3. It's unclear whether or not this will be fixed (as it would be risky to fix), so I would recommend unblocking this package by re-publishing for the 3.13.4 release.

FWIW, it looks like v3.14.4 is available now.

But also, it does look like Google had two versions with the same v3.13.3 number: https://docs.flutter.dev/release/archive?tab=linux

...one on that page with ref == 'b0daa73', the other ref == '2524052'.

That incoherence from upstream is probably what broke the sha256sum in the PKGBUILD for v3.13.3.

Yeah, there was a breakdown in the flutter release infrastructure, that lead to the wrong commit being re-published as 3.13.3. It's unclear whether or not this will be fixed (as it would be risky to fix), so I would recommend unblocking this package by re-publishing for the 3.13.4 release.

FWIW, it looks like v3.14.4 is available now.

But also, it does look like Google had two versions with the same v3.13.3 number: https://docs.flutter.dev/release/archive?tab=linux

...one on that page with ref == 'b0daa73', the other ref == '2524052'.

That incoherence from upstream is probably what broke the sha256sum in the PKGBUILD for v3.13.3.

FWIW, it looks like v3.14.4 is available now: https://docs.flutter.dev/release/archive?tab=linux

But yeah, I'm seeing a conflicting sha256sum for v3.13.3 as well:

$ shasum -a 256 flutter-3.13.3.tar.xz 
4fc057286135d4b7559db7d735a235753e273f284219b2e9d2f77aa455dd923e  flutter-3.13.3.tar.xz

Not equal to c53c8aeff17d13c4c0b47bff2c54a293e48286e03dd089f37d561737e41a8c2c from the PKGBUILD.

The sha256sum is wrong for v3.13.3. Seems like Google silently uploaded a new version?