Re: Orphaned packages that will be retired (and everything will most likely burn)

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

Re: Orphaned packages that will be retired (and everything will most likely burn)

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

Re: Orphaned packages that will be retired (and everything will most likely burn)

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

Re: Orphaned packages that will be retired

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

Re: Orphaned packages that will be retired

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 s

Re: Orphaned packages that will be retired (and everything will most likely burn)

Hi, I submitted a ticket to take over the maven package, https://pagure.io/releng/issue/8179. -- Ingo ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: Orphaned packages that will be retired (and everything will most likely burn)

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. Regards, Ingo ___ devel mailing list --

Re: Orphaned packages that will be retired

On 28. 02. 19 11:50, Paolo Bonzini wrote: On 25/02/19 21:49, Miro Hrončok wrote: bonzini: plexus-utils I have no idea what this is and how I became the maintainer. :) Grep the full https://churchyard.fedorapeople.org/orphans-2019-02-25.txt report for your FAS name. qemu (maintained by:

Re: Orphaned packages that will be retired

On 25/02/19 21:49, Miro Hrončok wrote: > bonzini: plexus-utils I have no idea what this is and how I became the maintainer. :) Paolo ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Orphaned packages that will be retired

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 you know for sure that the package should be retired, please do so now

Re: Orphaned packages that will be retired

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 you know for sure > that the package should be retired, please do so now with a proper reason

Re: Orphaned packages that will be retired

On Mon, Feb 25, 2019 at 9:51 PM 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 rea

Re: Orphaned packages that will be retired

On Mon, 2019-02-25 at 21:49 +0100, Miro Hrončok wrote: > Note: If you received this mail directly you (co)maintain one of the affected > packages or a package that depends on one. Please adopt the affected package > or > retire your depending package to avoid broken dependencies, otherwise your

Re: Orphaned packages that will be retired (and everything will most likely burn)

Dne 20. 02. 19 v 10:02 Till Maas napsal(a): > On Fri, Feb 15, 2019 at 04:28:17PM +0100, Vít Ondruch wrote: >> Dne 15. 02. 19 v 14:22 Emmanuel Seyman napsal(a): >>> * Hans de Goede [15/02/2019 12:09] : And automatic scripts really just should hand it over to the first co-maintainer

Orphaned packages that will be retired

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

Orphaned packages that will be retired

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

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Fri, Feb 15, 2019 at 04:28:17PM +0100, Vít Ondruch wrote: > > Dne 15. 02. 19 v 14:22 Emmanuel Seyman napsal(a): > > * Hans de Goede [15/02/2019 12:09] : > >> And automatic scripts really just should hand it over to the first > >> co-maintainer > >> in the list. > > > As long as we have no

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Fri, Feb 15, 2019 at 11:30 PM Vít Ondruch wrote: > As long as we have no idea if the other maintainers are active, I am > strongly against the automation. I've been there. Followed nor > responsive policy just to find out later that instead of orphaning the > package, next inactive maintainer

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 11. 02. 19 17:57, 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

Re: Orphaned packages that will be retired (and everything will most likely burn)

Dne 15. 02. 19 v 14:22 Emmanuel Seyman napsal(a): > * Hans de Goede [15/02/2019 12:09] : >> And automatic scripts really just should hand it over to the first >> co-maintainer >> in the list. As long as we have no idea if the other maintainers are active, I am strongly against the automation.

Re: Orphaned packages that will be retired (and everything will most likely burn)

