From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/lastpass-binary-component/
Date: Thu, 17 Aug 2017 03:47:06 +0000 (UTC) [thread overview]
Message-ID: <1502941284.547063b703b811c2576c9fd54d16ea70a13b51b8.gokturk@gentoo> (raw)
commit: 547063b703b811c2576c9fd54d16ea70a13b51b8
Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 17 03:41:24 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Thu Aug 17 03:41:24 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=547063b7
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 | 2 +-
...y-component-4.1.4.ebuild => lastpass-binary-component-4.1.44.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-admin/lastpass-binary-component/Manifest b/app-admin/lastpass-binary-component/Manifest
index 753abbd8013..1cbcb8e814d 100644
--- a/app-admin/lastpass-binary-component/Manifest
+++ b/app-admin/lastpass-binary-component/Manifest
@@ -1 +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
diff --git a/app-admin/lastpass-binary-component/lastpass-binary-component-4.1.4.ebuild b/app-admin/lastpass-binary-component/lastpass-binary-component-4.1.44.ebuild
similarity index 100%
rename from app-admin/lastpass-binary-component/lastpass-binary-component-4.1.4.ebuild
rename to app-admin/lastpass-binary-component/lastpass-binary-component-4.1.44.ebuild
next reply other threads:[~2017-08-17 3:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 3:47 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-14 20:19 [gentoo-commits] repo/gentoo:master commit in: app-admin/lastpass-binary-component/ Göktürk Yüksek
2020-02-12 17:38 Göktürk Yüksek
2020-02-12 17:38 Göktürk Yüksek
2019-09-23 17:16 Michał Górny
2018-11-08 22:01 Göktürk Yüksek
2017-12-12 2:57 Göktürk Yüksek
2017-05-22 21:21 Göktürk Yüksek
2016-05-18 7:46 Göktürk Yüksek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1502941284.547063b703b811c2576c9fd54d16ea70a13b51b8.gokturk@gentoo \
--to=gokturk@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox