From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: app-admin/bitwarden-cli/
Date: Mon, 26 Feb 2024 16:30:35 +0000 (UTC) [thread overview]
Message-ID: <1708928284.53c5090f8e9afbef708796f16c8ddd08ebd70c59.ceamac@gentoo> (raw)
commit: 53c5090f8e9afbef708796f16c8ddd08ebd70c59
Author: Rahil Bhimjiani <me <AT> rahil <DOT> rocks>
AuthorDate: Mon Feb 26 06:18:04 2024 +0000
Commit: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Mon Feb 26 06:18:04 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=53c5090f
app-admin/bitwarden-cli: line break, fix metadata.xml
I always forget about running pkgcheck prior to pushing
Signed-off-by: Rahil Bhimjiani <me <AT> rahil.rocks>
app-admin/bitwarden-cli/bitwarden-cli-2024.2.0.ebuild | 3 ++-
app-admin/bitwarden-cli/metadata.xml | 2 --
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/app-admin/bitwarden-cli/bitwarden-cli-2024.2.0.ebuild b/app-admin/bitwarden-cli/bitwarden-cli-2024.2.0.ebuild
index 8258f2c576..7d6bf1c2a0 100644
--- a/app-admin/bitwarden-cli/bitwarden-cli-2024.2.0.ebuild
+++ b/app-admin/bitwarden-cli/bitwarden-cli-2024.2.0.ebuild
@@ -51,7 +51,8 @@ src_prepare() {
src_compile() {
pushd apps/cli
- PKG_CACHE_PATH="${WORKDIR}"/.pkg-cache npm --verbose --offline run dist:lin || die "Build failed! Try prebuilt from upstream ${CATEGORY}/${PN}-bin"
+ PKG_CACHE_PATH="${WORKDIR}"/.pkg-cache npm --verbose --offline run dist:lin \
+ || die "Build failed! Try prebuilt from upstream ${CATEGORY}/${PN}-bin"
./dist/linux/bw completion --shell zsh > bw.zsh
}
diff --git a/app-admin/bitwarden-cli/metadata.xml b/app-admin/bitwarden-cli/metadata.xml
index 120e3e571a..32c863c574 100644
--- a/app-admin/bitwarden-cli/metadata.xml
+++ b/app-admin/bitwarden-cli/metadata.xml
@@ -9,7 +9,5 @@
<remote-id type="github">bitwarden/clients</remote-id>
<bugs-to>https://github.com/bitwarden/clients/issues</bugs-to>
<doc>https://github.com/bitwarden/clients/tree/main/apps/cli</doc>
- <doc>https://contributing.bitwarden.com/getting-started/clients/cli/</doc>
- <doc>https://bitwarden.com/help/cli/</doc>
</upstream>
</pkgmetadata>
next reply other threads:[~2024-02-26 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 16:30 Viorel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 9:25 [gentoo-commits] repo/proj/guru:master commit in: app-admin/bitwarden-cli/ David Roman
2024-03-07 13:24 Viorel Munteanu
2024-02-27 6:31 Haelwenn Monnier
2024-02-27 6:31 Haelwenn Monnier
2024-02-26 16:30 Viorel Munteanu
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=1708928284.53c5090f8e9afbef708796f16c8ddd08ebd70c59.ceamac@gentoo \
--to=ceamac@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