| 8 Jan 2026 |
hexa | cabal2nix depends on django???? | 20:42:31 |
hexa | error: django-4.2.27 not supported for interpreter python3.13
note: trace involved the following derivations:
derivation 'cabal2nix-2.20.1'
derivation 'nix-prefetch-scripts'
derivation 'nix-prefetch-bzr'
derivation 'python3.13-breezy-3.3.12'
derivation 'python3.13-launchpadlib-2.1.0'
derivation 'python3.13-httplib2-0.22.0'
derivation 'python3.13-pytest-randomly-3.13.0'
derivation 'python3.13-factory-boy-3.3.3'
| 20:49:48 |
hexa | I think you backported the thing | 20:49:55 |
hexa | which I said I needed to look into but did not | 20:50:10 |
hexa | Redacted or Malformed Event | 20:51:03 |
hexa | the reason the disable cannot be backported is that django 4.2 is the default python on 25.11 | 21:12:35 |
hexa | and I repeat that it is my mistake that I misjudged the version constraints | 21:12:59 |
Sandro 🐧 | Is anyone using bzr? We could probably turn that off per default | 21:17:53 |
hexa | bzr is far from the only consumer, so that is not a solution | 21:18:30 |
hexa | I repeat: it is the default django on 25.11 | 21:19:01 |
hexa | so the disable was fine for unstable, it is not for 25.11 | 21:19:11 |
vcunat | I can un-disable, but that django version still won't build. | 21:32:21 |
vcunat | (that's why I looked for what happened to that version on unstable and backported the disablement blindly) | 21:32:53 |
hexa | I know | 21:33:08 |
hexa | disable the one failing test | 21:45:43 |
hexa | and fixed the formatting on awscli2 | 21:45:49 |