On 05. 08. 19 14:02, Mikolaj Izdebski wrote:
gradle-local package can't be removed yet because other packages
depend on it. Removing dependency involves porting packages from
Gradle to Maven, which can only be done by package maintainers.
However most of Java package maintainers are not really
On Mon, Aug 5, 2019 at 1:50 PM Hans de Goede wrote:
>
> Hi Fabio,
>
> On 05-08-19 13:37, Fabio Valentini wrote:
> > On Mon, Aug 5, 2019 at 1:15 PM Mikolaj Izdebski wrote:
> >>
> >> On Mon, Aug 5, 2019 at 12:07 PM Hans de Goede wrote:
> >>> In the extended version:
> >>>
Hi Fabio,
On 05-08-19 13:37, Fabio Valentini wrote:
On Mon, Aug 5, 2019 at 1:15 PM Mikolaj Izdebski wrote:
On Mon, Aug 5, 2019 at 12:07 PM Hans de Goede wrote:
In the extended version:
https://churchyard.fedorapeople.org/orphans-2019-08-05.txt
I see that javapackages-tools is still on the
On Mon, Aug 5, 2019 at 1:15 PM Mikolaj Izdebski wrote:
>
> On Mon, Aug 5, 2019 at 12:07 PM Hans de Goede wrote:
> > In the extended version:
> > https://churchyard.fedorapeople.org/orphans-2019-08-05.txt
> > I see that javapackages-tools is still on the list (because it depends on
> > gradle)
On Mon, Aug 5, 2019 at 12:07 PM Hans de Goede wrote:
> In the extended version:
> https://churchyard.fedorapeople.org/orphans-2019-08-05.txt
> I see that javapackages-tools is still on the list (because it depends on
> gradle)
> and that in turn brings problems for lot of other packages.
>
> So
On 05. 08. 19 12:07, Hans de Goede wrote:
Hi all,
On 05-08-19 11:52, 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
Hi all,
On 05-08-19 11:52, 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 Tue, 30 Jul 2019 at 18:28, Christopher
wrote:
>
> On Tue, Jul 30, 2019 at 1:10 PM Alexander Scheel
wrote:
> [snip]
> > The Java SIG is here:
> >
> > - https://fedoraproject.org/wiki/SIGs/Java
>
> Is there anything special one must do to "Join" the Java SIG? I would
> like to join.
No, it
* Christopher [30/07/2019 13:20] :
>
> Is there anything special one must do to "Join" the Java SIG? I would
> like to join.
SIGs are rather informal and none of them have a joining
procedure that I know of.
You should subscribe to the mailing list, introduce yourself and
request any commit
On 30. 07. 19 21:53, Dave Dykstra wrote:
I don't see an answer to Jan's question about "javaewah" and think it
might have gotten buried in the thread, so I'd like to say -- I have
this question too. It seems something went wrong with the script that
generated the list.
Sorry, I've
- Original Message -
> From: "Dave Dykstra"
> To: "Alexander Scheel"
> Cc: "Jan Pazdziora" , "Development discussions related
> to Fedora"
>
> Sent: Tuesday, July 30, 2019 4:45:06 PM
> Subject: Re: "javaewah" (w
y disabled to help clean up the orphaned
packages report.
So, as soon as the orphaned packages report is updated to reflect
that, you should no longer be listed as affected - at least not
affected by jgit.
Fabio
> Dave
>
>
> On Tue, Jul 30, 2019 at 04:02:12PM -0400, Alexander Scheel wr
gt;
> > Cc: "Jan Pazdziora"
> > Sent: Tuesday, July 30, 2019 3:53:37 PM
> > Subject: "javaewah" (was Re: Over 500 orphaned packages seeking new
> > maintainers)
> >
> > I don't see an answer to Jan's question about "javaewah" and t
- Original Message -
> From: "Dave Dykstra"
> To: "Development discussions related to Fedora"
>
> Cc: "Jan Pazdziora"
> Sent: Tuesday, July 30, 2019 3:53:37 PM
> Subject: "javaewah" (was Re: Over 500 orphaned packages seeki
I don't see an answer to Jan's question about "javaewah" and think it
might have gotten buried in the thread, so I'd like to say -- I have
this question too. It seems something went wrong with the script that
generated the list.
Dave
On Mon, Jul 29, 2019 at 01:02:28PM +0200, Jan Pazdziora
On Tue, Jul 30, 2019 at 1:10 PM Alexander Scheel wrote:
[snip]
> The Java SIG is here:
>
> - https://fedoraproject.org/wiki/SIGs/Java
Is there anything special one must do to "Join" the Java SIG? I would
like to join.
___
devel mailing list --
On Tue, Jul 30, 2019 at 12:07 PM Stephen John Smoogen wrote:
[SNIP]
> The issue is that no one has time to take ownership of these packages. The
> whole premise around Fedora's package model for the last 15 years is that the
> number of packagers and the number of packages linearly grew. You
> Where this fails is where there's duplication of efforts. Take slf4j as an
> example. mizdebsk maintains it in one of his various modules (it looks like
> the javapackages module). We maintain it in the SIG as an ursine package so
> things like Dogtag and a lot of other things don't break. When
- Original Message -
> From: "Stephen John Smoogen"
> To: "Development discussions related to Fedora"
>
> Cc: "Dinesh Prasanth Moluguwan Krishnamoorthy"
> Sent: Tuesday, July 30, 2019 12:05:59 PM
> Subject: Re: Over 500 orphaned pack
ted to Fedora" <
>> devel@lists.fedoraproject.org>
>> > Cc: "Fabio Valentini"
>> > Sent: Monday, July 29, 2019 6:14:57 PM
>> > Subject: Re: Over 500 orphaned packages seeking new maintainers
>> >
>> > On Mon, Jul 29, 2019 at 5:36
> > Sent: Monday, July 29, 2019 6:14:57 PM
> > Subject: Re: Over 500 orphaned packages seeking new maintainers
> >
> > On Mon, Jul 29, 2019 at 5:36 PM Alexander Scheel
> wrote:
> > >
> > > > Question (not for Fabio specifically, but for the list) mo
- Original Message -
> From: "Christopher"
> To: "Development discussions related to Fedora"
>
> Cc: "Fabio Valentini"
> Sent: Monday, July 29, 2019 6:14:57 PM
> Subject: Re: Over 500 orphaned packages seeking new maintainers
>
On 30. 07. 19 12:41, Hans de Goede wrote:
Hmm:
[hans@shalem master]$ sudo dnf repoquery --whatrequires javapackages-filesystem | wc -l
3514
There are some doubles in here, due to multi-arch and updates, this includes things like:
java-1.8.0-openjdk-headless
Ouch, I do not see these
Hi,
On 30-07-19 12:29, Hans de Goede wrote:
2) Remove the obsolete jpackage-utils stuff, which no longer is part of:
https://fedoraproject.org/wiki/Packaging:Java
From:
cortado
sdljava
vecmath1.2
freecol
bolzplatz2006
And keep them in the main Fedora repos
Except that the guidelines say
Hi,
On 29-07-19 23:35, Alexander Scheel wrote:
The reason I'm confused is because AFAIK last time jpackage-utils /
javapackages-tools also was part of the set of
packages causingproblems and javapackages-tools was picked up by the
Stewardship SIG (or so I believe) so I'm
surprised to see it go
On Mon, Jul 29, 2019 at 05:14:38PM -0700, Kevin Fenzi wrote:
> On 7/27/19 11:53 AM, Hans de Goede wrote:
> > On 26-07-19 18:25, Kevin Fenzi wrote:
> >> On 7/26/19 4:25 AM, Hans de Goede wrote:
> >>> 2) Make taking over the package a 1 click action
> >>
> >> There's work to get this happening...
>
On 7/27/19 11:53 AM, Hans de Goede wrote:
> Hi,
>
> On 26-07-19 18:25, Kevin Fenzi wrote:
>> On 7/26/19 4:25 AM, Hans de Goede wrote:
>>
>>> 1) Have some automated process automatically email co-maintainers
>>> when the
>>> primary maintainer orphan the package.
>>
>> That should already be the
On 7/26/19 10:39 AM, Emmanuel Seyman wrote:
> * Kevin Fenzi [26/07/2019 09:25] :
>>
>> That said, we could:
>> * make a bugzilla user for every package named
>> 'packagename-ow...@fedoraproject.org'
>> * assign bugs for that package to that user (no ccs)
>
> Please don't do this.
>
> The best
On Mon, Jul 29, 2019 at 5:36 PM Alexander Scheel wrote:
>
> > Question (not for Fabio specifically, but for the list) modules can have
> > (Build)Requires on other modules
> > right?
>
> Yes, if the module maintainer is willing to expose their module in the
> BUILDROOT. That was PKI's problem:
> The reason I'm confused is because AFAIK last time jpackage-utils /
> javapackages-tools also was part of the set of
> packages causingproblems and javapackages-tools was picked up by the
> Stewardship SIG (or so I believe) so I'm
> surprised to see it go away again now.
One of the SIG's 3
Hi,
On 29-07-19 16:59, Fabio Valentini wrote:
On Mon, Jul 29, 2019, 16:40 Miro Hrončok mailto:mhron...@redhat.com>> wrote:
On 29. 07. 19 16:35, Hans de Goede wrote:
> Hi,
>
> On 29-07-19 12:37, Miro Hrončok wrote:
>> The following packages are orphaned and will be
Miro Hrončok wrote:
> Note that jgit is not (yet) orphaned nor retired, and its dependencies might
> be picked up by somebody. I suggest to remove the dep in rawhide temporarily
> (to make the next weeks reports more readable and shorter to calculate (the
> present one took 2 days)). Once the dust
On Mon, Jul 29, 2019, 16:40 Miro Hrončok wrote:
> On 29. 07. 19 16:35, Hans de Goede wrote:
> > Hi,
> >
> > On 29-07-19 12:37, 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
>
On 29. 07. 19 16:44, Todd Zullinger wrote:
Hi,
Pavel Cahyna wrote:
On Mon, Jul 29, 2019 at 12:59:22PM +0200, Miro Hrončok wrote:
On 29. 07. 19 12:37, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them.
Hi,
Pavel Cahyna wrote:
> On Mon, Jul 29, 2019 at 12:59:22PM +0200, Miro Hrončok wrote:
>> On 29. 07. 19 12:37, 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
On 29. 07. 19 16:35, Hans de Goede wrote:
Hi,
On 29-07-19 12:37, 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
Hi,
On 29-07-19 12:37, 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 Mon, Jul 29, 2019 at 12:37:33PM +0200, 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 Mon, Jul 29, 2019 at 12:59:22PM +0200, Miro Hrončok wrote:
> On 29. 07. 19 12:37, 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,
On 29. 07. 19 12:37, 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:
Hi,
On 26-07-19 18:25, Kevin Fenzi wrote:
On 7/26/19 4:25 AM, Hans de Goede wrote:
1) Have some automated process automatically email co-maintainers when the
primary maintainer orphan the package.
That should already be the case? FMN should mail you... perhaps this
isn't working?
If this
* Kevin Fenzi [26/07/2019 09:25] :
>
> That said, we could:
> * make a bugzilla user for every package named
> 'packagename-ow...@fedoraproject.org'
> * assign bugs for that package to that user (no ccs)
Please don't do this.
The best feature the system we currently use has is accountability.
On Fri, Jul 26, 2019 at 09:25:54AM -0700, Kevin Fenzi wrote:
> On 7/26/19 4:25 AM, Hans de Goede wrote:
> > Proposal to really fix this. We often say that people should not feel they
> > own a package, but that this is all a team effort, hence we also promote
> > co-maintainer ship, so I propose
;> 2) Only orphan a package when the maintainer count drops to 0.
> If we come up with a way to deal with bugzilla, sure.
What is the issue here? Orphaned packages are owned by orphaned-extras user.
Anyway, I don't like the automatic handover idea. That way the package
might be given from o
On 7/26/19 4:25 AM, Hans de Goede wrote:
> 1) Have some automated process automatically email co-maintainers when the
> primary maintainer orphan the package.
That should already be the case? FMN should mail you... perhaps this
isn't working?
> 2) Make taking over the package a 1 click action
On Fri, Jul 26, 2019 at 04:13:50PM +0100, Peter Robinson wrote:
> On Fri, Jul 26, 2019 at 1:14 PM Hans de Goede wrote:
> > Can we please stop this gargantuan time waste? Proposal to make this
> > less painful:
> >
> > 1) Have some automated process automatically email co-maintainers when the
> >
On Fri, Jul 26, 2019 at 1:14 PM Hans de Goede wrote:
>
> Hi,
>
> On 22-07-19 10:47, 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,
Hi,
On 22-07-19 10:47, 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:
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
Note that javapackages-tools provides jpackage-utils, so apparantly some of
these reports are wrong. But it might be a good idea to update the requires
instead of considering this a virtual (feature) provide.
___
devel mailing list --
On Mon, Jul 22, 2019 at 12:33 PM Richard W.M. Jones wrote:
>
> On Mon, Jul 22, 2019 at 10:47:10AM +0200, Miro Hrončok wrote:
> > See this report online at:
> > https://churchyard.fedorapeople.org/orphans-2019-07-22.txt
>
> Since the majority of new failures (394!) are caused by the orphaning
> of
On Mon, Jul 22, 2019 at 10:47:10AM +0200, Miro Hrončok wrote:
> See this report online at:
> https://churchyard.fedorapeople.org/orphans-2019-07-22.txt
Since the majority of new failures (394!) are caused by the orphaning
of google-oauth-java-client, I looked at the full report and seems
this is
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, Jul 8, 2019 at 5:35 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 reason:
>
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, Jul 1, 2019 at 4:02 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 reason:
>
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
Hi,
I can take python-pdfkit. Because business as usual.
Upstream is active and there's a new version provided on PyPi. No idea why this
package is orphaned.
Regards, Raphael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
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
I will take exaile.
https://pagure.io/releng/issue/8459
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Hi,
I'll also take python-email_reply_parser. It's actively developed by
upstream.
Regards, Raphael
Am 17.06.19 um 21:14 schrieb Miro Hrončok:
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
Hi Miro,
I can take csvdiff. It has official support for Python 3.7:
https://github.com/larsyencken/csvdiff/blob/163dd9da676a8e5f926a935803726340261f03ae/setup.py#L55
Regards, Raphael
Am 17.06.19 um 21:14 schrieb Miro Hrončok:
The following packages are orphaned and will be retired when
> python-num2words orphan 0 weeks ago
I have requested ownership of this for the neuro-sig.
https://pagure.io/releng/issue/8450
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone:
El lun., 17 jun. 2019 a las 21:15, Miro Hrončok
() escribió:
> gpart dcantrel, orphan 6 weeks ago
I'll take gpart, is a lifesaver :-)
https://pagure.io/releng/issue/8447
--
Francisco J. Tsao Santín
https://gattaca.es
Twitter: @FranTsao
1024D/71CF4D62
Dne 17. 06. 19 v 21:14 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
> that the package should be retired, please do so now with a proper
> reason:
>
On 17. 06. 19 21:27, Luis Enrique Bazán De León wrote:
Hi Miro
Can I work on this python-slugify
Sure, request package ownership via: https://pagure.io/releng/issues
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: If
Hi Miro
Can I work on this python-slugify
FAS lbazan
Cheers,
El lun., 17 jun. 2019 a las 14:14, Miro Hrončok ()
escribió:
> 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
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, Jun 11, 2019 10:24:21 +0200, Miro Hrončok wrote:
> > On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
>
> > Still, since I don't know how it's done, what command does one use to
> > find these (and the reverse mappings) too please?
>
> That's a bit tedious. But you can follow the
On 11. 06. 19 10:24, Miro Hrončok wrote:
On 11. 06. 19 10:02, Ankur Sinha wrote:
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> neuro-sig: jboss-jms-1.1-api, gsl
How would I ascertain which one of the neuro-sig packages requires this
jboss package?
$ sudo dnf repoquery
On 11. 06. 19 10:02, Ankur Sinha wrote:
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> neuro-sig: jboss-jms-1.1-api, gsl
How would I ascertain which one of the neuro-sig packages requires this
jboss package?
$ sudo dnf repoquery --recursive --whatrequires jboss-jms-1.1-api
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> > > neuro-sig: jboss-jms-1.1-api, gsl
>
>
> How would I ascertain which one of the neuro-sig packages requires this
> jboss package?
>
> $ sudo dnf repoquery --recursive --whatrequires jboss-jms-1.1-api
>
Hello,
On Mon, Jun 10, 2019 21:28:55 +0100, Mat Booth wrote:
> On Mon, 10 Jun 2019 at 18:59, Fabio Valentini wrote:
>
> Hi Miro,
>
> I will request these for the stewardship SIG:
>
> jboss-websocket-1.0-api, weld-parent, jboss-jms-1.1-api,
> jboss-connector-1.7-api,
Miro Hrončok writes:
> the-new-hotness orphan1 weeks ago
This looks scary, isn't this needed to actually run the-new-hotness? If
yes, I'll take it.
signature.asc
Description: PGP signature
___
devel
> > lupinix: checkstyle, gsl
> >
>
> I requested ownership for gsl: https://pagure.io/releng/issue/8429
>
Thanks Christian.
Some scientific tools also depend on gsl, so the neuro-sig will be happy
to help out with it too. Please feel free to give "neuro-sig" commit
rights if you'd like.
--
On Mon, 10 Jun 2019 at 18:59, Fabio Valentini wrote:
> Hi Miro,
>
> I will request these for the stewardship SIG:
>
> jboss-websocket-1.0-api, weld-parent, jboss-jms-1.1-api,
> jboss-connector-1.7-api, jboss-marshalling, jboss-el-2.2-api,
> jboss-jsp-2.3-api,
> felix-osgi-obr-resolver, jline1,
On 10. 06. 19 19:58, Fabio Valentini wrote:
Hi Miro,
I will request these for the stewardship SIG:
jboss-websocket-1.0-api, weld-parent, jboss-jms-1.1-api,
jboss-connector-1.7-api, jboss-marshalling, jboss-el-2.2-api, jboss-jsp-2.3-api,
felix-osgi-obr-resolver, jline1, jboss-jsf-2.1-api, emma,
Hi Miro,
I will request these for the stewardship SIG:
jboss-websocket-1.0-api, weld-parent, jboss-jms-1.1-api,
jboss-connector-1.7-api, jboss-marshalling, jboss-el-2.2-api, jboss-jsp-2.3-api,
felix-osgi-obr-resolver, jline1, jboss-jsf-2.1-api, emma, jboss-jstl-1.2-api,
jboss-servlet-3.0-api,
On 10/06/2019 19:22, 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:
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 03. 06. 19 17:41, Richard W.M. Jones wrote:
A lot of packages that I care about depend on mtools, but
I see no announcement of mtools being orphaned ...
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JYV6PAJEDO5OXOLD3ZBXN3WEYGFMUJ76/
--
Miro Hrončok
--
On 03/06/19 16:18, Miro Hrončok wrote:
>
> ipxe (maintained by: berrange, bonzini, crobinso, virtmaint-sig)
> ipxe-20190125-1.git36a4c85f.fc30.src requires mtools =
> 4.0.18-16.fc30, syslinux = 6.04-0.8.fc28
I'll take a look at removing the dependency.
Paolo
A lot of packages that I care about depend on mtools, but
I see no announcement of mtools being orphaned ...
> Depending on: mtools (21), status change: 2019-05-31 (0 weeks ago)
> gnome-boxes (maintained by: elmarco, feborges, fidencio, gnome-sig,
> teuf, zeenix)
>
I'll submit a request to have apache-commons-discovery un-orphaned again.
Fabio
On Mon, Jun 3, 2019, 16:19 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
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
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
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
ure that the package should be retired, please do so now with a
> > proper
> > reason:
> >
> > Orphaned packages:
> >
> > ladspa-swh-plugins orphan 59 weeks ago
>
> Hi. Somehow I missed this email from November, perhaps because I was
> not a co-maintainer.
>
On Fri, 30 Nov 2018 at 13:42, 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
> reaso
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
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
1101 - 1200 of 2415 matches
Mail list logo
