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.

@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!

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?

After deleting the .pub-cache folder from my home it worked too. Thanks!

1 file changed, 17 insertions(+), 1 deletion(-)
PKGBUILD | 18 +++++++++++++++++-

modified   PKGBUILD
@@ -14,8 +14,24 @@ makedepends=("python")
 backup=("opt/${pkgname}/packages/${pkgname}_test/pubspec.yaml" "opt/${pkgname}/packages/${pkgname}/pubspec.yaml")
 options=("!emptydirs")
 install="${pkgname}.install"
+# Use bash Parameter Expansion so that the more than 2 billion people
+# (almost 30% of the population) that are currently under illegal
+# unilateral sanctions by the west (collectively makes up about 10% of
+# the population) can download and use flutter.
+
+# For those that live in China, Iran, Iraq, Syria, Russia, North
+# Korea, Cuba, Venezuela, Sudan, Yemen, Afghanistan, Belarus,
+# Palestine, Myanmar, Nicaragua, Libya, Zimbabwe (this list gets
+# bigger every year) you are not allowed to access
+# storage.googleapis.com and therefore will need to export these two
+# shell variables in your ~/.bashrc:
+
+# export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn export
+# export PUB_HOSTED_UTL=https://pub.flutter-io.cn
+
+# Thank you to China for not being fascist psychopaths.
 source=(
-  "${pkgname}-${pkgver}.tar.xz::https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/${pkgname}_linux_${pkgver/.hotfix/+hotfix}-stable.tar.xz"
+  "${pkgname}-${pkgver}.tar.xz::${FLUTTER_STORAGE_BASE_URL:-https://storage.googleapis.com}/flutter_infra_release/releases/stable/linux/${pkgname}_linux_${pkgver/.hotfix/+hotfix}-stable.tar.xz"
   "${pkgname}.sh"
   "${pkgname}.csh"
 )

I have added flutter to my unofficial repository, due to it being a dependency of a package I maintain saber.

Feel free to pull it from my repository, check out PolarRepo