The commit
c11fc76d645ed4cebe6334273e4536f9f80ea1ca incorrectly bumps
to the version 4.1.4 as opposed to 4.1.44. Because the upstream does
not version their tarballs, it did not show up during
testing. Moreover, the tarballs for the versions 4.1.2 and 4.1.44 are
identical, so this mistake did not actually introduce any
breakage. Because 4.1.44 > 4.1.4, there will be no downgrades or any
unintended side effects either.
Package-Manager: Portage-2.3.6, Repoman-2.3.1
-DIST lastpass-binary-component-4.1.4.tar.bz2 1623477 SHA256 adb0e91f8d212d34dbb85db0b11738fe36db1a741ad5674d7070c4019a9fc75e SHA512 6fd518fa19f7206a1007376460c61e5a5c8d868126a767b3978309f0cc7ccd069e743cb12364e6841d8d3cb29452d058122b95f42bcfd2bd4deb4b8c77dc5f75 WHIRLPOOL c50bde0ee3f82abe56803beb2bda09786f7806b5e480eb8401fe0302ee984465f2682af66243095f3ea83744d59d6d3548806c423b69a8603abed9fc3ba3d00c
+DIST lastpass-binary-component-4.1.44.tar.bz2 1623477 SHA256 adb0e91f8d212d34dbb85db0b11738fe36db1a741ad5674d7070c4019a9fc75e SHA512 6fd518fa19f7206a1007376460c61e5a5c8d868126a767b3978309f0cc7ccd069e743cb12364e6841d8d3cb29452d058122b95f42bcfd2bd4deb4b8c77dc5f75 WHIRLPOOL c50bde0ee3f82abe56803beb2bda09786f7806b5e480eb8401fe0302ee984465f2682af66243095f3ea83744d59d6d3548806c423b69a8603abed9fc3ba3d00c