jabref: 5.1 -> 5.2 #109870
Closed
jabref: 5.1 -> 5.2 #109870
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This doesn't work for me, when I use 5.2 I get the following error on running [...@nixos:~]$ jabref
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=20993, tid=20994
#
# JRE version: (15.0.1+9) (build )
# Java VM: OpenJDK 64-Bit Server VM (15.0.1+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C 0x0000000000000000
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/lqv1qn0r19kzc9hhibj8k667049196wr-systemd-246.6/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/.../core.20993)
#
# An error report file with more information is saved as:
# /home/.../hs_err_pid20993.log
#
#
Aborted (core dumped) |
SuperSandro2000
added
the
9.needs: human intervention
SuperSandro2000
removed
the
9.needs: human intervention
|
I marked this as stale due to inactivity. → More info |
stale
bot
added
the
2.status: stale
|
trying to update to Builder called die: Cannot wrap '/nix/store/99drq22rvrxsigzalra0d80kj5f83p17-jabref-5.1/lib/runtime/bin/java' because it is not an executable file
Backtrace:
7 assertExecutable /nix/store/mnrankjvp65m4gr6yq92ghdd5i0mj9lc-hook/nix-support/setup-hook
36 makeWrapper /nix/store/mnrankjvp65m4gr6yq92ghdd5i0mj9lc-hook/nix-support/setup-hook
1330 genericBuild /nix/store/7gdji02y6rbnzv5mcxcf3mwksk785y8j-stdenv-linux/setup
2 main /nix/store/9krlzvny65gdc8s7kpb6lkx8cd02c25b-default-builder.sh |
stale
bot
removed
the
2.status: stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/JabRef/jabref/releases.
meta.description for jabref is: "Open source bibliography reference manager"
meta.homepage for jabref is: "https://www.jabref.org"
meta.changelog for jabref is: ""
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 5.2 with grep in /nix/store/i9cw9ilw98pr7ba945aybjs2y9dqb04m-jabref-5.2
directory tree listing: https://gist.github.com/d9782d3741fb0062dab2e8db5b02440a
du listing: https://gist.github.com/45b215b0513c8349a47ece603c8b5517
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-reviewrun on x86_64-linux 11 package built:
Maintainer pings
cc @gebner for testing.