public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-trimesh] f44: Revert "Conditionalize python3-manifold dep. for F44, for now"
Date: Thu, 23 Jul 2026 22:39:30 GMT	[thread overview]
Message-ID: <178484637093.1.8715913195518947647.rpms-python-trimesh-3db708386906@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-trimesh
            Branch : f44
            Commit : 3db70838690694785aa3bf10c7073bb6f587699f
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-07-23T23:24:47+01:00
            Stats  : +1/-4 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-trimesh/c/3db70838690694785aa3bf10c7073bb6f587699f?branch=f44

            Log:
            Revert "Conditionalize python3-manifold dep. for F44, for now"

This reverts commit 73b8a6d9bc04a8889b9d99fbeada3ffe5f53780f.

---
diff --git a/python-trimesh.spec b/python-trimesh.spec
index a59d9cb..ae5eab1 100644
--- a/python-trimesh.spec
+++ b/python-trimesh.spec
@@ -9,13 +9,10 @@
 # https://bugzilla.redhat.com/show_bug.cgi?id=2460576
 # https://github.com/nschloe/meshio/issues/1558
 %bcond meshio %{defined fc44}
-# Python bindings for manifold are not yet built in F44:
-# https://src.fedoraproject.org/rpms/manifold/pull-request/1#comment-321943
-#
 # Since the tests for manifold’s Python bindings depend on trimesh, a
 # dependency cycle exists: trimesh → manifold → blender, and then trimesh
 # normally depends on both manifold and blender.
-%bcond manifold %[ %{without bootstrap} && %{undefined fc44} ]
+%bcond manifold %{without bootstrap}
 
 Name:           python-trimesh
 Version:        4.12.2

                 reply	other threads:[~2026-07-23 22:39 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=178484637093.1.8715913195518947647.rpms-python-trimesh-3db708386906@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --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