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

perlPackages.TimeDate: fix tests that fail as of 2020 #78757

Merged

Conversation

knl
Copy link
Contributor

@knl knl commented Jan 29, 2020

Motivation for this change

TimeDate tests in 19.09 fail as of 2020: https://hydra.nixos.org/job/nixpkgs/nixpkgs-19.09-darwin/perl530Packages.TimeDate.x86_64-darwin.

This has been fixed on master, this PR cherrypicks that change.

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.

@knl knl requested a review from basvandijk January 29, 2020 09:40
@basvandijk
Copy link
Member

@GrahamcOfBorg build perlPackages.TimeDate

@@ -18720,6 +18720,8 @@ let
url = mirror://cpan/authors/id/G/GB/GBARR/TimeDate-2.30.tar.gz;
sha256 = "11lf54akr9nbivqkjrhvkmfdgkbhw85sq0q4mak56n6bf542bgbm";
};
# https://rt.cpan.org/Public/Bug/Display.html?id=124509
patches = [ ../development/perl-modules/timedate-2020.patch ];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please use fetchPatch from atoomic/perl-TimeDate@4b67ccb ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree using fetchPatch would be better. However let's do this in a separate PR against master and cherry-pick it here. Ideally most commits in release branches are just cherry picks.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See: #78765

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