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. ** Bug watch added: github.com/koppor/jabref/issues #135 https://github.com/koppor/jabref/issues/135 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758772 Title: Upgrade jabref version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jabref/+bug/1758772/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
