public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rui Huang" <vowstar@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: media-video/uxplay/
Date: Wed,  9 Aug 2023 09:34:30 +0000 (UTC)	[thread overview]
Message-ID: <1691573661.7733a58b0e3a58f0212d4f04b501ae1eb85738b1.vowstar@gentoo> (raw)

commit:     7733a58b0e3a58f0212d4f04b501ae1eb85738b1
Author:     Huang Rui <vowstar <AT> gmail <DOT> com>
AuthorDate: Wed Aug  9 09:34:21 2023 +0000
Commit:     Rui Huang <vowstar <AT> gmail <DOT> com>
CommitDate: Wed Aug  9 09:34:21 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=7733a58b

media-video/uxplay: add 1.65.3, drop 1.64

Signed-off-by: Huang Rui <vowstar <AT> gmail.com>

 media-video/uxplay/Manifest                                     | 2 +-
 media-video/uxplay/{uxplay-1.64.ebuild => uxplay-1.65.3.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-video/uxplay/Manifest b/media-video/uxplay/Manifest
index e3263381cc..3321709f40 100644
--- a/media-video/uxplay/Manifest
+++ b/media-video/uxplay/Manifest
@@ -1 +1 @@
-DIST uxplay-1.64.tar.gz 403977 BLAKE2B 0b7c4b858a6fce659c0b34a42c4d7fe268f67edaf6895857ea58b69d187379a2a36b2117f4aba83bdef9606c0692456f8065a6ed81773c090fc4a1c2ec6062be SHA512 531d193af182e3b202315f8078848ad44d5b3b458b125e5d183301de8d326b4a30221538fa3b00e049d51ec79bbedb5f45abf0319a04d87dc87193789e2482f1
+DIST uxplay-1.65.3.tar.gz 416832 BLAKE2B 95df0656e0b53a51f68f8e9404de4d7935f713e398c561c4ef44d2315ce41b47bf13787bcbd616a140a6d1a3b09edca6dc7d29a861fd69b1e6d6615183acdd1f SHA512 3e43c56144e1b224598d57b374a0adeacdb96813c84480fc7a9d3cfd2f61b4aef8291de94786491b2a46c5e09367621490954c47f03045247bf4785b35b8bfa2

diff --git a/media-video/uxplay/uxplay-1.64.ebuild b/media-video/uxplay/uxplay-1.65.3.ebuild
similarity index 100%
rename from media-video/uxplay/uxplay-1.64.ebuild
rename to media-video/uxplay/uxplay-1.65.3.ebuild


             reply	other threads:[~2023-08-09  9:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09  9:34 Rui Huang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-28  3:25 [gentoo-commits] repo/proj/guru:dev commit in: media-video/uxplay/ Rui Huang
2024-04-28  3:25 Rui Huang
2023-12-10 15:23 Petrus Zhao
2023-09-26 13:52 [gentoo-commits] repo/proj/guru:master " David Roman
2023-09-26 13:50 ` [gentoo-commits] repo/proj/guru:dev " David Roman
2023-05-13 12:09 Petrus Zhao
2023-02-26  7:28 Petrus Zhao
2023-01-28 10:12 Petrus Zhao
2023-01-01  7:55 Petrus Zhao
2022-12-30 10:39 Petrus Zhao
2022-12-28 14:35 Petrus Zhao
2022-12-28 14:26 Petrus Zhao
2022-12-28 14:26 Petrus Zhao
2022-11-04  8:13 Petrus Zhao
2022-08-21  7:50 Petrus Zhao
2022-07-24 14:28 Petrus Zhao
2022-07-07  2:07 Rui Huang
2022-06-26  5:48 Petrus Zhao
2022-06-25 15:44 Petrus Zhao
2022-05-14 13:46 Petrus Zhao
2022-05-02 13:57 Petrus Zhao
2022-04-24  4:20 Rui Huang
2022-04-04  7:21 Petrus Zhao
2022-03-17  4:13 Petrus Zhao
2022-02-26 11:40 Petrus Zhao
2021-12-30 14:32 Petrus Zhao
2021-12-10 13:18 Petrus Zhao
2021-11-20 12:35 Petrus Zhao
2021-11-16  5:57 Petrus Zhao
2021-11-09 12:29 Petrus Zhao
2021-11-07  4:11 Petrus Zhao
2021-10-09  2:19 Petrus Zhao

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=1691573661.7733a58b0e3a58f0212d4f04b501ae1eb85738b1.vowstar@gentoo \
    --to=vowstar@gmail.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