Note that packaging JabRef for Ubuntu needs more work than just adding the JAR file. In short: This is because Debian's strong policy regarding code provenance. For instance, in ArchLinux, this is different (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jabref). However, they cannot say which source code went into that jar. For more information see https://wiki.debian.org/ReproducibleBuilds.
The fine-grade TODOs to get JabRef into Debian (and thus into Ubuntu) are listed at https://github.com/koppor/jabref/issues/135. We need help there.
Note that packaging JabRef for Ubuntu needs more work than just adding the JAR file. In short: This is because Debian's strong policy regarding code provenance. For instance, in ArchLinux, this is different (https:/ /aur.archlinux. org/cgit/ aur.git/ tree/PKGBUILD? h=jabref). However, they cannot say which source code went into that jar. For more information see https:/ /wiki.debian. org/Reproducibl eBuilds.
The fine-grade TODOs to get JabRef into Debian (and thus into Ubuntu) are listed at https:/ /github. com/koppor/ jabref/ issues/ 135. We need help there.