Post by DR via arch-general
It's breaking 32bit chrome and other stuffs.
It's already flagged as out-of-date, no need to go complaining on the
mailing list though.
While it may be disappointing that a package actually goes a whole 2
weeks without getting updated, these things do occasionally happen, even
in Arch Linux. :)
In the meantime, breaking 32-bit-applications-on-64-bit-Arch-Linux
binary artifacts that don't even seem to be packaged in the AUR is not
really sufficient justification IMHO to already be bugging the
maintainer about it, especially since AFAIK Google stopped providing new
32-bit Chrome versions a while ago, on account of they provide 64-bit
builds and feel that that is sufficient in this day and age...