Bug 257979 - [REVIVE] print/jabref: Bibliographic reference manager
Summary: [REVIVE] print/jabref: Bibliographic reference manager
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2021-08-21 08:06 UTC by O. Hartmann
Modified: 2022-02-23 09:04 UTC (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2021-08-21 08:06:31 UTC
Since print/jabref gone due to an outdated port (java/openjfx8-devel), there is no well-known bibliography manager left in the FreeBSD ports for scientific/TeX based bibliography.
I was wondering if the latest jabref could work with the latest java/openjfx14.

Please reconsider reviving the essential port.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-08-23 05:17:26 UTC
It does work with the latest versions of OpenJFX, a patch copying the port from the last revision, updating it to the latest versions and running QA is needed
Comment 2 Rainer Hurling freebsd_committer freebsd_triage 2021-08-23 17:30:31 UTC
The latest version, 5.3, has no platform independant runnable JAR any more. Instead, one has to download something like the JabRef Linux portable [1] or more complicated, a source tar file from Github [2]. 

[1] https://www.fosshub.com/JabRef.html
[2] https://github.com/JabRef/jabref/releases/tag/v5.3

The installation guide (https://docs.jabref.org/installation) tells about running bin/JabRef after untaring the portable version. This breaks with the following messages:

./bin/JabRef	
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
Aug. 23, 2021 7:14:54 PM com.sun.javafx.application.PlatformImpl startup
WARNUNG: Unsupported JavaFX configuration: classes were loaded from 'module org.jabref.merged.module', isAutomatic: false, isOpen: true
Error in glXCreateNewContext, remote GLX is likely disabled
GLib-GIO-Message: 19:14:54.699: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.
Aug. 23, 2021 7:14:54 PM java.util.prefs.FileSystemPreferences$6 run
WARNUNG: Prefs file removed in background /home/rhurlin/.java/.userPrefs/org/jabref/prefs.xml
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=89286, tid=191667
#
# JRE version: OpenJDK Runtime Environment AdoptOpenJDK-16.0.1+9 (16.0.1+9) (build 16.0.1+9)
# Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK-16.0.1+9 (16.0.1+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  0x0000000000000000
#
# Core dump will be written. Default location: core.89286 (may not exist)
#
# An error report file with more information is saved as:
# /usr/home/rhurlin/Downloads/JabRef/hs_err_pid89286.log
Compiled method (c2)    1250 1033       4       java.util.HashMap::put (13 bytes)
 total in heap  [0x000000081d363490,0x000000081d363830] = 928
 relocation     [0x000000081d3635f0,0x000000081d363618] = 40
 main code      [0x000000081d363620,0x000000081d363720] = 256
 stub code      [0x000000081d363720,0x000000081d363748] = 40
 metadata       [0x000000081d363748,0x000000081d363758] = 16
 scopes data    [0x000000081d363758,0x000000081d363798] = 64
 scopes pcs     [0x000000081d363798,0x000000081d3637e8] = 80
 dependencies   [0x000000081d3637e8,0x000000081d3637f0] = 8
 handler table  [0x000000081d3637f0,0x000000081d363820] = 48
 nul chk table  [0x000000081d363820,0x000000081d363830] = 16
#
# If you would like to submit a bug report, please visit:
#   https://github.com/AdoptOpenJDK/openjdk-support/issues
#
Abbruch(core dumped)


Errors with JavaFX, GLX and JDK16(?) are mentioned. It seems that a revived port would need some overhaul.

HTH,
Rainer
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2021-08-24 01:06:10 UTC
(In reply to Rainer Hurling from comment #2)

For someone without deep Java experience, but with a good working relationship with upstream, whats necessary, or the delta between whats available now, and what was available before (for previous versions) or what we need, to make this restoration and port update easier?
Comment 4 commit-hook freebsd_committer freebsd_triage 2021-11-04 13:54:47 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=29b29dd7bb5820b8402b91bdddeb306ed235357a

commit 29b29dd7bb5820b8402b91bdddeb306ed235357a
Author:     Mateusz Piotrowski <0mp@FreeBSD.org>
AuthorDate: 2021-11-03 21:10:59 +0000
Commit:     Mateusz Piotrowski <0mp@FreeBSD.org>
CommitDate: 2021-11-04 13:54:00 +0000

    print/linux-jabref: Add new port

    This is a port of JabRef. We used to have a native version of JabRef
    available in the ports as print/jabref. Unfortunately, it expired last
    year. print/linux-jabref uses a poratble Linux release and runs in
    Linuxulator. Hopefully, this is only a temporary workaround solution for
    having JabRef on FreeBSD.

    PR:             257979
    Requested by:   Corey Stephan
    Requested by:   O. Hartmann <ohartmann@walstatt.org>

 MOVED                                            |   2 +-
 print/Makefile                                   |   1 +
 print/linux-jabref/Makefile (new)                |  52 +++++
 print/linux-jabref/distinfo (new)                |   7 +
 print/linux-jabref/files/jabref-wrapper.in (new) |   3 +
 print/linux-jabref/pkg-descr (new)               |  16 ++
 print/linux-jabref/pkg-plist (new)               | 247 +++++++++++++++++++++++
 7 files changed, 327 insertions(+), 1 deletion(-)
Comment 5 Mateusz Piotrowski freebsd_committer freebsd_triage 2021-11-04 13:57:18 UTC
In the meantime, I've committed print/linux-jabref. Hopefully, this is going to be a sufficient band-aid for JabRef users for now.
Comment 6 Mikael Urankar freebsd_committer freebsd_triage 2021-11-08 14:36:46 UTC
Is anyone able to test https://github.com/MikaelUrankar/jabref-ports/ ?
Comment 7 O. Hartmann 2022-02-23 09:04:54 UTC
(In reply to Mikael Urankar from comment #6)

Hello there,
thank for the effort. I'll give the patch/port a try as soon as I can get our poudriere to handle "overlays".