Arch Linux User Repository

Thanks for your quick response, and all of your hard work! Sometimes it's just not obvious how to prevent breaking changes, ey?

I will follow-up by reporting this issue via yay's reporting mechanism (github issues). I'll have to check the yay-git package to be sure it hasn't already been fixed, there, and maybe just a new release of yay is all that is needed.

Was this tested?

It was tested to work with makepkg, which is the gold standard...

I don't exactly test what every fad AUR helper does. Note that this sort of heuristic blacklisting of perfectly good packages means that yay would not work for packages that implement new features, immediately after makepkg itself received a new release. So I don't generally encourage this sort of error-checking anyway. It gives me flashbacks to pacaur and its "mismatched srcinfo" errors.

for the less informed who run into this issue, here's the quick and dirty on upgrading the aur package when yay breaks:

cd ~/.cache/yay/lastpass

makepkg -si

I'm also running into a breaking error with aur package upgrades:

yay error message:

:: Parsing SRCINFO (1/1): lastpass failed to parse lastpass: Line 30: Unknown key: "b2sums": b2sums = 493334b0cf11abe2add52a2935b1e3a4afdffd8b4b64d659913084257af058c51b2157fb1fdb4f78da9dee9f61750bcd0614661b092a66c6fd252eff35f348f8

This is a fatal error and aborts the entire yay run. I would suggest adding an as-yet unsupported line to the config is not backwards compatible for the various AUR tools. Maybe those tools should be given some time to either ignore invalid config lines, or add support for the new proposed config lines.

Was this tested? Can we remove the b2sums line until tools like yay have some time to get this added?

Well, yay doesn't like it... :: Parsing SRCINFO (1/3): lastpass failed to parse lastpass: Line 30: Unknown key: "b2sums": b2sums = 493334b0cf11abe2add52a2935b1e3a4afdffd8b4b64d659913084257af058c51b2157fb1fdb4f78da9dee9f61750bcd0614661b092a66c6fd252eff35f348f8

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.

Are you running an unreleased version of pacman/makepkg? I don't think b2sums is available yet.

For some reason, with this package installed, when activating the copy password functionality in Firefox (about page said binary component is installed), it would hang my browser for multiple minutes, and not copy the password. After removing the package (about page said binary component is removed, but copy password still shows), the functionality behaves as normal.

Looks like a new version was released on Dec. 13. Current version for Firefox is 4.21.0.4. Chrome is at 4.21.0.

Can this url set things back on track? https://addons.mozilla.org/firefox/downloads/file/1114760 It will install version 4.18.1.2 in firefox. Seems to be the last... I rather have a working PKGBUILD of an old version than nothing at all.