public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/edid-decode/
Date: Sun, 12 Feb 2023 10:52:34 +0000 (UTC)	[thread overview]
Message-ID: <1676199135.f2ccd71847a56df447bc3ea17c413872d09ac39f.chewi@gentoo> (raw)

commit:     f2ccd71847a56df447bc3ea17c413872d09ac39f
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 12 10:52:15 2023 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Sun Feb 12 10:52:15 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2ccd718

sys-apps/edid-decode: Fix SRC_URI for 0_pre20230131

Sorry, hadn't noticed that ConiKost uses a different path in his devspace.

Closes: https://bugs.gentoo.org/894026
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 sys-apps/edid-decode/edid-decode-0_pre20230131.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/edid-decode/edid-decode-0_pre20230131.ebuild b/sys-apps/edid-decode/edid-decode-0_pre20230131.ebuild
index 985b57699fa3..76dd496bae09 100644
--- a/sys-apps/edid-decode/edid-decode-0_pre20230131.ebuild
+++ b/sys-apps/edid-decode/edid-decode-0_pre20230131.ebuild
@@ -10,7 +10,7 @@ MY_P="${PN}-${EGIT_COMMIT}"
 
 DESCRIPTION="Decode EDID data in a human-readable format"
 HOMEPAGE="https://git.linuxtv.org/edid-decode.git/"
-SRC_URI="https://dev.gentoo.org/~chewi/files/${P}.tar.gz"
+SRC_URI="https://dev.gentoo.org/~chewi/distfiles/${P}.tar.gz"
 S="${WORKDIR}/${MY_P}"
 
 KEYWORDS="amd64 ~arm64 x86"


             reply	other threads:[~2023-02-12 10:52 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 10:52 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-17 19:30 [gentoo-commits] repo/gentoo:master commit in: sys-apps/edid-decode/ Conrad Kostecki
2025-04-17 19:30 Conrad Kostecki
2025-03-13  0:29 Sam James
2025-03-12 23:02 Sam James
2024-08-31  2:42 Ionen Wolkens
2024-06-30 18:26 Michał Górny
2024-06-22 20:01 Conrad Kostecki
2024-06-22 20:01 Conrad Kostecki
2024-06-14 18:05 Sam James
2024-03-03 19:04 Michał Górny
2024-03-03 19:03 Michał Górny
2023-11-11 11:23 Yixun Lan
2023-02-21 20:03 Conrad Kostecki
2023-02-12  9:53 James Le Cuirot
2022-04-18 20:09 Conrad Kostecki
2022-04-18 20:09 Conrad Kostecki
2022-04-18 20:09 Conrad Kostecki
2022-03-19 18:38 Conrad Kostecki
2022-01-22  6:03 Arthur Zamarin
2021-11-16 22:18 Conrad Kostecki
2021-11-16 22:18 Conrad Kostecki
2021-11-16 22:18 Conrad Kostecki
2021-10-17 16:56 Conrad Kostecki
2021-10-17 14:38 Conrad Kostecki
2021-02-07 17:07 Conrad Kostecki
2021-02-07 17:07 Conrad Kostecki
2021-02-07 17:07 Conrad Kostecki
2021-01-06 12:22 Conrad Kostecki
2021-01-05 22:17 Conrad Kostecki
2020-09-18  9:20 Conrad Kostecki
2020-08-09 15:53 Conrad Kostecki
2020-08-09 15:53 Conrad Kostecki
2020-05-10 19:25 Conrad Kostecki
2020-05-10 19:25 Conrad Kostecki
2020-03-12 22:48 Conrad Kostecki
2020-03-12 22:48 Conrad Kostecki
2020-02-04 18:09 Conrad Kostecki
2020-01-21 10:42 Agostino Sarubbo
2020-01-20 12:52 Agostino Sarubbo
2019-12-21 23:37 Conrad Kostecki
2019-12-21 23:37 Conrad Kostecki
2019-12-07 15:47 Conrad Kostecki

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=1676199135.f2ccd71847a56df447bc3ea17c413872d09ac39f.chewi@gentoo \
    --to=chewi@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