On Tue, Apr 30, 2019 at 11:40:40AM +0200, Miro Hrončok wrote:
> On 30. 04. 19 11:35, Zbigniew Jędrzejewski-Szmek wrote:
> >On Mon, Apr 29, 2019 at 06:44:14PM +0200, Miro Hrončok wrote:
> >>PyMca orphan 4 weeks
> >>ago
> >Claimed in
On 30. 04. 19 11:35, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Apr 29, 2019 at 06:44:14PM +0200, Miro Hrončok wrote:
PyMca orphan 4 weeks ago
Claimed in https://pagure.io/releng/issue/8318.
See also https://bugz.fedoraproject.org/PyMca
On Mon, Apr 29, 2019 at 06:44:14PM +0200, Miro Hrončok wrote:
> PyMca orphan 4 weeks ago
Claimed in https://pagure.io/releng/issue/8318.
Zbyszek
___
devel mailing list --
On 29. 04. 19 18:44, Miro Hrončok wrote:
> jstanek: nodejs-formatio, nodejs-sinon, nodejs-lolex, nodejs-util,
> nodejs-samsam
Claimed: https://pagure.io/releng/issue/8317
--
Jan Staněk
Associate Software Engineer, Core Services
Red Hat Czech
jsta...@redhat.com IM: jstanek
signature.asc
Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
...
> Request package ownership via releng ticket:
> https://pagure.io/releng/issues
> lightdm-gtk cwickert, dbenoit, orphan, 3 weeks
https://pagure.io/releng/issue/8315
-- Rex
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
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
On Mon, Apr 29, 2019, 11:47 Jan Staněk wrote:
> On 27. 04. 19 10:51, Miro Hrončok wrote:
> > Zuzka, Jan, I've seen you requested soem nodejs packages recently. Would
> > you be able to take some more?
>
> If needed to keep them from orphaning, yes; but I cannot promise any
> really active
On 27. 04. 19 10:51, Miro Hrončok wrote:
> Zuzka, Jan, I've seen you requested soem nodejs packages recently. Would
> you be able to take some more?
If needed to keep them from orphaning, yes; but I cannot promise any
really active maintenance. The best I can promise is that I will *try*
to keep
On 27. 04. 19 9:29, Jan De Luyck wrote:
What's the status of those next to my name that my package notepadqq is
depending on?
(namely nodejs-archiver-utils, nodejs-crc32-stream,
nodejs-compress-commons, nodejs-tar-stream, nodejs-archiver, nodejs-zip-stream)
(I have little time at the moment
What's the status of those next to my name that my package notepadqq is
depending on?
(namely nodejs-archiver-utils, nodejs-crc32-stream,
nodejs-compress-commons, nodejs-tar-stream, nodejs-archiver,
nodejs-zip-stream)
(I have little time at the moment to keep track of packages - just
wondering,
On 26. 04. 19 16:24, Zuzana Svetlikova wrote:
> I'll take them.
Already mine (announced in the js-jquery orphaning thread) ;)
--
Jan Staněk
Associate Software Engineer, Core Services
Red Hat Czech
jsta...@redhat.com IM: jstanek
signature.asc
Description: OpenPGP digital signature
I'll take them.
On Tue, Apr 16, 2019 at 10:56 AM Miro Hrončok wrote:
> On 15. 04. 19 18:52, Christopher wrote:
> > If nobody picks up the ones by my name (nodejs-path-exists,
> > nodejs-bluebird, nodejs-grunt-known-options), then I will probably
> > have to orphan js-jquery, because it probably
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
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
On 15. 04. 19 18:52, Christopher wrote:
If nobody picks up the ones by my name (nodejs-path-exists,
nodejs-bluebird, nodejs-grunt-known-options), then I will probably
have to orphan js-jquery, because it probably needs those for its
build (I can't think of any other reason my name would be
On Mon, Apr 15, 2019 at 9:06 PM Stephen John Smoogen
wrote:
>
>
> On Mon, 15 Apr 2019 at 13:22, Ralf Corsepius wrote:
>
>> On 3/19/19 11:01 AM, Stelian Iancu wrote:
>> > On Tue, Mar 19, 2019 at 7:35 AM Emmanuel Seyman
>> wrote:
>> >>
>> >> * Sérgio Basto [19/03/2019 00:03] :
>> >>>
>> >>> I
On Mon, 15 Apr 2019 at 13:22, Ralf Corsepius wrote:
> On 3/19/19 11:01 AM, Stelian Iancu wrote:
> > On Tue, Mar 19, 2019 at 7:35 AM Emmanuel Seyman
> wrote:
> >>
> >> * Sérgio Basto [19/03/2019 00:03] :
> >>>
> >>> I though it was just one person which decide orphan his 259 packages
> >>
> >>
On 3/19/19 11:01 AM, Stelian Iancu wrote:
On Tue, Mar 19, 2019 at 7:35 AM Emmanuel Seyman wrote:
* Sérgio Basto [19/03/2019 00:03] :
I though it was just one person which decide orphan his 259 packages
Mikolaj is the last actif member of the Java SIG.
And who is guilty for this?
I
If nobody picks up the ones by my name (nodejs-path-exists,
nodejs-bluebird, nodejs-grunt-known-options), then I will probably
have to orphan js-jquery, because it probably needs those for its
build (I can't think of any other reason my name would be listed next
to those).
On Mon, Apr 15, 2019 at
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
On Mon, 15 Apr 2019 13:30:27 +0200
Miro Hrončok wrote:
astyleorphan 0 weeks ago
codeblocksorphan, sharkcz 0 weeks ago
I'll take over these - https://pagure.io/releng/issue/8283
Dan
Dne 15. 04. 19 v 13:30 Miro Hrončok napsal(a):
> rubygem-capybara mmorsi, orphan, ruby- 0
> weeks ago
> packagers-sig
> rubygem-childprocess ggillies, mmorsi, orphan, 0
> weeks ago
>
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
> Sorry, but I'm afraid I don't quite get this. Could you please rephrase?
> The script uses source repos to fetch build-dependencies.
Thanks. That answers my question.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
On Mon, Apr 8, 2019, 19:20 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:
>
On 09. 04. 19 0:03, Raphael Groner wrote:
Hopefully, it's sufficient to rebuild in rawhide only.
It is.
No idea why the original try to unbundle failed and your script cares about
other as just looking into really generated dependencies of binary rpm instead
of analysis done in spec file.
Hi Miro,
volumeicon should be fixed in rawhide.
It turns out that the BuildRequires line wasn't needed at all in
volumeicon.spec because upstream bundles partly its own copy of the needed
functions with code obviously copied from keybinder. Therefore I dropped this
BR and added a new Provides
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
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
On 02. 04. 19 8:41, Vít Ondruch wrote:
> Miro,
>
> Could you please also send a list of retired packages after you pull the
> trigger?
The information was included in my e-mail (I guess a bit hidden):
>> Packages already retired today:
>>SimplyHTML aether-connector-okhttp antlr3
Miro,
Could you please also send a list of retired packages after you pull the
trigger?
Thx
Vít
Dne 01. 04. 19 v 23:17 Miro Hrončok napsal(a):
> 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
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:
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:
I considered taking xcdroast but it needs to be patched to work with wodim
because it's only designed to be used with real cdrecord... Probably best
just to retire it. There are several other lightweight graphical CD/DVD
writer tools.
Thanks,
Richard
On Wed, 2019-03-27 at 18:48 +0100, Miro Hrončok wrote:
> On 27. 03. 19 18:18, Sérgio Basto wrote:
> > On Tue, 2019-03-26 at 11:08 +0100, Miro Hrončok wrote:
> > > sergiomb: nodejs-array-union
> >
> > why today ;) I'm associated to nodejs-array-union , seems to me
> > thescript have a bug ...
>
>
On 27. 03. 19 18:18, Sérgio Basto wrote:
On Tue, 2019-03-26 at 11:08 +0100, Miro Hrončok wrote:
sergiomb: nodejs-array-union
why today ;) I'm associated to nodejs-array-union , seems to me thescript have
a bug ...
What bug? Read the full report and grep your FAS name, follow the crumbs:
On Tue, 2019-03-26 at 11:08 +0100, Miro Hrončok wrote:
> sergiomb: nodejs-array-union
why today ;) I'm associated to nodejs-array-union , seems to me thescript have
a bug ...
Thanks,
--
Sérgio M. B.
___
devel mailing list --
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:
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:
On Tue, Mar 19, 2019 at 7:35 AM Emmanuel Seyman wrote:
>
> * Sérgio Basto [19/03/2019 00:03] :
> >
> > I though it was just one person which decide orphan his 259 packages
>
> Mikolaj is the last actif member of the Java SIG.
>
I think the bigger question here is what is going to happen with the
* Sérgio Basto [19/03/2019 00:03] :
>
> I though it was just one person which decide orphan his 259 packages
Mikolaj is the last actif member of the Java SIG.
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
On Mon, 2019-03-18 at 19:06 -0400, Gerald Henriksen wrote:
> On Mon, 18 Mar 2019 15:45:49 +, you wrote:
>
> >
> > After thinking , my suggestion is do not retire any java package.
> >
> > These package should be take by java sig .
>
> That's nice, who exactly is this Java sig you have
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, 18 Mar 2019 15:45:49 +, you wrote:
>
>After thinking , my suggestion is do not retire any java package.
>
>These package should be take by java sig .
That's nice, who exactly is this Java sig you have kindly decided
should take on this significant undertaking?
My (limited)
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
ct.org, Development discussions
related to Fedora
Subject: Orphaned packages to be retired (Java packages in 2 weeks)
Date: Mon, 18 Mar 2019 12:55:11 +0100
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know fo
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
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
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
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
* 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
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
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
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
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".
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
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
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
* 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,
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
* 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
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
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
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,
> > >
* 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
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:
t; >> > non-event for everyone concerned except you. Instead of helping with
> >> > that (or just waiting), you are about to cause the retirement of
> quite a
> >> > few packages whose maintainers want nothing to do with Modularity.
> >> > That's not e
g with
> that (or just waiting), you are about to cause the retirement of quite a
> few packages whose maintainers want nothing to do with Modularity.
> That's not excellent.
I am not forcing anyone to do anything. If I followed your thinking
then I colud say that by not adopting orphaned pa
-event for everyone concerned except you. Instead of helping with
> > that (or just waiting), you are about to cause the retirement of quite a
> > few packages whose maintainers want nothing to do with Modularity.
> > That's not excellent.
>
> I am not forcing anyone to do
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
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
ose maintainers want nothing to do with Modularity.
> That's not excellent.
I am not forcing anyone to do anything. If I followed your thinking
then I colud say that by not adopting orphaned packages you are
forcing others to do the same things you accuse me of forcing people
to.
&
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
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
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
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
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
>
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 <
> >
not orphan that many packages. I orphaned about 250 packages only.
>
Sorry, you're right, it affects nearly that many though.
> It is not too late for anything. Orphaned packages can still be
> adopted. That's the whole point of this thread.
>
> > We could have avoided the bad ending if at
he orphaned nearly 1700 packages to force
> modularization
I did not orphan that many packages. I orphaned about 250 packages only.
It is not too late for anything. Orphaned packages can still be
adopted. That's the whole point of this thread.
> We could have avoided the bad endi
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
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
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
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
On Thu, Feb 28, 2019 at 5:03 PM Alexander Bokovoy wrote:
>
> On to, 28 helmi 2019, Stephen John Smoogen wrote:
> >On Thu, 28 Feb 2019 at 06:11, Ingo Hoffmann wrote:
> >>
> >> Hi,
> >>
> >> First time here and concerned Java citizen. Who or how can I contact
> >> regarding the maven package
On to, 28 helmi 2019, Stephen John Smoogen wrote:
On Thu, 28 Feb 2019 at 06:11, Ingo Hoffmann wrote:
Hi,
First time here and concerned Java citizen. Who or how can I contact regarding
the maven package maintenance? I want to either maintain or co-maintain it if
there's someone already
On Thu, 28 Feb 2019 at 06:11, Ingo Hoffmann wrote:
>
> Hi,
>
> First time here and concerned Java citizen. Who or how can I contact
> regarding the maven package maintenance? I want to either maintain or
> co-maintain it if there's someone already doing it.
>
Note there are 2 different
On Thu, Feb 28, 2019 at 1:00 PM Stephen John Smoogen wrote:
> To try and make this clearer: The script is looking for chains of
> orphans. If X is orphaned and your package currently (build)requires
> it.. your package will be affected when it gets dropped. Either you
> have to help someone take
On Wed, 27 Feb 2019 at 14:35, Miro Hrončok wrote:
>
>
>
> On 27. 02. 19 15:34, Robert-André Mauchin wrote:
> > On lundi 25 février 2019 21:49:32 CET you wrote:
> >> The following packages are orphaned and will be retired when they
> >> are orphaned for six weeks, unless someone adopts them. If
1201 - 1300 of 2415 matches
Mail list logo
