public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrick McLean" <chutzpah@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/xmlsec/
Date: Fri, 29 Mar 2024 19:13:17 +0000 (UTC)	[thread overview]
Message-ID: <1711739592.bf0bf11ed36ab4cf358d7434aec1b51ecf9d2215.chutzpah@gentoo> (raw)

commit:     bf0bf11ed36ab4cf358d7434aec1b51ecf9d2215
Author:     Patrick McLean <chutzpah <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 28 20:37:49 2024 +0000
Commit:     Patrick McLean <chutzpah <AT> gentoo <DOT> org>
CommitDate: Fri Mar 29 19:13:12 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf0bf11e

dev-python/xmlsec: Remove ver restriction on lxml (bug #927927)

As per upstream issue, the segfaults are caused die to lxml being linked
against a different libxml2 than xmlsec. This isn't a problem for
package manager installed packages, especially source based installs.

Closes: https://bugs.gentoo.org/927927
Signed-off-by: Patrick McLean <chutzpah <AT> gentoo.org>

 dev-python/xmlsec/{xmlsec-1.3.12-r3.ebuild => xmlsec-1.3.12-r4.ebuild} | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dev-python/xmlsec/xmlsec-1.3.12-r3.ebuild b/dev-python/xmlsec/xmlsec-1.3.12-r4.ebuild
similarity index 91%
rename from dev-python/xmlsec/xmlsec-1.3.12-r3.ebuild
rename to dev-python/xmlsec/xmlsec-1.3.12-r4.ebuild
index 03cc95cdf32d..4dc3a59da936 100644
--- a/dev-python/xmlsec/xmlsec-1.3.12-r3.ebuild
+++ b/dev-python/xmlsec/xmlsec-1.3.12-r4.ebuild
@@ -26,10 +26,9 @@ SLOT="0"
 KEYWORDS="amd64 arm64 ~ppc64 x86"
 
 # Doesn't yet support xmlsec-1.3.0: https://github.com/xmlsec/python-xmlsec/issues/252
-# Doesn't yet support lxml-5: https://github.com/xmlsec/python-xmlsec/issues/277
 RDEPEND="
 	<dev-libs/xmlsec-1.3.0:=[openssl]
-	<dev-python/lxml-5[${PYTHON_USEDEP}]
+	dev-python/lxml[${PYTHON_USEDEP}]
 "
 DEPEND="${RDEPEND}"
 BDEPEND="


             reply	other threads:[~2024-03-29 19:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 19:13 Patrick McLean [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-12  8:31 [gentoo-commits] repo/gentoo:master commit in: dev-python/xmlsec/ Michał Górny
2025-03-11 20:20 Arthur Zamarin
2025-03-10 12:46 Jakov Smolić
2024-05-18 11:46 Michał Górny
2024-05-16 15:03 Arthur Zamarin
2024-05-04  7:31 Arthur Zamarin
2024-05-04  7:17 Arthur Zamarin
2024-04-18  5:34 Michał Górny
2024-01-21  6:21 Michał Górny
2024-01-21  2:44 Sam James
2024-01-21  2:44 Sam James
2024-01-20 18:35 Arthur Zamarin
2024-01-05  6:10 Sam James
2023-11-24 15:56 Michał Górny
2023-06-01 16:53 Arthur Zamarin
2023-05-04 17:04 Michał Górny
2023-04-15  5:40 Sam James

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=1711739592.bf0bf11ed36ab4cf358d7434aec1b51ecf9d2215.chutzpah@gentoo \
    --to=chutzpah@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