[Bug 832853] Review Request: java3d - Java 3D
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=832853
--- Comment #35 from Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> ---
Oh, nice. Not sure if Eric still plans to package this. Even if not, somebody
will sooner or later because there's still software out there that depends on
java3d.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
5 years, 3 months
[Bug 832853] Review Request: java3d - Java 3D
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=832853
Harvey Harrison <harvey.harrison(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(harvey.harrison@g |
|mail.com) |
--- Comment #34 from Harvey Harrison <harvey.harrison(a)gmail.com> ---
I have pulled in the changes that separate Java3d from java3d-utils. I have
tagged a version 1.6.2 in each of the projects vecmath, j3dcore and j3dutils.
This should resolve the licensing issue with java3d as it no longer requires
any of the code from j3dutils with the problematic statements.
The tags, or master branchs here can be used to package:
https://github.com/hharrison/vecmath
https://github.com/hharrison/java3d-core
https://github.com/hharrison/java3d-utils
Please advise if you run into any issues packaging, but at this point it should
be ready to go now.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
5 years, 3 months
[Bug 1645294] Review Request: delve - Debugger for Go programming
language
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1645294
--- Comment #15 from Derek Parker <deparker(a)redhat.com> ---
All dependencies have been packaged now, however because of the default setup
for Go packaging (symlinking to `_build`) tests are failing due to not
evaluating the symlinks in tests where the debug information generated in the
binary actually _does_ eval symlinks. There will be a fix for this in the next
release which should be out this week or early next week, so I'll just wait for
that to finish up this package.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
5 years, 3 months