public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petrus Zhao" <petrus.zy.07@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: media-video/uxplay/
Date: Sat, 28 Jan 2023 10:12:33 +0000 (UTC)	[thread overview]
Message-ID: <1674900672.6b3f4ec4af8de842c553d9bfcafbe41f228b3040.PetrusZhao@gentoo> (raw)

commit:     6b3f4ec4af8de842c553d9bfcafbe41f228b3040
Author:     Petrus Zhao <petrus.zy.07 <AT> gmail <DOT> com>
AuthorDate: Sat Jan 28 10:11:12 2023 +0000
Commit:     Petrus Zhao <petrus.zy.07 <AT> gmail <DOT> com>
CommitDate: Sat Jan 28 10:11:12 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6b3f4ec4

media-video/uxplay: add 1.62, drop 1.61.1

Signed-off-by: Petrus Zhao <petrus.zy.07 <AT> gmail.com>

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

diff --git a/media-video/uxplay/Manifest b/media-video/uxplay/Manifest
index 40158b199..0f3bade3a 100644
--- a/media-video/uxplay/Manifest
+++ b/media-video/uxplay/Manifest
@@ -1 +1 @@
-DIST uxplay-1.61.1.tar.gz 389118 BLAKE2B ba6915c369c1bef725d67819314564e2eb7b5fbce7f58cec2f937e52aa01a3daa321a51a3b19dba391434106d1e45a70d3f2f21377fbc38661d28c8b51b70fc2 SHA512 52166a49b0ac23c3216a1aa437ff327e4b6ce857e72497aa4ea129d2bb3d3f6f10094234ff0a8210902b2c471faa2e8b6f86b61c1c74e4e40b22ff15207e377c
+DIST uxplay-1.62.tar.gz 394487 BLAKE2B a8ed01e9b5a92fbc6faf985f26f0ce8afaec6637abb50a7058ad153d6de77cf1f4f72b515ae7c4e348f93bb93dba56165cb7400f60f5b239e9f1c1a7dffabc8c SHA512 6e17b0bed0b368e9c1525d5d3f4c9b67ad6f3c64eb20071820314f74edc066078bb4cbd53393b12bd5cd5aee5f2dfb435c37b6865dba6e676bfc526620d2a9f5

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


             reply	other threads:[~2023-01-28 10:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 10:12 Petrus Zhao [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-08-09  9:34 Rui Huang
2023-05-13 12:09 Petrus Zhao
2023-02-26  7:28 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=1674900672.6b3f4ec4af8de842c553d9bfcafbe41f228b3040.PetrusZhao@gentoo \
    --to=petrus.zy.07@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