public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lars Wendler" <polynomial-c@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-strategy/warzone2100/
Date: Sun, 15 Aug 2021 12:45:08 +0000 (UTC)	[thread overview]
Message-ID: <1629031493.a72e19538f75f5d2900a45d2866d762f3e7c81d9.polynomial-c@gentoo> (raw)

commit:     a72e19538f75f5d2900a45d2866d762f3e7c81d9
Author:     Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 15 12:42:54 2021 +0000
Commit:     Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
CommitDate: Sun Aug 15 12:44:53 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a72e1953

games-strategy/warzone2100: Revbump to fix video install location

Closes: https://bugs.gentoo.org/808438
Signed-off-by: Lars Wendler <polynomial-c <AT> gentoo.org>

 .../{warzone2100-4.1.3-r1.ebuild => warzone2100-4.1.3-r2.ebuild}         | 1 +
 1 file changed, 1 insertion(+)

diff --git a/games-strategy/warzone2100/warzone2100-4.1.3-r1.ebuild b/games-strategy/warzone2100/warzone2100-4.1.3-r2.ebuild
similarity index 99%
rename from games-strategy/warzone2100/warzone2100-4.1.3-r1.ebuild
rename to games-strategy/warzone2100/warzone2100-4.1.3-r2.ebuild
index ab190710681..3e39b944a70 100644
--- a/games-strategy/warzone2100/warzone2100-4.1.3-r1.ebuild
+++ b/games-strategy/warzone2100/warzone2100-4.1.3-r2.ebuild
@@ -111,6 +111,7 @@ src_install() {
 		"${ED}"/usr/share/doc/${PF}/copyright || die
 
 	if use videos ; then
+		insinto /usr/share/${PN}
 		newins "${DISTDIR}"/${VIDEOS_P} sequences.wz
 	fi
 }


             reply	other threads:[~2021-08-16 20:48 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 12:45 Lars Wendler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-15  3:50 [gentoo-commits] repo/gentoo:master commit in: games-strategy/warzone2100/ Michał Górny
2024-03-01  7:55 Sam James
2024-03-01  7:55 Sam James
2023-11-30  3:07 Sam James
2023-11-09 14:26 Sam James
2023-11-09 10:24 Sam James
2023-05-23  2:52 Sam James
2023-04-25 21:25 Sam James
2023-04-18  4:29 Sam James
2023-03-27  2:15 Sam James
2023-03-22  5:43 Sam James
2023-01-28  9:29 Arthur Zamarin
2023-01-28  5:11 Sam James
2023-01-22  2:25 Sam James
2023-01-22  1:39 Sam James
2022-11-03  6:35 Sam James
2022-11-03  6:35 Sam James
2022-08-27  7:43 Sam James
2022-08-11  7:37 Ionen Wolkens
2022-03-02  3:04 Sam James
2021-12-27  0:35 Lars Wendler
2021-12-27  0:35 Lars Wendler
2021-11-24  1:43 Sam James
2021-10-27  7:22 Sam James
2021-09-12 20:20 Ionen Wolkens
2021-09-12 20:20 Ionen Wolkens
2021-08-17 21:29 Sam James
2021-08-17 16:45 Sam James
2021-08-17 16:43 Sam James
2021-08-17 16:42 Sam James
2021-08-14  3:53 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-14  3:48 Sam James
2021-08-09 22:21 Sam James
2021-08-06 12:58 Sam James
2021-06-23  2:24 Ionen Wolkens
2021-04-20 13:45 Sam James
2021-04-04 12:38 Sam James
2021-01-14 14:15 Sam James
2021-01-14 14:13 Sam James
2021-01-14 14:13 Sam James
2020-06-27 20:51 Aaron Bauman
2019-08-06 21:32 Lars Wendler
2018-05-06 19:03 Matt Turner
2017-09-21 14:33 Michael Palimaka
2017-09-21 14:33 Michael Palimaka
2017-05-05 13:44 Lars Wendler
2017-04-26  9:44 Lars Wendler
2017-04-26  9:44 Lars Wendler
2016-12-12  8:41 Lars Wendler
2016-09-29 12:46 Lars Wendler
2016-09-26 10:41 Lars Wendler
2016-09-26  7:20 Lars Wendler
2016-09-26  7:20 Lars Wendler
2016-08-05  0:23 Austin English
2016-06-07 22:27 Michael Sterrett
2016-06-06 14:31 Agostino Sarubbo
2016-05-03  0:44 Michael Sterrett
2016-04-02 13:44 Agostino Sarubbo
2016-02-23 15:24 Michael Sterrett
2016-01-25 22:05 Michael Sterrett
2016-01-25 22:05 Michael Sterrett
2015-08-25  8:13 Lars Wendler

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=1629031493.a72e19538f75f5d2900a45d2866d762f3e7c81d9.polynomial-c@gentoo \
    --to=polynomial-c@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