Re: The Javapocalypse is Monday

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Jun 5, 2021 at 4:11 PM Sérgio Basto <sergio@xxxxxxxxxx> wrote:
>
> On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
> > On 6/4/21 12:30 AM, Jerry James wrote:
> > > I have packages that depend directly on the following, so I am
> > > willing
> > > to adopt them if nobody more competent shows up (although there is no
> > > point in taking ant-contrib if ant is going to be broken anyway):
> > > - ant-contrib
> > > - jakarta-common-httpclient
> > > - jakarta-ws-rs
> > > - maven-invoker-plugin
> > > - spec-version-maven-plugin
> > >
> > > I introduced the jansi1 and jline2 packages so that jansi could be
> > > moved to 2.x and jline to 3.x, but I don't actually maintain any
> > > packages that need the old versions.  I would like to give them away
> > > to someone who needs them, but note that you will need to grab
> > > jansi-native as well, before Monday!
> > >
> > > Has anybody already done something about any of these packages (and
> > > my
> > > packager-dashboard page just hasn't caught up yet)?  Is anybody
> > > planning to do something about any of these packages before they are
> > > retired on Monday?
> >
> > Hi,
> >
> > I looked at the orphaned packages looking for new maintainers,
> > which affects Clojure-packages and decided to take these:
> >
> > korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
> > plexus-velocity,  maven-script-interpreter, maven-mapping, weld-parent,
> > aopalliance, jakarta-server-pages, javaparser, jakarta-interceptors
> >
> > these were already taken by someone else:
> > apache-ivy, jansi-native
> >
> > Not really sure in what state these packages are, if I dont
> > have time to maintain them I'll reorphan them and orphan
> > the Clojure packages as well.
>
> I also have the same plan (if I dont have time to maintain them I'll
> reorphan )
>
> Now log4j-1.2 is required for ant and jboss-logging [1] can't we remove
> these dependencies on log4j-1.2 ?

Those packages both no longer depend on log4j12 (it might only look
that way to you because of the virtual provides; what they depend on
is actually only log4j 2.x). I have months ago ported both ant and
jboss-logging packages to use the log4j 1.2 API shim provided by log4j
instead of the old, deprecated, and security hole-y log4j12 package,
which is now retired in Fedora. Because I'd rather have packages use
the actually maintained, new version of log4j instead of an old and
dusty compat package.

Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux