diff --git a/python-cramjam.spec b/python-cramjam.spec
index 64b7a49..cb1b1c2 100644
--- a/python-cramjam.spec
+++ b/python-cramjam.spec
@@ -33,7 +33,9 @@ Source1:        get_source
 
 %endif
 
-BuildRequires:  python3-devel
+BuildSystem:            pyproject
+BuildOption(install):   -l cramjam
+
 BuildRequires:  tomcli >= 0.8.0
 BuildRequires:  cargo-rpm-macros >= 24
 
@@ -72,9 +74,7 @@ License:        %{shrink:
 %description -n python3-cramjam %{common_description}
 
 
-%prep
-%autosetup -n cramjam-%{srcversion}
-
+%prep -a
 # Downstream-only: patch out the generate-import-lib feature, which is only
 # relevant on Windows, and which depends on the corresponding pyo3 feature –
 # which is not packaged for that reason.
@@ -119,25 +119,27 @@ done
 %cargo_prep
 
 
-%generate_buildrequires
-%pyproject_buildrequires
+%generate_buildrequires -a
 %cargo_generate_buildrequires
 
 
-%build
+%build -p
 %cargo_license_summary
 %{cargo_license} > LICENSES.dependencies
-%pyproject_wheel
 
 
-%install
-%pyproject_install
-%pyproject_save_files -l cramjam
-
-
-%check
-%pyproject_check_import
+%check -a
 %if %{with tests}
+# Test failures in test_variants_decompress_into with recent hypothesis
+# versions: https://github.com/milesgranger/cramjam/issues/201
+#
+# It is hard to be really sure what is going on here. The failures are
+# concerning, and might (or might not) reflect a serious problem. Nevertheless,
+# since the problem appears to be linked to newer hypothesis versions, there’s
+# not reason to believe that the package has *new* problems. It *might* have
+# newly *revealed* problems. This merits further investigation.
+k="${k-}${k+ and }not test_variants_decompress_into"
+
 # Regression with miniz_oxide>0.8.5
 # https://github.com/milesgranger/cramjam/issues/211
 # Failed: DID NOT RAISE <class 'cramjam.DecompressionError'>