Red Hat Bugzilla – Bug 1299158
Version 4.1 of JabRef is out
Last modified: 2018-07-22 09:50:06 EDT
New stable version of jabref, 3.2, has been out. It would be nice to have Fedora packages for it. Thanks.
It seems upstream has switched to github for code hosting, and the website is also under migration. We might need to switch the release monitoring too.
New releases: https://github.com/JabRef/jabref/releases
Migration tracking bug: https://github.com/JabRef/jabref/issues/111
I agree, it'd be nice to have an up-to-date version of Jabref in Fedora. Version 2.10 is over a year old (released on Mar 11 2014).
Am not sure how helpful this is to say: Version 3.5 runs stably on F24 in my everyday work with it.
Also: the depending Block https://bugzilla.redhat.com/show_bug.cgi?id=1247399 seems not to move forward (maybe waiting on this issue?). But, in my lay reading, it seems the block is unproblematic. What needs to be done/checked next?
We need the changes in the blocking bug made before we can build a newer jabref.
Actually, after a quick look at 3.5, there may be lots of other deps needed as well:
Error: No Package found for mvn(com.googlecode.java-diff-utils)
Error: No Package found for mvn(com.mashape.unirest:unirest-java)
Error: No Package found for mvn(info.debatty:java-string-similarity)
Error: No Package found for mvn(org.swinglabs:swingx)
Actually, now it is jabref 3.7.
It even changed the build from ant to gradle
I'd be willing to review any dependencies...
(In reply to Susi Lehtola from comment #8)
> I'd be willing to review any dependencies...
Thank you, there are also several dependencies need to be upgraded.
jgoodies update is not that easy. In Debian, upstream software had to be updated.
---------- Forwarded message ----------
From: Emmanuel Bourg <firstname.lastname@example.org>
Date: 2016-12-06 9:48 GMT+01:00
Subject: Re: Freeplane and latest jgoodies-forms: strange runtime error
You've been hit by a binary incompatibility between jgoodies-forms 1.6
and 1.9. The type of the Borders.DLU2 field changed from
javax.swing.Border to com.jgoodies.forms.factories.Paddings.Padding.
This modification is source compatible (Padding implements
javax.swing.Border) but not binary compatible (the JVM attempts to match
the exact signature), thus requiring the StyleEditorPanel class to be
All external libraries are listed at https://github.com/JabRef/jabref/blob/master/external-libraries.txt - required for the upcoming version 4.0 of JabRef relying on JavaFX being available.
Version 3.8.2 does not rely on JavaFX. Its external libraries are listed at https://github.com/JabRef/jabref/blob/v3.8.2/external-libraries.txt
Sure, the dependencies stated at build.gradle are the ones really used: https://github.com/JabRef/jabref/blob/v3.8.2/build.gradle#L70
For the curios persons, the status of Debian packaging is tracked at https://github.com/koppor/jabref/issues/135
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
JavaFX is packaged in Fedora now. Is there anything else preventing an update?
Lots. First off - bug 1247399 was never resolved properly and so nothing provides:
Error: No Package found for mvn(org.openoffice:juh)
Error: No Package found for mvn(org.openoffice:jurt)
Error: No Package found for mvn(org.openoffice:ridl)
Error: No Package found for mvn(org.openoffice:unoil)
There are lots of other missing deps, starting with:
Error: No Package found for mvn(com.github.lgooddatepicker:LGoodDatePicker)
Error: No Package found for mvn(com.impossibl.pgjdbc-ng:pgjdbc-ng)
Error: No Package found for mvn(de.undercouch:citeproc-java)
Error: No Package found for mvn(net.java.dev.glazedlists:glazedlists_java15)
Error: No Package found for mvn(org.citationstyles:locales)
Error: No Package found for mvn(org.citationstyles:styles)
Error: No Package found for mvn(org.xmlunit:xmlunit-core)
Error: No Package found for mvn(org.xmlunit:xmlunit-matchers)
org.xmlunit is only required for testing. This has been fixed in the master branch, but not for the 3.8.2 release.
The other dependencies are still required.
When JabRef 4.0 is released, com.github.lgooddatepicker won't be required anymore.
you may find all missing SPECs for jabref 3.8.2 at my repository on github:
These SPECs are for OpenMandriva but with really few modification you may use them for Fedora too.
Can we first update the "upstream" of JabRef in the package database from Unknown to https://github.com/JabRef/jabref/releases, so that we have automatic release monitoring at least?
Sorry, a further look into the "Recent History" section of the webpage  indicates the release monitoring is working. However, the upstream is shown as "Unknown" and no automatic bug report here in bugzilla.
(In reply to Alick Zhao from comment #18)
> Can we first update the "upstream" of JabRef in the package database from
> Unknown to https://github.com/JabRef/jabref/releases, so that we have
> automatic release monitoring at least?
The upstream url in a.fp.o and release monitoring are not related at all. Release monitoring (and all its metadata) is on https://release-monitoring.org/ instead.
(In reply to Alick Zhao from comment #19)
> […] However, the upstream is shown
> as "Unknown" and no automatic bug report here in bugzilla.
This is a known bug, see https://github.com/fedora-infra/fedora-packages/issues/248 for details. The Jabref spec file in Fedora is correct.
Also, the upstream URL changed, so I created a pull request to get it updated: https://src.fedoraproject.org/rpms/jabref/pull-request/1
Just a note, recent version of JabRef depends on the packages openjfx and java-1.8.0-openjdk-openjfx
jabref 4.2 is now out
Version 4.3.1 out now, the provided version 2.10 is from 2014/03/11, see
An updates version in Fedora with actual dependencies would be nice.
Is there an update on what prevents an update to 4.3.1 ?
What are the missing dependencies ?
(In reply to marc.heinimann from comment #25)
> Is there an update on what prevents an update to 4.3.1 ?
> What are the missing dependencies ?
JavaFX webkit bindings are missing, see bug #1547378.
When manually downloading the binary builds from jabref.org, the webkit element is broken, everything else looks fine. Crashes rarely.
(In reply to Christian Stadelmann from comment #26)
> (In reply to marc.heinimann from comment #25)
> > Is there an update on what prevents an update to 4.3.1 ?
> > What are the missing dependencies ?
> JavaFX webkit bindings are missing, see bug #1547378.
> When manually downloading the binary builds from jabref.org, the webkit
> element is broken, everything else looks fine. Crashes rarely.
Since libjfxwebkit depends on ffmpeg and binary blobs (!) and a packaging of these components is nowhere in sight wouldn't it be easier to package the newest version of jabref now an just put a warning label in the rpm description? Or does this directly violate any redhat packaging guidelines.