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.065575
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 ... Next › Last »

Nevax commented on 2016-07-17 07:57

Can you add vivaldi support please ?

Det commented on 2016-06-22 13:36

I didn't know you were switching either after install?

Erroneous commented on 2016-06-22 11:20

Would it make more sense to make a command to fix LastPass after install? Maybe a lastpass-extension-fix command which could be used any time after installation instead of hard coding a user and directory into the post install script.

sebstar commented on 2016-05-04 09:10

Is it possible to execute (sudo -u $_user) the changes to the user plugin directories as the user themself? My $HOME is mounted on a nfsv4 network share where (thankfully) the root user doesn't have access to, so the user home directory part of the .install script fails.

Det commented on 2016-04-15 15:56

That's with the binary plugin. You can extract the .crx to see the one provided without it.

FadeMind commented on 2016-04-15 15:55

LastPass Chrome Extension version is 4.1.6, not 4.1.5.

http://pix.toile-libre.org/upload/original/1460735695.png

Det commented on 2016-04-11 15:13

Not, if multiple?

Erroneous commented on 2016-04-11 13:49

I don't know if there is a standard way of doing this, but you could use the following to figure out the current user name and home directory in lastpass.install if only one user is logged in:

_user=$(users | sed -e 's/ /\n/g' | grep -v root | sort | uniq) # User
_home=$(eval echo ~$_user) # $HOME

Det commented on 2016-03-28 17:23

"Your package lastpass [1] has been flagged out-of-date by Emmaseven [2]:

md5 not correct"

Which one? All pass here.

Det commented on 2016-03-26 10:22

Done-desu!