Arch Linux User Repository

This package is deprecated in favor of aur/flutter which now contains all required artifacts on its own. This PKGBUILD will be kept as is in order to ensure seamless builds of old Flutter version in future.

Latest update looks like it might have conflicting dependencies.

Most packages require dart > 3.5 but it looks like flutter-engine-common-google-bin requires dart < 3.5

@Yorokobii Maybe you could consider installing aur/flutter-intellij-patch ? That one simply installs that symlink.

Some tools use the path to the flutter bin to call the dart bin, I suppose to use compatible versions. Do you think it would be okay for your package to make a link to the dart binary as /usr/lib/flutter/bin/dart ? This package is so complex I'm not entirely sure it's good practice but I'm just throwing that here.

Please note that if you want to use extra/dart to build package which requires flutter SDK, you need to set FLUTTER_ROOT=/usr/lib/flutter or dart cannot find proper flutter SDK. You can try to build spotube without FLUTTER_ROOT set to prove this.

Is there something wrong with the dependencies?

@raevn They're too complicated. Read the pinned comments.

Also look through previous comments. If there are recent reports of errors (not confusion about depends), you may want to postpone building until the next update.

Since this package was updated a week ago, it should still be working.

$ pikaur -S flutter Reading repository package databases... Reading local package database... Resolving AUR dependencies... :: error: Can't resolve dependencies for AUR package 'flutter-target-android': :: error: Dependencies missing for flutter-target-android :: warning: Following package cannot be found in AUR: flutter-engine-android
:: Try recovering flutter-target-android? [e] edit PKGBUILD [f] skip 'check()' function of PKGBUILD [s] skip this package [A] abort

Is there something wrong with the dependencies?

@WithTheBraid Hmm, neither paru, nor yay suggested to fulfill the dart dependency with aur/flutter-dart-google-bin, even when dart was too old and dart-sdk-dev was too new. Should it know that or does that only show up after building the package?

I have built the latest release against flutter-dart-google-bin and encountered ERROR: Target kernel_snapshot failed: Exception again.

@xuiqzy The extra/dart package was bumped to 3.4.0 yesterday, see https://gitlab.archlinux.org/archlinux/packaging/packages/dart/-/commit/3f50d2346959602f63f9c2bd03ac0f454a5cf297 . Additionally, the aur/flutter-dart-google-bin package provides you with exactly the binary Dart version google ships for aur/flutter-artifacts-google-bin in cases your mirrored Dart version (or your distro's Dart version) did not sync with the bump yet.

Neither dart from repos nor dart-sdk-dev is fulfilling the dart dependency currently because the dart max version is exclusive, so 3.5 is not included. The dart min version is inclusive so works with >= 3.4 (but dart is on 3.3), is that intentional or should the dart max version constraint also be inclusive, i.e. <=?