public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Karolina Surma <ksurma@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-beautifulsoup4] rawhide: Temporarily change the upper bound of the skipped libxml2 version
Date: Fri, 05 Jun 2026 10:50:12 GMT	[thread overview]
Message-ID: <178065661271.1.7318639004667991232.rpms-python-beautifulsoup4-3d2c3182fc81@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-beautifulsoup4
Branch : rawhide
Commit : 3d2c3182fc8118181691c5794cf74f00dae307ee
Author : Karolina Surma <ksurma@redhat.com>
Date   : 2026-06-05T12:47:17+02:00
Stats  : +1/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/python-beautifulsoup4/c/3d2c3182fc8118181691c5794cf74f00dae307ee?branch=rawhide

Log:
Temporarily change the upper bound of the skipped libxml2 version

---
diff --git a/0001-Skip-the-lxml-tree-builder-s-test_surrogate_in_chara.patch b/0001-Skip-the-lxml-tree-builder-s-test_surrogate_in_chara.patch
index 866492f..415e736 100644
--- a/0001-Skip-the-lxml-tree-builder-s-test_surrogate_in_chara.patch
+++ b/0001-Skip-the-lxml-tree-builder-s-test_surrogate_in_chara.patch
@@ -54,7 +54,7 @@ index 0b69956..aa82143 100644
 +    # For lxml only, we need to skip the test if the libxml2 version doesn't
 +    # have the fix from https://gitlab.gnome.org/GNOME/libxml2/-/commit/4dcc2d743eb83b8aaec0d91660d615fdb024dad0. That means any pre-2.13 version.
 +    @pytest.mark.skipif(
-+        "etree.LIBXML_VERSION < (2, 13, 0)",
++        "etree.LIBXML_VERSION < (2, 14, 0)",
 +        reason="libxml version doesn't issue REPLACEMENT CHARACTER",
 +    )
 +    def test_surrogate_in_character_reference(self):

                 reply	other threads:[~2026-06-05 10:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178065661271.1.7318639004667991232.rpms-python-beautifulsoup4-3d2c3182fc81@fedoraproject.org \
    --to=ksurma@redhat.com \
    --cc=git-commits@fedoraproject.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