From: "Alexey Zapparov" <alexey@zapparov.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: app-shells/vivid/
Date: Sat, 25 Dec 2021 21:41:11 +0000 (UTC) [thread overview]
Message-ID: <1640468465.b6a70a4c73534fe65b9466f1d91e316c3a0b5b71.alexey@gentoo> (raw)
commit: b6a70a4c73534fe65b9466f1d91e316c3a0b5b71
Author: Alexey Zapparov <alexey <AT> zapparov <DOT> com>
AuthorDate: Sat Dec 25 21:41:05 2021 +0000
Commit: Alexey Zapparov <alexey <AT> zapparov <DOT> com>
CommitDate: Sat Dec 25 21:41:05 2021 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=b6a70a4c
app-shells/vivid: add 0.7.0-r1
Fix LICENSE requirements.
Package-Manager: Portage-3.0.28, Repoman-3.0.3
Signed-off-by: Alexey Zapparov <alexey <AT> zapparov.com>
app-shells/vivid/{vivid-0.7.0.ebuild => vivid-0.7.0-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-shells/vivid/vivid-0.7.0.ebuild b/app-shells/vivid/vivid-0.7.0-r1.ebuild
similarity index 97%
rename from app-shells/vivid/vivid-0.7.0.ebuild
rename to app-shells/vivid/vivid-0.7.0-r1.ebuild
index ae583ae54..b6dd7de2b 100644
--- a/app-shells/vivid/vivid-0.7.0.ebuild
+++ b/app-shells/vivid/vivid-0.7.0-r1.ebuild
@@ -51,7 +51,7 @@ SRC_URI="
$(cargo_crate_uris)
"
-LICENSE="Apache-2.0 MIT LGPL-3+"
+LICENSE="LGPL-3+ MIT"
SLOT="0"
KEYWORDS="~amd64 ~x86"
next reply other threads:[~2021-12-25 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 21:41 Alexey Zapparov [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-18 3:15 [gentoo-commits] repo/proj/guru:dev commit in: app-shells/vivid/ Alexey Zapparov
2023-05-29 17:41 Alexey Zapparov
2023-05-29 17:41 Alexey Zapparov
2023-05-29 17:41 Alexey Zapparov
2022-01-30 20:04 Alexey Zapparov
2021-12-26 19:17 Alexey Zapparov
2021-12-25 21:22 Alexey Zapparov
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=1640468465.b6a70a4c73534fe65b9466f1d91e316c3a0b5b71.alexey@gentoo \
--to=alexey@zapparov.com \
--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