app-admin/lastpass-binary-component: fix the versioning
authorGöktürk Yüksek <gokturk@gentoo.org>
Thu, 17 Aug 2017 03:41:24 +0000 (23:41 -0400)
committerGöktürk Yüksek <gokturk@gentoo.org>
Thu, 17 Aug 2017 03:41:24 +0000 (23:41 -0400)
commit547063b703b811c2576c9fd54d16ea70a13b51b8
treedb0eda42e3b603135a876f3e42aca2ca23216faa
parent6a8b37fbfcb617f63e53c21ff8af429aa4624020
app-admin/lastpass-binary-component: fix the versioning

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
app-admin/lastpass-binary-component/Manifest
app-admin/lastpass-binary-component/lastpass-binary-component-4.1.44.ebuild [moved from app-admin/lastpass-binary-component/lastpass-binary-component-4.1.4.ebuild with 100% similarity]