Your message dated Wed, 21 Jun 2023 21:44:37 +0200
with message-id <[email protected]>
and subject line Fixed in experimental, now in unstable
has caused the Debian Bug report #1011549,
regarding openrocket needs newer jogl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1011549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libjogl2-java
Version: 2.3.2+dfsg-9
I'm working on re-packaging openrocket so that it can go back into
Debian main. A big part of the work is eliding all the embedded class
library jar files and replacing those with Debian library packages.
One of the class libraries is jogl, for which openrocket apparently
needs jogl 2.4 with patches applied by Sibo:
https://github.com/openrocket/openrocket/issues/1156
https://github.com/openrocket/openrocket/pull/1157
Is there any chance we could freshen the Debian package? I see that
jogamp.org still shows 2.3.2 as the most recent "stable" release, but
that's about 7 years old.
I'm linking against the 2.3.2 package now, and the core of openrocket is
working ok, but none of the 3d rendering features will work until we get
to a fresher jogl version.
Regards,
Bdale
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.4.0+dfsg-1~exp1
Hello,
The bug is fixed in the version in experimental, which will land in sid
very soon.
Best,
--
Pierre
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
__
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.
