public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/drone-cli/
Date: Thu, 06 Mar 2025 18:04:41 +0000 (UTC)	[thread overview]
Message-ID: <1741284247.48c2d6bea892280077ef93cca03bceaa4a811edc.arthurzam@gentoo> (raw)

commit:     48c2d6bea892280077ef93cca03bceaa4a811edc
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu Mar  6 18:04:07 2025 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Mar  6 18:04:07 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=48c2d6be

dev-util/drone-cli: fix LICENSE for dependent

Closes: https://bugs.gentoo.org/695240
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-util/drone-cli/drone-cli-1.7.0.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-util/drone-cli/drone-cli-1.7.0.ebuild b/dev-util/drone-cli/drone-cli-1.7.0.ebuild
index c71e573f9e5d..14c1de892f83 100644
--- a/dev-util/drone-cli/drone-cli-1.7.0.ebuild
+++ b/dev-util/drone-cli/drone-cli-1.7.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -11,6 +11,8 @@ SRC_URI="https://github.com/drone/drone-cli/archive/v${PV}.tar.gz -> ${P}.tar.gz
 SRC_URI+=" https://dev.gentoo.org/~williamh/dist/${P}-deps.tar.xz"
 
 LICENSE="Apache-2.0"
+# Dependent licenses
+LICENSE+="  Apache-2.0 BSD BSD-2 MIT MPL-2.0"
 SLOT="0"
 KEYWORDS="~amd64"
 


             reply	other threads:[~2025-03-06 18:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 18:04 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-21 18:10 [gentoo-commits] repo/gentoo:master commit in: dev-util/drone-cli/ William Hubbs
2023-08-09 17:47 William Hubbs
2023-08-09 17:47 William Hubbs
2022-10-02 17:46 William Hubbs
2022-03-23 15:06 William Hubbs
2020-07-14 21:49 William Hubbs
2020-02-09 13:14 David Seifert
2019-12-04  3:23 William Hubbs
2019-11-23 10:35 Manuel Rüger
2019-11-23 10:35 Manuel Rüger
2019-07-29  9:27 Manuel Rüger
2019-07-23 15:17 Manuel Rüger
2019-06-06  9:33 Manuel Rüger
2019-04-25 11:47 Manuel Rüger
2019-04-25 11:47 Manuel Rüger
2019-04-11 11:06 Manuel Rüger
2019-02-22 13:28 Manuel Rüger
2019-02-22 13:28 Manuel Rüger
2019-01-15 15:27 Manuel Rüger
2019-01-15 15:27 Manuel Rüger
2018-11-28 13:31 Manuel Rüger
2018-11-16 10:28 Manuel Rüger
2018-11-09  8:13 Manuel Rüger
2018-06-06 12:30 Manuel Rüger
2018-05-15 20:01 Manuel Rüger
2018-04-10  1:15 Manuel Rüger
2018-03-19 12:51 Manuel Rüger
2018-03-02 15:06 Manuel Rüger
2018-03-02 15:05 Manuel Rüger
2018-02-20 21:07 Manuel Rüger
2018-02-15  2:20 Manuel Rüger
2018-02-15  1:33 Manuel Rüger
2018-01-11 12:06 Manuel Rüger
2017-10-04  9:09 Michał Górny
2017-09-22 12:10 Manuel Rüger
2017-09-22 12:10 Manuel Rüger
2017-09-15 10:50 Manuel Rüger
2017-08-02  0:16 Manuel Rüger
2017-08-02  0:16 Manuel Rüger
2017-07-21 12:16 Manuel Rüger
2017-07-21 12:16 Manuel Rüger
2017-06-30 14:52 Manuel Rüger
2017-06-23 13:59 Manuel Rüger
2017-06-12 12:13 Manuel Rüger

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=1741284247.48c2d6bea892280077ef93cca03bceaa4a811edc.arthurzam@gentoo \
    --to=arthurzam@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