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

Jump to bottom

dbeaver: use github release as src #72310

Closed
wants to merge 1 commit into from
Closed

dbeaver: use github release as src #72310

wants to merge 1 commit into from

Conversation

jojosch
Copy link
Member

@jojosch jojosch commented Oct 30, 2019

Motivation for this change

#71512 (comment)

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • 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 nix-review --run "nix-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.
Notify maintainers

cc @

@c0bw3b
Copy link
Contributor

c0bw3b commented Oct 31, 2019

In this instance, the explanation seems to be: dbeaver/dbeaver#7029
There is a possibility that the release asset linked to the Github tag might also change soon...

And it seems older releases where replaced too -> hash mismatch for v6.1.5 on r19.09 hydra job...

@jojosch jojosch closed this Nov 4, 2019
@jojosch jojosch deleted the dbeaver_6.2.3-gh branch November 4, 2019 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
10.rebuild-darwin: 0 10.rebuild-linux: 0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@jojosch @c0bw3b