public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/weasyprint/
Date: Sun, 11 Jun 2023 13:46:37 +0000 (UTC)	[thread overview]
Message-ID: <1686491165.fcfadc5ce4bcb8b77dd650285c246f146271d097.sam@gentoo> (raw)

commit:     fcfadc5ce4bcb8b77dd650285c246f146271d097
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 11 13:46:05 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jun 11 13:46:05 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fcfadc5c

dev-python/weasyprint: Stabilize 59.0 amd64, #908368

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/weasyprint/weasyprint-59.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/weasyprint/weasyprint-59.0.ebuild b/dev-python/weasyprint/weasyprint-59.0.ebuild
index 7a8466c8f3fc..50701af2f2b5 100644
--- a/dev-python/weasyprint/weasyprint-59.0.ebuild
+++ b/dev-python/weasyprint/weasyprint-59.0.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 
 RDEPEND="
 	>=dev-python/cffi-0.6:=[${PYTHON_USEDEP}]


             reply	other threads:[~2023-06-11 13:46 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 13:46 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-31 19:34 [gentoo-commits] repo/gentoo:master commit in: dev-python/weasyprint/ Arthur Zamarin
2024-10-30 16:41 Michał Górny
2024-07-06  8:33 Michał Górny
2024-07-06  6:39 Sam James
2024-06-25  7:27 Petr Vaněk
2024-06-22 17:52 Michał Górny
2024-06-22 17:18 Sam James
2024-06-22  5:33 Michał Górny
2024-06-05  4:51 Michał Górny
2024-05-22 11:58 Michał Górny
2024-05-22 11:40 Michał Górny
2024-05-07  1:57 Michał Górny
2024-05-01  4:34 Michał Górny
2024-03-23 11:58 Michał Górny
2024-03-23 11:53 Michał Górny
2024-03-09  7:18 Michał Górny
2024-03-07 15:59 Michał Górny
2024-02-26 17:48 Michał Górny
2024-02-13  4:27 Michał Górny
2023-12-30 14:26 Arthur Zamarin
2023-12-11 17:42 Michał Górny
2023-10-28 18:24 Michał Górny
2023-10-28 16:48 Arthur Zamarin
2023-10-27 16:21 Michał Górny
2023-09-29 19:15 Arthur Zamarin
2023-09-26  4:42 Michał Górny
2023-06-11 16:15 Michał Górny
2023-05-11 17:58 Michał Górny
2023-03-25  5:02 Michał Górny
2023-03-24 20:26 Arthur Zamarin
2023-03-08  4:44 Michał Górny
2023-02-21  8:00 Michał Górny
2023-02-21  8:00 Michał Górny
2023-02-20 23:28 Sam James
2023-02-17 18:51 Michał Górny
2023-01-18 11:15 Michał Górny
2022-12-24  7:41 Michał Górny
2022-11-30 20:49 Arthur Zamarin
2022-11-14  5:07 Michał Górny
2022-11-05 14:34 Michał Górny
2022-11-04 18:06 Arthur Zamarin
2022-11-04 18:06 Arthur Zamarin
2022-10-19  3:49 Michał Górny
2022-10-02  3:15 Sam James
2022-10-01  8:33 Sam James
2022-07-25  7:12 Michał Górny
2022-07-08  7:40 Arthur Zamarin
2022-06-16  8:10 Michał Górny
2022-05-21  9:24 Michał Górny
2022-05-21  9:24 Michał Górny
2022-05-16 13:30 Michał Górny
2022-04-05  7:53 Michał Górny
2022-02-28  8:28 Michał Górny
2022-01-08 16:57 Arthur Zamarin
2021-11-14 20:53 Michał Górny
2021-10-17  9:44 Michał Górny
2021-09-11  7:15 Michał Górny
2021-08-28  6:54 Michał Górny
2021-08-07 14:07 Michał Górny
2021-08-07 14:07 Michał Górny
2021-08-07 14:07 Michał Górny
2021-08-07 14:07 Michał Górny
2021-08-01  8:17 Michał Górny
2021-04-18  7:05 Michał Górny
2021-03-11 22:59 Michał Górny
2021-03-03  8:07 Michał Górny
2020-10-16 18:22 Michał Górny
2019-12-28 16:16 David Seifert
2019-08-28  8:19 David Seifert
2019-03-01  0:26 Aaron Bauman
2018-11-17  3:49 Virgil Dupras
2018-11-17  3:49 Virgil Dupras
2018-02-07  6:37 Thomas Deutschmann
2018-01-06 13:39 Michał Górny
2017-11-08  7:08 Patrick Lauer
2017-09-18 18:11 Patrick Lauer
2017-07-07  9:36 Aaron Swenson
2016-06-29  9:50 Patrick Lauer
2016-03-01 19:46 Patrick Lauer

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=1686491165.fcfadc5ce4bcb8b77dd650285c246f146271d097.sam@gentoo \
    --to=sam@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