Hello Pierre, On Fri, Mar 10, 2023 at 10:23:53PM +0100, Pierre Gruet wrote: > Hi tony, > > On Sun, 12 Feb 2023 10:15:35 -0800 tony mancill <[email protected]> wrote: > > > > Okay, first the good news. There are upstream tags for 2.4.0. I have > > started working on adapting the sequence of debian/patches against the > > new release. > > > > But in addition to not yet being done with that, it didn't seem prudent > > to try to push this into bookwork at the last minute, and that wouldn't > > have given the reverse dependencies any time to react anyway. So I am > > going to work towards an upload to experimental soon, and then we can > > aim for getting this into unstable/testing after the freeze. > > I fully understand your position. However I recently looked at scilab, a > rdep of jogl, and saw it is severely broken -- although a key package, so it > will be shipped in Bookworm anyway. Scilab cannot be run in GUI mode, only > in command-line mode with plots not working (after some tweaking I am > working on). > > Locally I tried to update jogl to version 2.4.0 (I had not seen you were > working on it, sorry), and to do so I also had to update its dependency > gluegen2 to version 2.4.0 (possibly you have already seen it), and then the > command-line mode would allow one to make plots.
Yes, I saw the upload of gluegen2. Thank you for doing that and need to apologize! > Given the Hard freeze begins in two days, I will only touch scilab and not > jogl nor gluegen2 right now. > > It you want, I can upload my changes to gluegen2 and jogl2 to experimental > in the upcoming days. But if you prefer doing it yourself, please tell me > and do so when you are ready :) Please feel free to go ahead with your uploads. Working code, made available to all, is what's important. And there are plenty of other packages for me to work on. :) Best regards, tony
signature.asc
Description: PGP signature
__ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use [email protected] for discussions and questions.
