El mié., 5 feb. 2020 9:28, Vitaly Zaitsev via devel < devel(a)lists.fedoraproject.org&gt; escribió: But I believe Bill Chatfield was trying to revive it (see other recent Java threads in this list), so you may want to help him, and eventually support this software. Iñaki

Am 05.02.20 um 09:55 schrieb Code Zombie: I don't know the Netbeans code but in Fedora we need to build each package from source (no precompiled jars). That means we also need to ship *all* dependencies with the required versions. Currently the Fedora Java stack is not in a good shape because the original Fedora packagers left or are focussed on the "modular" Java stack in Fedora. We have a few individuals who try to fix this but they really need help. -> I suspect there will be quite a few missing/broken/outdated dependencies in Fedora which need to be packaged/fixed first before something like Netbeans can be shipped in Fedora. Please let us know if you are interested in becoming a packager to help with this problem (though I'd like to warn you that this probably requires quite some efforts and you should not expect quick wins). Felix

On Wed, Feb 5, 2020 at 9:22 AM Vitaly Zaitsev via devel <devel(a)lists.fedoraproject.org&gt; wrote: When I read this I'm always puzzled by the negativity. What is "completely broken" exactly that you need? Things seem to work quite well. Cheers, Mario -- Mario Torre Associate Manager, Software Engineering Red Hat GmbH <https://www.redhat.com> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898

On Wed, Feb 5, 2020 at 2:41 PM Fabio Valentini <decathorpe(a)gmail.com&gt; wrote: First of all, thank you for your work! I know it may not mean much but it is appreciated. On a general side, I would say, however, that this is the nature of every collaborative effort, isn't it? Also, I can only speak for JMC (since my team owns this) and for OpenJDK (since I'm part of the OpenJDK team an Jiri own this), and I know the base is sound. And we aren't required to do any of this work, but we do it because we want to have Fedora a great platform for Java development, so we put efforts in ensuring that OpenJDK (and JMC) are packaged correctly. Also, there is always the risk that someone leaves to do better things, but this doesn't mean "completely broken" (otherwise why haven't the packages been retired?), so I think my first question is still valid. Cheers, Mario -- Mario Torre Associate Manager, Software Engineering Red Hat GmbH <https://www.redhat.com> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898

FYI, I'm still planning on working on the Java packaging issues. But, still working on figuring out how to do the work. I've had a lot of other problems come up lately so I have not made too much progress. But, I still expect to be working on this soon. On Wednesday, February 5, 2020, 9:11:25 AM EST, Fabio Valentini <decathorpe(a)gmail.com&gt; wrote: On Wed, Feb 5, 2020 at 2:55 PM Mario Torre <neugens(a)redhat.com&gt; wrote: <> Thank you. Sure. Some members of the Stewardship SIG also work on DogTag PKI, so they actually need a working Java stack. On the other hand, I don't use any Java packages at all (other than OpenJDK itself), and just took ownership of most packages to prevent them from being removed and 25% of fedora imploding. Your work is appreciated :) OpenJDK works quite well. "Completely broken" is a rather pessimistic point of view. For example, because of our continued work, of the ~240 packages the Stewardship SIG maintains, *none* failed to build in the f32 mass rebuild. However, due to a lack of manpower, we need to focus our effort on basically 1) keep packages building, 2) fix CVEs filed against our packages. Some packages we can keep up-to-date without much effort, but we can't deal with the few gnarly bits since the people who knew how to deal with those packages have either left or abandoned non-modular Java packages. So to answer your question, the only reasons why not more packages have been retired is 1) we took them when they were orphaned, 2) we fix FTBFS issues, and 3) we fix CVEs. But that's really the bare minimum to prevent packages from being removed entirely. We can reuse some work from the modular branches, but the modular Java maintainers have made it clear that they are not interested in helping us. So ... collaborative effort? Not so much Fabio _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

The flatpak packages seem huge in size (at least that's what is shown in the Gnome Software application). Also, for one, Flatpak version of Eclipse does not support built-in support. On Wed, Feb 5, 2020 at 4:12 AM Aleksandar Kurtakov <akurtako(a)redhat.com&gt; wrote:

On 05.02.2020 10:11, Aleksandar Kurtakov wrote: Then start building Fedora native flatpaks. Flatpak != Flathub. Flathub is a third-party repository. -- Sincerely, Vitaly Zaitsev (vitaly(a)easycoding.org)