Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pythonPackages.exchangelib: removed due to prolonged breakage #95313

Closed
wants to merge 1 commit into from

Conversation

jonringer
Copy link
Contributor

Motivation for this change

There's about 20 other python modules that have been broken prior to the 20.03 release.

Currently I'm just looking for feedback on what the message and convention should be for doing such removals

cc @FRidh

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@vcunat
Copy link
Member

vcunat commented Aug 13, 2020

If something hasn't built successfully for a long time, I don't expect anyone would even notice the removal.

@vcunat
Copy link
Member

vcunat commented Aug 13, 2020

But why not mention the maintainers: @catern

@FRidh
Copy link
Member

FRidh commented Aug 13, 2020

I know some like to throw when software is (re)moved. I don't find showing warnings important, and I think modules can be removed without a trace. Just indeed cc the listed maintainers.

@catern
Copy link
Contributor

catern commented Aug 13, 2020

Thanks for pinging me, let me give fixing it a try.

@jonringer
Copy link
Contributor Author

But why not mention the maintainers: @catern

@vcunat because there's about 20 other packages, all with different maintainers. I was more or less looking for feedback that the wording of the error is acceptable, so I could move forward with removing the other packages.

@vcunat
Copy link
Member

vcunat commented Aug 13, 2020

Ah, I see. Well, I see no harm in trying the process including this step.

@jonringer
Copy link
Contributor Author

I'll make a PR per removal if a maintainer is listed, otherwise I'll make another PR to remove all the unmaintained packages

@jonringer
Copy link
Contributor Author

#95265

catern added a commit to catern/nixpkgs that referenced this pull request Aug 13, 2020
Also marks the package as no longer broken.

Obsoletes PR NixOS#95313
@catern
Copy link
Contributor

catern commented Aug 13, 2020

Sorry for the long breakage, but it's fixed now (and upgraded to boot)

jonringer pushed a commit that referenced this pull request Aug 13, 2020
Also marks the package as no longer broken.

Obsoletes PR #95313
@jonringer jonringer closed this Aug 13, 2020
@jonringer jonringer deleted the remove-broken-py branch August 13, 2020 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants