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.069321
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 10 11 ... Next › Last »

FadeMind commented on 2016-03-26 07:13

nplastpass64
and
nplastpass
bin files are now in $srcdir/lplinux/

So install command should be

install -Dm755 lplinux/nplastpass$_64 "$pkgdir"/etc/opt/chrome/native-messaging-hosts/nplastpass$_64

apastuszak commented on 2016-03-13 23:48

Since I installed the latest version, Chrome will not remember my 2 factor authentication code for 30 days. I need to re-enter it every time I re-launch Chrome.

Det commented on 2016-03-09 15:32

✔ NOTE: If the md5sums don't match, don't post the makepkg output. Simply flag the package.

sedwen commented on 2016-02-11 21:48

md5sum incorrect

lpchrome_linux_4.0.6-1.crx ... FAILED

flagged

Det commented on 2016-02-11 20:07

It was a purposeful change.

FadeMind commented on 2016-02-11 19:40

FIXED PKGBUILD:

https://pastebin.com/raw/qiPusU9X

libnplastpass64.so is not available anymore for Firefox.

I fixed name for CRX chrome plugin too.

spapanik21 commented on 2016-01-27 11:24

There are two issues with the package. First it does not install the package in opera, and second it fails to get the signing in firefox (which will be a real issue when ff46 gets released)

s83 commented on 2016-01-25 22:26

Can you add support for opera and opera-developer? thank you in advance

Det commented on 2016-01-18 21:37

Oh yeah.

radiomike commented on 2016-01-18 21:34

PKGBUILD and lastpass.install currently broken due to change of name for firefox plugin.

Other references to lp_linux_$_ffver.xpi need updating to lp4_$_ffver.xpi?

One in _firefox_package() function and at least 2 in lastpass.install