* Hans de Goede [15/02/2019 12:09] : > > And automatic scripts really just should hand it over to the first > co-maintainer > in the list. This inspires two observations (which I'm sure you already know). * There's no such thing as "the first co-maintainer" There are co-maintainers and they

Re: Orphaned packages that will be retired (and everything will most likely burn)

Hi, On 15-02-19 12:51, Mikolaj Izdebski wrote: On Fri, Feb 15, 2019 at 12:11 PM Hans de Goede wrote: I will take sdljava as bolzplatz relies on it. I do not know how / why this was orphaned. This package has 2 other admin's in the user/group settings. If this was done automatically it would

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Fri, Feb 15, 2019 at 12:11 PM Hans de Goede wrote: > I will take sdljava as bolzplatz relies on it. > > I do not know how / why this was orphaned. This package has > 2 other admin's in the user/group settings. If this was done > automatically it would be nice if we could change the automatic >

Re: Orphaned packages that will be retired (and everything will most likely burn)

I'll take over zopfli. Miro Hrončok writes: > 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://fedor

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 13/02/19 14:31, Richard W.M. Jones wrote: > Isn't the assembler syntax different or does gas now support > the nasm syntax (and macros plus a bunch of other stuff AIUI)? > If we require gas then I assume a whole bunch of asm would have > to be rewritten ... Indeed, for example edk2 used to

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Wed, Feb 13, 2019 at 11:30:43AM +, Nick Clifton wrote: > Hi Paolo, > > > I can maintain nasm if no one else wants to take it. > > Please do, if that it what you want. However I think that it > might be better in the long run if we can retire nasm (and yasm > too) and instead replace them

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Wednesday, 13 February 2019 at 12:30, Nick Clifton wrote: > Hi Paolo, > > > I can maintain nasm if no one else wants to take it. > > Please do, if that it what you want. However I think that it > might be better in the long run if we can retire nasm (and yasm > too) and instead replace them

Re: Orphaned packages that will be retired (and everything will most likely burn)

Hi Paolo, > I can maintain nasm if no one else wants to take it. Please do, if that it what you want. However I think that it might be better in the long run if we can retire nasm (and yasm too) and instead replace them with gas. Cheers Nick PS. In case there is someone reading this

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Monday, 11 February 2019 at 18:12, Paolo Bonzini wrote: > On 11/02/19 17:57, 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 th

Re: Orphaned packages that will be retired (and everything will most likely burn)

Le 2019-02-12 11:43, Adam Samalik a écrit : I might be missing something here, so excuse me if that's obvious, but wouldn't this happen without Modularity anyway? I mean, how does Modularity relate to packages being orphaned? Or is that because they have been moved out into modules and their

Re: Orphaned packages that will be retired (and everything will most likely burn)

It won't help because you didn't take the build dependencies of ant/maven… On Tue, Feb 12, 2019 at 12:51 PM Fabio Valentini wrote: > On Tue, Feb 12, 2019 at 12:16 PM Fabio Valentini > wrote: > > > > On Tue, Feb 12, 2019 at 12:08 PM Miro Hrončok > wrote: > > > > > > On 12. 02. 19 11:46, Fabio

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12/02/2019 11:46, Mikolaj Izdebski wrote: On Tue, Feb 12, 2019 at 11:56 AM Tom Hughes wrote: Java and everything java related (like ant) is now modular only and has been orphaned in the non-modular rawhide. That's totally not true. There are about 1.4k source Java packages, but there are

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 11:56 AM Tom Hughes wrote: > Java and everything java related (like ant) is now modular only > and has been orphaned in the non-modular rawhide. That's totally not true. There are about 1.4k source Java packages, but there are less that 200 modular Java source packages.

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 12:16 PM Fabio Valentini wrote: > > On Tue, Feb 12, 2019 at 12:08 PM Miro Hrončok wrote: > > > > On 12. 02. 19 11:46, Fabio Valentini wrote: > > >> (I know anyone can unbreak it by claiming the packages, but that's not > > >> the point > > >> here.) > > > > > > Miro, am

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 12:08 PM Miro Hrončok wrote: > > On 12. 02. 19 11:46, Fabio Valentini wrote: > >> (I know anyone can unbreak it by claiming the packages, but that's not the > >> point > >> here.) > > > > Miro, am I reading it correctly that the list below "Orphans (rawhide) > > (not

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 11:54 AM Tom Hughes wrote: > On 12/02/2019 10:43, Adam Samalik wrote: > > > I might be missing something here, so excuse me if that's obvious, but > > wouldn't this happen without Modularity anyway? I mean, how does > > Modularity relate to packages being orphaned? Or is

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12. 02. 19 11:46, Fabio Valentini wrote: (I know anyone can unbreak it by claiming the packages, but that's not the point here.) Miro, am I reading it correctly that the list below "Orphans (rawhide) (not depended on) (147):" is the list of orphan leaf packages? Yes. Also, if somebody

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12/02/2019 10:43, Adam Samalik wrote: I might be missing something here, so excuse me if that's obvious, but wouldn't this happen without Modularity anyway? I mean, how does Modularity relate to packages being orphaned? Or is that because they have been moved out into modules and their

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12. 02. 19 11:43, Adam Samalik wrote:> (I know anyone can unbreak it by claiming the packages, but that's not the point here.) I might be missing something here, so excuse me if that's obvious, but wouldn't this happen without Modularity anyway? I mean, how does Modularity

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 11:03 AM Miro Hrončok wrote: > > On 12. 02. 19 10:47, Brian (bex) Exelbierd wrote: > > > > > > On Tue, Feb 12, 2019 at 10:17 AM Tom Hughes > > wrote: > > > > So basically the module squad have managed to ensure that everything > > that

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 11:03 AM Miro Hrončok wrote: > On 12. 02. 19 10:47, Brian (bex) Exelbierd wrote: > > > > > > On Tue, Feb 12, 2019 at 10:17 AM Tom Hughes > > wrote: > > > > So basically the module squad have managed to ensure that everything > > that

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12. 02. 19 10:47, Brian (bex) Exelbierd wrote: On Tue, Feb 12, 2019 at 10:17 AM Tom Hughes > wrote: So basically the module squad have managed to ensure that everything that relies on ant to build is going to have to modularise or else be forced out of

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 10:17 AM Tom Hughes wrote: > So basically the module squad have managed to ensure that everything > that relies on ant to build is going to have to modularise or else be > forced out of the distribution then... > > Fortunately that only includes one thing of mine and

Re: Orphaned packages that will be retired (and everything will most likely burn)

Le 2019-02-12 10:21, Emmanuel Seyman a écrit : * Tom Hughes [12/02/2019 09:15] : So basically the module squad have managed to ensure that everything that relies on ant to build is going to have to modularise or else be forced out of the distribution then... Once more with feeling: if you

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12/02/2019 09:21, Emmanuel Seyman wrote: * Tom Hughes [12/02/2019 09:15] : So basically the module squad have managed to ensure that everything that relies on ant to build is going to have to modularise or else be forced out of the distribution then... Once more with feeling: if you want

Re: Orphaned packages that will be retired (and everything will most likely burn)

* Tom Hughes [12/02/2019 09:15] : > > So basically the module squad have managed to ensure that everything > that relies on ant to build is going to have to modularise or else be > forced out of the distribution then... Once more with feeling: if you want ant as a package, all that is needed to

Re: Orphaned packages that will be retired (and everything will most likely burn)

So basically the module squad have managed to ensure that everything that relies on ant to build is going to have to modularise or else be forced out of the distribution then... Fortunately that only includes one thing of mine and that's just some java bindings that I can drop but forcing

Re: Orphaned packages that will be retired (and everything will most likely burn)

Not in the buildroot. Default modules are available by default only for users and not in the buildroot. On Tue, Feb 12, 2019 at 10:01 AM Tom Hughes wrote: > On 12/02/2019 07:22, Mikolaj Izdebski wrote: > > On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini > wrote: > >> I'm curious: What happens

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 12/02/2019 07:22, Mikolaj Izdebski wrote: On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote: I'm curious: What happens to modules when a package's master branch gets retired? Nothing. Modules will continue to exist and will continue to be delivered to users. But as I understand it

Re: Orphaned packages that will be retired (and everything will most likely burn)

I was talking to Petr Šabata some time ago and he told me that there will be some solution for getting modular packages in non-modular buildroot within month or two. On Tue, Feb 12, 2019 at 9:06 AM Aleksandar Kurtakov wrote: > > > On Tue, Feb 12, 2019 at 9:51 AM Ralf Corsepius > wrote: > >> On

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 9:51 AM Ralf Corsepius wrote: > On 2/12/19 8:22 AM, Mikolaj Izdebski wrote: > > On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini > wrote: > >> I'm curious: What happens to modules when a package's master branch > >> gets retired? > > > > Nothing. Modules will continue to

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 2/12/19 8:22 AM, Mikolaj Izdebski wrote: On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote: I'm curious: What happens to modules when a package's master branch gets retired? Nothing. Modules will continue to exist and will continue to be delivered to users. Actually, I consider ant

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote: > I'm curious: What happens to modules when a package's master branch > gets retired? Nothing. Modules will continue to exist and will continue to be delivered to users. -- Mikolaj Izdebski ___

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 11/02/19 17:57, 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://fedorap

Re: Orphaned packages that will be retired (and everything will most likely burn)

I don't think you can generate graph... Because how would you display "Requires: (foo if bar)"? :) On Mon, Feb 11, 2019 at 6:11 PM Adam Williamson wrote: > On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: > > The following packages require above mentioned packages: > > (this is in fact so

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 11/02/2019 17:02, Adam Williamson wrote: On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: The following packages require above mentioned packages: (this is in fact so long that I've posted it to https://churchyard.fedorapeople.org/orphans-2019-02-11.txt) It would be rather handy to

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: > The following packages require above mentioned packages: > (this is in fact so long that I've posted it to > https://churchyard.fedorapeople.org/orphans-2019-02-11.txt) It would be rather handy to get some sort of graph view, especially