docutils: 0.19 → 0.20.1#243078
Conversation
|
I believe this should be into staging, because of too much rebuilds. |
|
Ping to rebase this over staging. |
|
Oops. Something happened. Was |
7145ed2 to
d85ca78
Compare
|
You need to set this on Github too. There is a small tutorial on Contributing.md (If this is too hard to follow, you can close this PR and open a new one.) |
|
@AndersonTorres I think it’s all cleared up (other than pinging like 10 new people). I could start a new merge request if preferable. In the unlikely event that the tests fail, I’ll open a new merge request. |
|
Ok. It was less dramatic than I was thought initially. I would like someone tested Darwin locally, because ofborg is bailing out. |
|
Has anyone tested on Darwin? |
|
Bisect says commit 20642ff broke |
|
@trofi do you prefer a revert? |
|
I have no preference. My system uses |
|
Sphinx should support 0.20.x |
|
I use |
|
Sphinx is @ 7.1.x, but Nixpkgs unstable @ 5.3.x. IMO this is something that should be raised with Sphinx’s maintainer to update rather than holding back & reverting this stable version. Both this docutils version & that patch to Sphinx have been out since 2023-06. Edit: already an open issue #249230 |
|
I believe the best course of action is really a reversion. |
Revert "docutils: 0.19 → 0.20.1" This commit reverts #243078 Nixpkgs ships Sphinx 5.3.0, that does not support docutils >= 0.20. The most recent version available at the upstream is Sphinx 7.1.2; however its update is far from trivial. In order to bring the system to a consistent state (and hopefully update everything again), this revert is imperative.
Description of changes
fixes #243069
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Maintainer: @AndersonTorres