diff --git a/python-cramjam.spec b/python-cramjam.spec
index cb1b1c2..64b7a49 100644
--- a/python-cramjam.spec
+++ b/python-cramjam.spec
@@ -33,9 +33,7 @@ Source1:        get_source
 
 %endif
 
-BuildSystem:            pyproject
-BuildOption(install):   -l cramjam
-
+BuildRequires:  python3-devel
 BuildRequires:  tomcli >= 0.8.0
 BuildRequires:  cargo-rpm-macros >= 24
 
@@ -74,7 +72,9 @@ License:        %{shrink:
 %description -n python3-cramjam %{common_description}
 
 
-%prep -a
+%prep
+%autosetup -n cramjam-%{srcversion}
+
 # 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,27 +119,25 @@ done
 %cargo_prep
 
 
-%generate_buildrequires -a
+%generate_buildrequires
+%pyproject_buildrequires
 %cargo_generate_buildrequires
 
 
-%build -p
+%build
 %cargo_license_summary
 %{cargo_license} > LICENSES.dependencies
+%pyproject_wheel
 
 
-%check -a
+%install
+%pyproject_install
+%pyproject_save_files -l cramjam
+
+
+%check
+%pyproject_check_import
 %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'>