Arch Linux User Repository

Whoops, I seem to have forgotten to add that when I switched the packaging logic to what I use in my other Firefox extensions. Fixed now.

'unzip' from the Extra Repository should be a dependency of the package, otherwise it will fail to build, due to unzip command usage.

I doubt it... the pkgver is not actually used in the download urls at all, so changing the pkgver and the _chromever accomplishes nothing other than giving the source files a unique local name. So your suggestion is a no-op. If the files were updated on the Lastpass server, then it would redownload the same *unversioned* URLs under an updated local name, and update the checksums if relevant... but that is a no-op at the moment as well. Additionally, the chrome browser extension is downloaded and updated by Chrome itself, since Chrome doesn't do locally-installed global extensions like Firefox does -- all that this package does is install a policy file telling Chrome to install lastpass on its own. The native messaging binary is installed, as per the official Lastpass universal installer, from their universal installer tarball (and the webstore doesn't contain libnplastpass.so at all). The opera plugin is installed, again as per the official installer script, from the unversioned CRX hosted on their website, which does have a libnplastpass.so and is also behind the Chrome webstore version -- I have no idea why. (But then again, the release notes say the latest Chrome webstore version is 4.1.55 and the latest Firefox version is 4.1.53 and apparently neither are true.) I have just double-checked and none of the (unversioned) source files have been updated, so this package should still be valid. If there was an update, then either the checksums would fail, or I would change the addons.mozilla.org _amo_file ID in order to download the new version of the Firefox extension. (I have a convenience script for the Firefox extension, see ./testupdate.sh) ... So given that nothing which you described should have fixed anything, I am not sure what the problem is or how you expect me to fix it. Maybe restarting Chrome caused it to fix itself?

Firstly thanks! Secondly, the package doesn't work against the current (4.1.60) version of the Chrome extension. It is just silently ignored. I made the following changes: pkgver=4.1.60 _chromever=${pkgver} And then ran `updpkgsums`. The package built cleanly and is now detected properly by the Chrome browser extension. (For those playing at home, this can be checked under Lastpass [icon] -> More Options -> About Lastpass.)

"massive cleanup of pretty much every possible bad practice a maintainer can do. :(" Awww. :-D

lpchrome_linux_4.1.51 fail the md5sums check. Unable to build the package.

correct md5sum (second in PKGBUILD): 0c8ee397e4550310309bb7e8f069a892 lpchrome_linux_4.1.42-2.crx

==> Validating source files with md5sums... lplinux_4.1.23.tar.bz2 ... Passed lpchrome_linux_4.1.42-2.crx ... FAILED lpchrome_linux_4.1.23.crx ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp4_4.1.35a.xpi ... Passed profiles.ini ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass.

Much appreciated. Thank you!

Updated.