From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/PyQt6-sip/
Date: Fri, 12 Jul 2024 16:26:29 +0000 (UTC) [thread overview]
Message-ID: <1720801555.038a6e59b6b32c840b1c97ec10e4e65dd5143718.ionen@gentoo> (raw)
commit: 038a6e59b6b32c840b1c97ec10e4e65dd5143718
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 12 16:23:14 2024 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Fri Jul 12 16:25:55 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=038a6e59
dev-python/PyQt6-sip: update upstream metadata
Upstreams lists sip's repo as the "homepage" for PyQt6-sip
and as the place to report bugs (as I understand it), but
the source is not actually there that I can see. So only
adding to bugs-to rather than normal github metadata for now.
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-python/PyQt6-sip/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/PyQt6-sip/metadata.xml b/dev-python/PyQt6-sip/metadata.xml
index 4db1b0254ea4..c37952e6b29f 100644
--- a/dev-python/PyQt6-sip/metadata.xml
+++ b/dev-python/PyQt6-sip/metadata.xml
@@ -6,7 +6,7 @@
<name>Gentoo Qt Project</name>
</maintainer>
<upstream>
- <bugs-to>https://www.riverbankcomputing.com/mailman/listinfo/pyqt/</bugs-to>
+ <bugs-to>https://github.com/Python-SIP/sip/issues</bugs-to>
<remote-id type="pypi">PyQt6-sip</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2024-07-12 16:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 16:26 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 6:36 [gentoo-commits] repo/gentoo:master commit in: dev-python/PyQt6-sip/ Arthur Zamarin
2024-09-12 13:45 Sam James
2024-09-05 1:23 Sam James
2024-09-02 6:16 Sam James
2024-08-31 2:42 Ionen Wolkens
2024-08-12 18:21 Arthur Zamarin
2024-07-27 10:06 Michał Górny
2024-07-27 8:46 Arthur Zamarin
2024-07-12 16:26 Ionen Wolkens
2024-06-29 12:29 Jakov Smolić
2024-06-28 18:05 Sam James
2024-06-28 18:05 Sam James
2024-06-28 14:45 Ionen Wolkens
2024-05-13 5:49 Ionen Wolkens
2023-12-22 22:40 Mart Raudsepp
2023-11-15 17:20 Arthur Zamarin
2023-10-14 14:48 Ionen Wolkens
2023-09-15 6:08 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-08-06 4:32 Ionen Wolkens
2023-07-25 0:10 Ionen Wolkens
2023-04-22 6:53 Ionen Wolkens
2023-04-22 6:53 Ionen Wolkens
2023-04-20 16:15 Ionen Wolkens
2023-04-10 15:07 Ionen Wolkens
2023-03-21 5:49 Ionen Wolkens
2023-02-13 15:59 Ionen Wolkens
2023-01-30 19:11 Ionen Wolkens
2023-01-28 15:56 Ionen Wolkens
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=1720801555.038a6e59b6b32c840b1c97ec10e4e65dd5143718.ionen@gentoo \
--to=ionen@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