Re: Redis will no longer be OSS... now what?
On Thu, Mar 21, 2024 at 08:29:09AM +, Richard W.M. Jones wrote: > On Wed, Mar 20, 2024 at 06:19:28PM -0400, Neal Gompa wrote: > > Hey everyone, > > > > It looks like Redis, Inc. has announced that future versions of Redis > > are no longer OSS and will be dual-licensed SSPL and RSAL[1]. Absent a > > fork of Redis coming up, we will likely need to remove Redis from > > Fedora. > > > > All I can say is... :( > > > > [1]: https://redis.com/blog/redis-adopts-dual-source-available-licensing/ > > Another alternative is that someone in the community might fork it. > Can we stick with the last free version for a few months to see how > the pieces fall? Hi all, just noticed one fork, might be worth keeping eye on: https://codeberg.org/redict/redict Best regards, Markku > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-top is 'top' for virtual machines. Tiny program with many > powerful monitoring features, net stats, disk stats, logging, etc. > http://people.redhat.com/~rjones/virt-top > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 at 05:10:55PM +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: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2023-08-21.txt > > Package (co)maintainers Status > Change > > maven-clean-pluginmizdebsk, mkulik, orphan 4 weeks ago Hi all, I took maven-clean-plugin as some of my packages depend on it. I accidently tried to post this on devel-announce, sorry about that. Best wishes, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 at 05:10:55PM +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: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Request package ownership via the *Take* button in he left column on > https://src.fedoraproject.org/rpms/ > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2023-08-21.txt > grep it for your FAS username and follow the dependency chain. > > For human readable dependency chains, > see https://packager-dashboard.fedoraproject.org/ > For all orphaned packages, > see https://packager-dashboard.fedoraproject.org/orphan > > Package (co)maintainers Status > Change > > maven-clean-pluginmizdebsk, mkulik, orphan 4 weeks ago Hi all, I took maven-clean-plugin as some of my packages depend on it. Best wishes, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Eclipse IDE packages and friends orphaned
On 8/11/21 1:35 PM, Aleksandar Kurtakov wrote: *snip* > *List of packages orphaned (all were maintained for the sake of Eclipse > stack):* > * eclipse > * cbi-plugins > * eclipse-ecf > * eclipse-egit > * eclipse-emf > * eclipse-gef > * eclipse-jgit > * eclipse-license > * eclipse-m2e-core > * eclipse-m2e-workspace > * eclipse-mpc > * eclipse-subclipse > * eclipse-webtools > * felix-gogo-command > * felix-gogo-parent > * felix-gogo-runtime > * felix-gogo-shell > * felix-scr > * icu4j > * jsch > * lucene > * rhino > * takari-polyglot > * tycho Hi, I took jsch, it seems to affect couple of important packages. Also noticed kawa being orphaned, I took that too. BR, Markku > -- > Aleksandar Kurtakov > Red Hat Eclipse Team > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The Javapocalypse is Monday
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. BR, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The Death of Java (packages)
On 4/26/21 10:19 PM, Fabio Valentini wrote: > Hi everybody, > > Long story short, I can no longer in good conscience be the primary > maintainer of (most) Java packages in Fedora. I am not using any of > them, I don't like Java or any other languages targeting the JVM, and > don't get me started on the horrid Java ecosystem. Recently I've been > spending 40-60 hours per week at my desk, and I just don't have the > capacity to feel guilty for not taking care of those packages any > longer. Thank you for the past work, you've done huge effort to keep java packages in Fedora. Best wishes, Markku > > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: RFC: Automatically generated BuildRequires for maven-based Java projects
On 5/18/20 5:06 PM, Fabio Valentini wrote: > Good $LOCAL_TIME_OF_DAY, Hi, > Since this is still work-in-progress (though it works for a few simple > packages I tried it with), please feel free to report your > experiences, and - more importantly - open issues when the tool either > crashes (it shouldn't, since the POM parser successfully parsed all > non-broken maven project files from all fedora packages), or when it > generates too many (not that problematic) or too few (not so good) > dependencies. Sorry, took a while to find time to give this a spin. Tried this with my packages and few mockbuilds, tool successfully found all dependencies. Had to remove few extra plugins from pom as previously I had just put minimal dependencies required to build the package and mvn-genbr listed all plugins it detected. But nice work, this should reduce packaging efforts on Java-projects. Best wishes, Markku > The code for the POM parser and mvn-genbr lives in this project on pagure: > https://pagure.io/ironthree/pommes > > Go forth and break my code! > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Re-Launching the Java SIG
On 5/11/20 10:45 PM, Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not focused or organized right > now Great, really appreciate your work. > > So, if you're interested, please consider joining this group effort. > I'll get new members set up with the FAS group / pagure project / mailing > list. Count me in! I'm relatively new to fedora and rpm packaging, but got ~20 years of working with Java and my packages depends on the Java ecosystem. FAS account: korkeala. Markku. > Let's make this happen. > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Orphaned maven-release
Hi, I just orphaned maven-release package, I took this package last week as my package depended on maven-release, but then I was able to build it without the maven-release dependency (thanks Fabian!). Best regards, Markku Korkeala ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers (anaconda also affected)
On 4/30/20 3:12 PM, Fabio Valentini wrote: > On Thu, Apr 30, 2020 at 6:35 AM Markku Korkeala > wrote: >> >> On 4/27/20 1:39 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: >>> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life >>> >>> maven-release jcapik, orphan 2 >>> weeks ago >> >> Hi, >> >> I took maven-release as my package depends on it. Seems like >> updated dependencies broke the build, I'll see if that can be fixed > > Hi Markku, > > I'm almost 100% certain that your RPM package doesn't actually need > maven-release. > I suspect the dependency can just be removed when using > `%pom_remove_dep :maven-release-plugin` in %prep, or with something > similar. > If you tell me which package you're talking about, I can even send you a PR > ... Hi Fabio, thanks, I'll try that this weekend! My package is clojure-maven-plugin, which adds support building clojure programs with maven. Other idea was to prevent more java-packages to disappear from non-modular Fedora, but perhaps its more wise to channel that work to other java-packages. BR, Markku > Fabio > >> I'll see if I can take some other java packages as well to prevent >> them all being retired. >> >> >> Best wishes, >> Markku >> >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> 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@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers (anaconda also affected)
On 4/27/20 1:39 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: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > maven-release jcapik, orphan 2 > weeks ago Hi, I took maven-release as my package depends on it. Seems like updated dependencies broke the build, I'll see if that can be fixed I'll see if I can take some other java packages as well to prevent them all being retired. Best wishes, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Need help with getting packager permissions to bugzilla account
Kevin Fenzi kirjoitti 6.4.2020 21:46: On Mon, Apr 06, 2020 at 05:40:32PM +0300, Markku Korkeala wrote: Hi, I was sponsored to the packager group last year (FAS account korkeala), that time I had an old bugzilla account which I used. Now that I tried to do my first review, but it seems that I did not have privileges to assign the review request to myself. I check that I did not have any bugzilla permissions. Then I changed my old bugzilla account email and Fedora account email so I could login using fresh email address and get a fresh account to the bugzilla, hoping that the permissions would be automatically transferred through SAML. But still no permissions. Could someone help me get the correct packager permissions to the bugzilla? Yep. You should be set now, I manually added the perms. We have a script that is supposed to do this, but it's broken: https://pagure.io/fedora-infrastructure/issue/8628 Works now, thank you! -- Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Need help with getting packager permissions to bugzilla account
Hi, I was sponsored to the packager group last year (FAS account korkeala), that time I had an old bugzilla account which I used. Now that I tried to do my first review, but it seems that I did not have privileges to assign the review request to myself. I check that I did not have any bugzilla permissions. Then I changed my old bugzilla account email and Fedora account email so I could login using fresh email address and get a fresh account to the bugzilla, hoping that the permissions would be automatically transferred through SAML. But still no permissions. Could someone help me get the correct packager permissions to the bugzilla? Best wishes, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Review swaps: clojure-spec-alpha and clojure-core-specs-alpha
Hi, anyone up for review swaps? I'm updating clojure and it requires two new dependencies, here are the review requests: https://bugzilla.redhat.com/show_bug.cgi?id=1821025 https://bugzilla.redhat.com/show_bug.cgi?id=1821026 Best wishes, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Heads-up: updating Clojure to 1.9 in rawhide
Hi, I'm the process updating package Clojure to 1.9 in rawhide, this will require few alpha/beta releases to get new required dependencies built as well. Best regards, Markku Korkeala ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: How to handle circular build dependencies?
Rex Dieter kirjoitti 28.1.2020 16:57: Markku Korkeala wrote: Hi, sorry if this a newbie question, I tried to search this but did not find good documentation on this problem. I'm in the process of upgrading the clojure package to next version, which has new dependencies. These dependencies require certain clojure version themselves, so it makes a chicken-and-egg kind of problem. Are there good ways to handle these kind of circular dependencies? See if this helps, https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping Hi, thanks, I'll check that out. Markku. -- Rex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: How to handle circular build dependencies?
Richard W.M. Jones kirjoitti 27.1.2020 22:35: On Mon, Jan 27, 2020 at 06:43:36PM +0200, Markku Korkeala wrote: I think it's Perl where IIRC the package can be configured as a bootstrap package (by setting an RPM variable), built that way, the dependencies are then built, then the perl package is flipped back to non-bootstrap mode and built a second time against those just built dependencies. If you do it all in a side tag then no one will see the intermediate packages. I know I can update clojure to certain alpha version, which the new libraries require. Then build those, and when they are accepted then upgrade the clojure package, and then upgrade those libraries, etc. But it is tedious. I'm hoping there would be a better way :) Is it possible to build a "cut down" clojure which doesn't need the dependencies (ie that would be the bootstrap version)? And also do I have to do that bootstrapping again when building clojure for example EPEL-8? Probably :-) IMHO it helps to script Koji builds. We don't have any official tooling for that as far as I'm aware, but various people have built unofficial tools including me (see https://rwmj.wordpress.com/2020/01/14/goals-an-experimental-new-tool-which-generalizes-make/ http://git.annexia.org/?p=fedora-ocaml-rebuild.git;a=summary) Rich. Hi, thanks for all the suggestions and links. It should be possible to build "cut down" clojure, but might require too much effort. I think I'll study the problem little bit more and see also how the Debian maintainers solved this issue. -- Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
How to handle circular build dependencies?
Hi, sorry if this a newbie question, I tried to search this but did not find good documentation on this problem. I'm in the process of upgrading the clojure package to next version, which has new dependencies. These dependencies require certain clojure version themselves, so it makes a chicken-and-egg kind of problem. Are there good ways to handle these kind of circular dependencies? I know I can update clojure to certain alpha version, which the new libraries require. Then build those, and when they are accepted then upgrade the clojure package, and then upgrade those libraries, etc. But it is tedious. I'm hoping there would be a better way :) And also do I have to do that bootstrapping again when building clojure for example EPEL-8? Best regards, Markku -- Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers
Fabio Valentini writes: > On Tue, Sep 3, 2019 at 5:41 PM Markku Korkeala wrote: >> >> Miro Hrončok kirjoitti 2019-09-02 13:00: >> > clojure kushal, orphan, s4504kr, 1 >> > weeks ago >> > salimma, walters >> >> I would like to take clojure, filed a releng ticket: >> >> https://pagure.io/releng/issue/8732 > > Be advised that clojure has failed to build since fedora 23, according to > koji. > I wonder why it hasn't been retired at some point ... Thanks for the warning. I already did a PR a while back, which would have fixed the build issue and update to version 1.8.0, but it didn't get merged. There is still work to do to update newer releases as there are new build requirements to package. Markku > Fabio > >> BR, >> Markku >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> 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@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers
Miro Hrončok kirjoitti 2019-09-02 13:00: clojure kushal, orphan, s4504kr, 1 weeks ago salimma, walters I would like to take clojure, filed a releng ticket: https://pagure.io/releng/issue/8732 BR, Markku ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Self Introduction: Markku Korkeala
Hi all, I'm new to the Fedora-project, here is a short introduction. I am a Clojure/Java developer residing in Finland and a long time Fedore user, since Fedore Core 5. I joined the Fedora project to package Clojure and Java libraries and programs. I would like to become a owner of a retired package, clojure-maven-plugin, and then package libraries (clojure-spec-alpha, clojure-core-specs-alpha and clojure-pom-contrib) required to update Clojure to the latest version. Best regards, Markku Korkeala ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
