fix bitbucket test

tests/test_bitbucket.py

@@ -36,8 +36,8 @@ def test_version(helpers: conftest.Helpers) -> None:
         print(commit)
         assert version in commit
         assert "bitbucket" in commit
-        assert "/jongsoftdev/youless-python-bridge/branches/compare/" in commit
-        assert "%0D1.0" in commit
+        assert "/nielsenb/aniso8601/branches/compare/" in commit
+        assert "%0Dv9.0.0" in commit
 
 
 # integration test for bitbucket snapshots
@@ -76,5 +76,5 @@ def test_snapshot(helpers: conftest.Helpers) -> None:
         print(commit)
         assert version in commit
         assert "bitbucket" in commit
-        assert "/jongsoftdev/youless-python-bridge/branches/compare/" in commit
-        assert "%0Dc04342ef36dd5ba8f7d9b9fce2fb4926ef401fd5" in commit
+        assert "/nielsenb/aniso8601/branches/compare/" in commit
+        assert "%0D55b1b849a57341a303ae47eb67c7ecf8c283b7f8" in commit

tests/testpkgs/bitbucket.nix

@@ -3,19 +3,19 @@
 let
   # Why this package? No reason, I just found a small package that uses tags
   # for release by grepping through nixpkgs for fetchFromBitbucket.
-  owner = "jongsoftdev";
-  repo = "youless-python-bridge";
-  # As of 2023-11-22, latest version is 1.0.1, so we will be testing that it
-  # finds a version greater than 1.0. The rev from 2022-10-01 is an untagged
+  owner = "nielsenb";
+  repo = "aniso8601";
+  # As of 2024-04-23, latest version is 9.0.1, so we will be testing that it
+  # finds a version greater than 9.0.0. The rev from 2021-03-02 is an untagged
   # commit.
   version =
     if (isSnapshot)
     then "0.16-unstable-2022-10-01"
-    else "1.0";
+    else "9.0.0";
   rev =
     if (isSnapshot)
-    then "c04342ef36dd5ba8f7d9b9fce2fb4926ef401fd5"
-    else "1.0";
+    then "55b1b849a57341a303ae47eb67c7ecf8c283b7f8"
+    else "v9.0.0";
 in
 stdenv.mkDerivation rec {
   pname = repo;