Open koppor opened 8 years ago
I have no idea of the debian packaging stuff, but shouldn't it be easier now as we provide deb/rpm packages directly for the upcoming 5.x version?
When we integrate it in debian, the users will automatically use the latest version. Debian users are lazy. They won't upgrade from 3.8.2 (which is the latest version in debian - see https://packages.debian.org/de/sid/jabref) to our upcoming 5.0 if we don't include it fully in debian. Our deb
package is just an ugly workaround.
Thanks for your work! Looking forward to see 5.x in Debian/Ubuntu!
@darkdragon-001 Thank you for your appretiation. We really need help there. I could guide you from the JabRef side.
Thanks for your offer. Unfortunately, I am busy with the plenitude of projects I am working on right now and don't have the capacity to step into a new one :disappointed:
Same here. Thus, on hold until someone (including me) changes his priorities.
btw: If you really woulud upgrade JabRef 3 to 5 in the official debian repositorie you really need to think about to inform the user correct about the transformation of its bib-ifle.
I opened a bug report about that in the past. But my (user) wishes where ignored and it was closed without a fix. https://github.com/JabRef/jabref/issues/3251
@Codeberg Found the link 🎉
I try to collect the pointers at https://github.com/JabRef/user-documentation/issues/227
https://github.com/koppor/jabref/blob/master/jabref-in-debian.md.
This link is broken
A push on GitHub branch synching destroyed all my notes. Neither me or @Siedlerchr have a local copy of the old about
branch. I think, this data is forever lost.
I need to do everything from scratch 🙈
This isssue used to track the status of JabRef packaging to Debian. To ease collaboration, the status is tracked at https://github.com/koppor/jabref/blob/master/jabref-in-debian.md.
Comment here if you intend to work on something, then we can update
jabref-in-debian.md
accordingly.