From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-qt/
Date: Mon, 1 Jan 2018 18:56:23 +0000 (UTC) [thread overview]
Message-ID: <1514832978.fd08a155e473234cac54d7107165fa2546f1c519.blueness@gentoo> (raw)
commit: fd08a155e473234cac54d7107165fa2546f1c519
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 1 18:55:59 2018 +0000
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Mon Jan 1 18:56:18 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fd08a155
dev-python/pytest-qt: fix metadata.xml
Package-Manager: Portage-2.3.13, Repoman-2.3.3
dev-python/pytest-qt/metadata.xml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/dev-python/pytest-qt/metadata.xml b/dev-python/pytest-qt/metadata.xml
index b90dc9952a1..2b11b948e3b 100644
--- a/dev-python/pytest-qt/metadata.xml
+++ b/dev-python/pytest-qt/metadata.xml
@@ -6,8 +6,7 @@
<name>Anthony G. Basile</name>
</maintainer>
<upstream>
- <remote-id type="pypi">pytest-cov</remote-id>
- <remote-id type="bitbucket">memedough/pytest-cov</remote-id>
- <remote-id type="github">pytest-dev/pytest-cov</remote-id>
+ <remote-id type="pypi">pytest-qt</remote-id>
+ <remote-id type="github">pytest-dev/pytest-qt</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2018-01-01 18:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 18:56 Anthony G. Basile [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-03 16:00 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-qt/ Andrew Ammerlaan
2024-02-24 15:12 Michał Górny
2024-02-24 14:04 Sam James
2024-02-08 4:22 Michał Górny
2024-01-06 9:54 Michał Górny
2023-12-23 5:12 Michał Górny
2023-12-16 13:47 Michał Górny
2023-12-15 12:39 Arthur Zamarin
2023-12-15 10:49 Michał Górny
2023-12-03 5:45 Arthur Zamarin
2023-11-22 16:05 Michał Górny
2023-10-18 11:36 Andrew Ammerlaan
2023-09-11 6:48 Jakov Smolić
2023-03-17 15:23 Michał Górny
2022-11-25 20:36 Arthur Zamarin
2022-11-25 19:11 Sam James
2022-10-26 4:03 Michał Górny
2022-07-24 20:24 Michał Górny
2022-06-24 5:16 Michał Górny
2022-06-08 19:16 Andrew Ammerlaan
2022-05-25 9:43 Andrew Ammerlaan
2022-03-31 13:01 Michał Górny
2022-03-31 12:40 Jakov Smolić
2022-02-22 19:01 Michał Górny
2022-02-20 20:32 Sam James
2022-02-20 16:33 Michał Górny
2022-02-20 16:33 Michał Górny
2022-02-20 16:33 Michał Górny
2022-02-20 16:33 Michał Górny
2022-02-12 23:52 Michał Górny
2021-10-19 0:12 Sam James
2021-06-22 17:59 Andrew Ammerlaan
2021-06-22 17:59 Andrew Ammerlaan
2021-06-11 14:32 Andrew Ammerlaan
2021-06-05 12:19 Andrew Ammerlaan
2021-06-05 10:47 Andrew Ammerlaan
2021-05-22 20:55 Andrew Ammerlaan
2020-12-11 12:58 Michał Górny
2020-10-07 18:44 Joonas Niilola
2020-10-07 16:49 Joonas Niilola
2020-09-21 17:48 Michał Górny
2020-09-21 16:06 Michał Górny
2020-03-27 16:25 Joonas Niilola
2018-05-22 15:32 Mikle Kolyada
2018-05-22 15:31 Mikle Kolyada
2018-01-16 22:06 Anthony G. Basile
2018-01-15 21:29 Anthony G. Basile
2018-01-15 12:27 Anthony G. Basile
2018-01-03 22:16 Anthony G. Basile
2018-01-01 18:26 Anthony G. Basile
2018-01-01 18:10 Anthony G. Basile
2018-01-01 17:55 Anthony G. Basile
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=1514832978.fd08a155e473234cac54d7107165fa2546f1c519.blueness@gentoo \
--to=blueness@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