Package Details: lastpass 4.29.0.4-1

Git Clone URL: https://aur.archlinux.org/lastpass.git (read-only)
Package Base: lastpass
Description: The Universal LastPass installer for Firefox, Chrome, and Opera
Upstream URL: https://lastpass.com
Licenses: custom
Submitter: Det
Maintainer: eschwartz
Last Packager: eschwartz
Votes: 90
Popularity: 0.064372
First Submitted: 2013-06-02 17:50
Last Updated: 2019-06-12 04:17

Pinned Comments

eschwartz commented on 2019-04-03 17:17

No, it really isn't bad practice. It is bad practice to fail hard because you have a tightly interwoven dependency on makepkg internals (and the format that is absolutely, positively, guaranteedly documented, since I wrote the documentation). Given I have actually discussed this with one of the lead developers of yay, and my advice to not be vulnerable to breaking for any reason, was accepted, I consider myself justified in adding this.

I did not break yay. I discovered that yay was already broken. I also guaranteed that yay-git now supports upcoming versions of pacman.

Furthermore, the official policy of the AUR is that if an AUR helper does not work, you should use makepkg directly, and if makepkg itself does work, then the problem is automatically with the AUR helper and only the AUR helper.

I am not changing this, and it is not open for debate.

eschwartz commented on 2019-03-31 21:05

I am indeed running an unreleased version of pacman/makepkg, and I'm also the one who added b2sums to pacman in git master (and the pacman-git package I maintain). :p

It's not a problem for old versions of makepkg, as old versions will ignore b2sums and rely exclusively on sha256sums (all you need is at least one valid algorithm) -- you won't get the advantage of collision resistance with multiple algorithms including an SHA-3 contender, but SHA-2 is still pretty good even without using two algorithms for redundancy.

Added: Whether an AUR helper (that I do not test) can correctly handle this does not bother me, since makepkg (the gold standard which I use to test) handles it just fine.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

k2s commented on 2017-03-23 13:17

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

apastuszak commented on 2017-03-23 11:37

==> 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.

Anonymous comment on 2017-03-16 17:04

Much appreciated. Thank you!

Det commented on 2017-03-16 16:16

Updated.

Anonymous comment on 2017-03-16 16:11

Oops sorry. I'm having some issues with for `lpchrome_linux_4.1.41-1.crx' (md5sum mismatch). a73aa1a26b84f7a950a21dc4204eec96 in PKGBUILD, 649f10aeb2a75506e038e3ba0794cedd from the build path.

Det commented on 2017-03-16 15:58

> tianyug flagged lastpass out-of-date on 2017-03-16 for the following reason:
>
> v4.1.42 Release note: https://lastpass.com/upgrade.php?fromwebsite=1&releasenotes=1
> Tarball: https://lastpass.com/lplinux.php
> SHA-256: adb0e91f8d212d34dbb85db0b11738fe36db1a741ad5674d7070c4019a9fc75e

The versions are from here: https://lastpass.com/misc_download2.php

Det commented on 2017-02-15 19:07

Okayh... maybe it now works.

xiong.chiamiov commented on 2017-02-15 18:38

Aur Targets (1): lastpass

Proceed with installation? [Y/n]

Edit lastpass PKGBUILD with $EDITOR? [Y/n] n
Edit lastpass.install with $EDITOR? [Y/n] n
==> Making package: lastpass 4.1.23-2 (Wed Feb 15 10:37:05 PST 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found lplinux_4.1.23.tar.bz2
-> Found lpchrome_linux_4.1.40-1.crx
-> Found com.lastpass.nplastpass.json
-> Found lastpass_policy.json
-> Found lp4_4.1.35a.xpi
-> Found profiles.ini
==> Validating source files with md5sums...
lplinux_4.1.23.tar.bz2 ... Passed
lpchrome_linux_4.1.40-1.crx ... Passed
com.lastpass.nplastpass.json ... Passed
lastpass_policy.json ... Passed
lp4_4.1.35a.xpi ... Passed
profiles.ini ... Passed
==> Extracting sources...
-> Extracting lplinux_4.1.23.tar.bz2 with bsdtar
-> Extracting lpchrome_linux_4.1.40-1.crx with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
-> Installing for Google Chromes/Chromiums...
-> Installing for Mozilla Firefoxes...
install: cannot stat 'libnplastpass64.so': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
The build failed.

Det commented on 2017-02-15 17:35

Thanks, but that downloads some super-old 3.x. Should work now.

FadeMind commented on 2017-02-15 17:30

1. libnplastpass.so file was not found anywhere
2. New VALID firefox XPI file URL is: https://addons.mozilla.org/firefox/downloads/latest/lastpass-password-manager/addon-8542-latest.xpi

3.VALID

install -Dm644 lpchrome_$_chromver.crx "$pkgdir"/usr/share/lastpass/lpchrome_$_chromver.crx

NOT

install -Dm644 lpchrome_linux_$_chromver.crx "$pkgdir"/usr/share/lastpass/lpchrome_linux_$_chromver.crx