On 18. 03. 19 22:58, Richard W.M. Jones wrote:
The actual effect of this is that I'm going to disable Java bindings
for all the affected packages. Java loses, Fedora loses.
Everybody looses :(
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
__
On Mon, Mar 18, 2019 at 10:34:23AM +0100, Jakub Jelen wrote:
> On Fri, 2019-03-15 at 19:36 -0400, Gerald Henriksen wrote:
> > On Fri, 15 Mar 2019 23:48:49 +0100, you wrote:
> >
> > > * Richard W.M. Jones [15/03/2019 20:23] :
> > > > Is Java being dropped from the distro?
> > >
> > > Yes, that's w
On Mon, 18 Mar 2019 at 05:35, Jakub Jelen wrote:
>
> On Fri, 2019-03-15 at 19:36 -0400, Gerald Henriksen wrote:
> > On Fri, 15 Mar 2019 23:48:49 +0100, you wrote:
> >
> > > * Richard W.M. Jones [15/03/2019 20:23] :
> > > > Is Java being dropped from the distro?
> > >
> > > Yes, that's what we were
On Fri, 2019-03-15 at 19:36 -0400, Gerald Henriksen wrote:
> On Fri, 15 Mar 2019 23:48:49 +0100, you wrote:
>
> > * Richard W.M. Jones [15/03/2019 20:23] :
> > > Is Java being dropped from the distro?
> >
> > Yes, that's what we were warned about months ago.
>
> Don't think so.
>
> Nothing has
On Fri, 15 Mar 2019 23:48:49 +0100, you wrote:
>* Richard W.M. Jones [15/03/2019 20:23] :
>> Is Java being dropped from the distro?
>
>Yes, that's what we were warned about months ago.
Don't think so.
Nothing has been said about dropping Java, and if anything the OpenJDK
packagers have been mor
* Richard W.M. Jones [15/03/2019 20:23] :
>
> These are very important packages. What do we have to do here?
I'm going to repeat this until it sinks in...
If you (this is the generic you, not you specifically) want these
packages to be in the distribution, you need to step up and ask for
maintai
On Fri, Mar 15, 2019 at 12:40:00PM -0400, Todd Zullinger wrote:
> Richard W.M. Jones wrote:
> > On Tue, Mar 12, 2019 at 11:38:47AM +0100, Miro Hrončok wrote:
> >> rjones: apache-ivy, maven-jar-plugin, maven-javadoc-plugin, gradle,
> >> xmvn, plexus-utils
> >
> > I'm unclear what if anything I coul
Richard W.M. Jones wrote:
> On Tue, Mar 12, 2019 at 11:38:47AM +0100, Miro Hrončok wrote:
>> rjones: apache-ivy, maven-jar-plugin, maven-javadoc-plugin, gradle,
>> xmvn, plexus-utils
>
> I'm unclear what if anything I could do (apart from maintaining loads
> of Java packages which isn't going to h
On Tue, Mar 12, 2019 at 11:38:47AM +0100, Miro Hrončok wrote:
> rjones: apache-ivy, maven-jar-plugin, maven-javadoc-plugin, gradle,
> xmvn, plexus-utils
I'm unclear what if anything I could do (apart from maintaining loads
of Java packages which isn't going to happen). Is the email saying
that so
On Tue, 12 Mar 2019 at 06:53, Miro Hrončok wrote:
>
> You can build Java apps as modules, yes.
> If we remove the mentioned packages from rawhide, it will be the only way to
> build Java packages.
How are the Java applications that come with C (JNI) extensions
handled in the modules model? How do
On 13. 03. 19 18:05, Christopher wrote:
On Wed, Mar 13, 2019 at 10:07 AM Randy Barlow
wrote:
On Tue, 2019-03-12 at 18:39 -0400, Christopher wrote:
Well, the packager experience I'm expecting in 3 weeks is: "almost
all
of my dependencies and BuildRequires are gone; I can't build
anything".
How
On Wed, Mar 13, 2019 at 6:23 AM Mikolaj Izdebski wrote:
>
> On Wed, Mar 13, 2019 at 7:21 AM Fabio Valentini wrote:
> > Can you give us a minimal set of packages that is required to make sure
> > libreoffice etc. aren't caught up in the mass retirement?
>
> The minimal package set is the contents
On Wed, Mar 13, 2019 at 10:07 AM Randy Barlow
wrote:
>
> On Tue, 2019-03-12 at 18:39 -0400, Christopher wrote:
> > Well, the packager experience I'm expecting in 3 weeks is: "almost
> > all
> > of my dependencies and BuildRequires are gone; I can't build
> > anything".
> > How much worse could it
On Tue, 2019-03-12 at 18:39 -0400, Christopher wrote:
> Well, the packager experience I'm expecting in 3 weeks is: "almost
> all
> of my dependencies and BuildRequires are gone; I can't build
> anything".
> How much worse could it get than that?
Fair. I don't think we anticipated the large migrati
On Wed, Mar 13, 2019 at 12:49 PM Florian Weimer wrote:
>
> * Mikolaj Izdebski:
>
> >> As far as I understand it, under the Koji model, one of the tags wins,
> >> and which one determines whether you get the Python 2 subpackage or the
> >> Python 3 subpackage. You cannot get both. You will need t
* Mikolaj Izdebski:
>> As far as I understand it, under the Koji model, one of the tags wins,
>> and which one determines whether you get the Python 2 subpackage or the
>> Python 3 subpackage. You cannot get both. You will need two or more
>> buildroots for that.
>
> That used to be the case, bu
On Wed, Mar 13, 2019 at 11:59 AM Florian Weimer wrote:
>
> * Mikolaj Izdebski:
>
> > On Tue, Mar 12, 2019 at 4:42 PM Miroslav Suchý wrote:
> >> Alternative sum up:
> >> * People (not just Mikolaj) started using modules, while Koji cannot use
> >> modular repos.
> >
> > Incorrect. Koji (the softw
* Mikolaj Izdebski:
> On Tue, Mar 12, 2019 at 4:42 PM Miroslav Suchý wrote:
>> Alternative sum up:
>> * People (not just Mikolaj) started using modules, while Koji cannot use
>> modular repos.
>
> Incorrect. Koji (the software) *can* use modular repos. I know of more
> than one installation of K
On Wed, Mar 13, 2019 at 7:21 AM Fabio Valentini wrote:
> Can you give us a minimal set of packages that is required to make sure
> libreoffice etc. aren't caught up in the mass retirement?
The minimal package set is the contents of javapackages-tools module,
stream 201801. There are about 185 pa
Hi,
On 3/13/19 9:45 AM, Emmanuel Seyman wrote:
* Hans de Goede [13/03/2019 08:51] :
A solution for this needs to be found and be in place *before* dropping
these packages not the otherway around.
We've known the solution for months, now.
If you (this is the generic you, not you specifically
On Tue, 2019-03-12 at 21:24 +0100, Mikolaj Izdebski wrote:
> On Tue, Mar 12, 2019 at 3:11 PM Jakub Jelen
> wrote:
> > On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote:
> > > Hmm,
> > > https://lists.fedoraproject.org/archives/list/java-de...@lists.fedoraproject.org/thread/MQMRQVENBLDRS
* Hans de Goede [13/03/2019 08:51] :
>
> A solution for this needs to be found and be in place *before* dropping
> these packages not the otherway around.
We've known the solution for months, now.
If you (this is the generic you, not you specifically) want these packages
to be in the distribution
Hi,
On 12-03-19 11:38, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_
On Wed, Mar 13, 2019, 07:42 Alexander Bokovoy wrote:
> On ke, 13 maalis 2019, Fabio Valentini wrote:
> >On Tue, Mar 12, 2019, 22:37 Mikolaj Izdebski wrote:
> >
> >> On Tue, Mar 12, 2019 at 12:17 PM Dominik 'Rathann' Mierzejewski
> >> wrote:
> >> >
> >> > On Tuesday, 12 March 2019 at 12:02, Miko
On ke, 13 maalis 2019, Fabio Valentini wrote:
On Tue, Mar 12, 2019, 22:37 Mikolaj Izdebski wrote:
On Tue, Mar 12, 2019 at 12:17 PM Dominik 'Rathann' Mierzejewski
wrote:
>
> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen
wrote:
> >
On Tue, Mar 12, 2019, 22:37 Mikolaj Izdebski wrote:
> On Tue, Mar 12, 2019 at 12:17 PM Dominik 'Rathann' Mierzejewski
> wrote:
> >
> > On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> > > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen
> wrote:
> > > >
> > > > Is there already a way t
On Tue, Mar 12, 2019 at 6:03 PM Randy Barlow
wrote:
> As Miro said in another post, it's not that FESCo doesn't want to use
> modules in Koji, it's that we want to make sure that the packager
> experience is as good as it was pre-modularity, and in particular that
> packagers can build locally as
On Tue, 2019-03-12 at 22:18 +0100, Mikolaj Izdebski wrote:
> It's Fedora developers (represented by
> elected body of FESCo) that don't want to use modules in Fedoras'
> Koji
> installation.
As Miro said in another post, it's not that FESCo doesn't want to use
modules in Koji, it's that we want to
On 12. 03. 19 22:11, Mikolaj Izdebski wrote:
I hope FESCo
will finally realize how important it is to allow building any package
against modules and change the policy, allowing modules to be used as
build dependencies for non-modular packages.
Oh we do realize. Especially since everything will
On Tue, Mar 12, 2019 at 12:17 PM Dominik 'Rathann' Mierzejewski
wrote:
>
> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
> > >
> > > Is there already a way to package the java application as a module or
> > > we will really rem
On Tue, Mar 12, 2019 at 4:42 PM Miroslav Suchý wrote:
> Alternative sum up:
> * People (not just Mikolaj) started using modules, while Koji cannot use
> modular repos.
Incorrect. Koji (the software) *can* use modular repos. I know of more
than one installation of Koji that successfully builds no
On Tue, Mar 12, 2019 at 6:20 PM Christopher wrote:
> Addendum: some of us part-time packagers, which depended on these
> packages to build our own Java packages don't know how to convert to
> modular packaging. I'm still trying to learn in my spare time, but I
> don't know where to look and have l
On Tue, Mar 12, 2019 at 3:11 PM Jakub Jelen wrote:
>
> On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote:
> > Hmm,
> > https://lists.fedoraproject.org/archives/list/java-de...@lists.fedoraproject.org/thread/MQMRQVENBLDRS67WLNQ7EOCMSDI5WIET/
> > seems that people had a lot of time to act
On Tue, Mar 12, 2019 at 11:43 AM Miroslav Suchý wrote:
>
> Dne 12. 03. 19 v 12:34 Neal Gompa napsal(a):
> > This whole process was handled in the worst possible way. To sum up:
> > * No one knew Java SIG was having manpower issues because Mikolaj
> > didn't know how to ask for help
> > * Now it's
Dne 12. 03. 19 v 12:34 Neal Gompa napsal(a):
> This whole process was handled in the worst possible way. To sum up:
> * No one knew Java SIG was having manpower issues because Mikolaj
> didn't know how to ask for help
> * Now it's too late because he orphaned nearly 1700 packages to force
> modular
On Tue, 2019-03-12 at 12:16 +0100, Dominik 'Rathann' Mierzejewski
wrote:
> Maybe, but it will cause the removal of other packages that depend on
> their regular (non-modular) builds. You are forcing the hands of
> their
> maintainers before the infrastructure to make modular packages
> available
>
On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote:
> On Tue, Mar 12, 2019 at 1:36 PM Neal Gompa
> wrote:
>
> > On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov <
> > akurt...@redhat.com>
> > wrote:
> > > On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
> > domi...@gr
On Tue, Mar 12, 2019 at 8:35 AM Mikolaj Izdebski wrote:
>
> On Tue, Mar 12, 2019 at 12:36 PM Neal Gompa wrote:
> > This whole process was handled in the worst possible way. To sum up:
> > * No one knew Java SIG was having manpower issues because Mikolaj
> > didn't know how to ask for help
>
> You
On Tue, Mar 12, 2019 at 12:36 PM Neal Gompa wrote:
> This whole process was handled in the worst possible way. To sum up:
> * No one knew Java SIG was having manpower issues because Mikolaj
> didn't know how to ask for help
You did not know that, but the situation in Java SIG is well known to
Jav
On Tue, Mar 12, 2019 at 1:36 PM Neal Gompa wrote:
> On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov
> wrote:
> >
> > On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
> domi...@greysector.net> wrote:
> >>
> >> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> >> >
On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov wrote:
>
> On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski
> wrote:
>>
>> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
>> > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
>> > >
>> > > Is there already a way
On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
> > >
> > > Is there already a way to package the java application as a module or
>
On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
> >
> > Is there already a way to package the java application as a module or
> > we will really remove all these package from Fedora?
>
> Most of Java packages listed in this thread
On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
>
> Is there already a way to package the java application as a module or
> we will really remove all these package from Fedora?
Most of Java packages listed in this thread are already packaged as
modules. Their retirement in rawhide won't direc
On 12. 03. 19 11:48, Jakub Jelen wrote:
Is there already a way to package the java application as a module or
we will really remove all these package from Fedora?
You can build Java apps as modules, yes.
If we remove the mentioned packages from rawhide, it will be the only way to
build Java pa
Is there already a way to package the java application as a module or
we will really remove all these package from Fedora?
I am really not interested in maintaining a whole java frameworks
stack, but some guidance (not these weekly emails) from java
maintainers team that took this decision would b
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
47 matches
Mail list logo
