python39Packages.pycurl: disable failing tests, add SuperSandro2000 as maintainer#168154
Conversation
…s maintainer (cherry picked from commit c270def)
|
We got the history a bit messy, with this commit merged in two copies and also reverted twice, but hopefully people won't get tangled in that during bisection or something. |
That's why I would prefer "daggy" fixes. With them, the same fix commit could be merged into all affected branches without cherry-picking or rebasing. But AFAIK they're against nixpkgs policy or at least against common nixpkgs practice.
Unless I'm unaware of something, 32f4270 is and will be the only (partial) revert regarding this. Unless the branches are being merged in an unexpected order, this should be fine and this one revert will undo the test deactivation from both copies of the workaround.
I hope it will even facilitate bisection, as more packages will now be buildable in revisions in which they otherwise wouldn't have been buildable. |
(cherry picked from commit e62954b)
(cherry picked from commit c270def)
Description of changes
cherry-pick #166335 to
masterto workaround #167971 until #167993 hits master fromstagin/staging-next. As discussed in #167993 (comment), this causes many "re"builds, but only those that are currently (transitively) failing to build onmasterdue to thepycurlbuild problem, anyway. Thus it should be OK to targetmaster.This will be partially reverted by 32f4270 (i.e., the now-failing tests will be re-enabled), which will get introduced from
stagin/staging-nexttomastertogether with the fix-proper from #167993 that shall make those tests pass again.Things done
Built on platform(s)
For non-Linux: Is
sandbox = trueset innix.conf? (See Nix manual)Tested, as applicable:
Tested compilation of all packages that depend on this change using
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usageResult of
nixpkgs-reviewrun on x86_64-linux 11 package marked as broken and skipped:
1 package failed to build:
15 packages built:
Tested basic functionality of all binary files (usually in
./result/bin/)moonraker. I have no idea how to test that. If I launch it without arguments, it fails withFileNotFoundError: [Errno 2] No such file or directory: '/home/das-g/moonraker.conf'but that's hardly to be blamed onpycurl.22.05 Release Notes (or backporting 21.11 Release notes)
nixos/doc/manual/md-to-db.shto update generated release notesFits CONTRIBUTING.md.