Re: Ancient Puppet version in EPEL-7: remove it?
On Fri, Apr 29, 2022 at 7:21 AM Nico Kadel-Garcia wrote: > On Thu, Apr 28, 2022 at 11:49 PM Neal Gompa wrote: > > > > On Thu, Apr 28, 2022 at 11:38 PM Demi Marie Obenour > > wrote: > > > > > > On 4/28/22 07:09, Nico Kadel-Garcia wrote: > > > > On Wed, Apr 27, 2022 at 9:08 PM Demi Marie Obenour > > > > wrote: > > > >> > > > >> On 4/27/22 07:40, Ewoud Kohl van Wijngaarden wrote: > > > >>> On Tue, Apr 26, 2022 at 09:03:45PM -0500, Carl George wrote: > > > On Tue, Apr 26, 2022 at 1:25 PM Ewoud Kohl van Wijngaarden > > > wrote: > > > > > > > > Hello everyone, > > > > > > > > There is an ancient version of Puppet in EPEL-7. Version 3.6 has > been > > > > EOL for ages now. > https://binford2k.com/2016/11/22/puppet-3.x-eol/ has a > > > > nice EOL overview: > > > > > > > > * Puppet 3 - 2016-12-31 > > > > * Puppet 4 - 2018-10-?? > > > > * Puppet 5 - 2021-02-?? > > > > > > > > Puppet 6 requires a newer Ruby version than is available in EL7 > so > > > > rebasing the whole stack is not going to work. In theory you > could use > > > > SCLs but I think it's unrealistic to expect that. > > > > > > > > However, all bugs open for Puppet relate to EPEL-7[1] so I'm > wondering > > > > what to do. > > > > > > > > We can close all bugs as WONTFIX (including the security ones), > but > > > > would it be better to also remove the package from EPEL-7? > > > > > > > > Regards, > > > > Ewoud Kohl van Wijngaarden > > > > > > > > [1]: > https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=puppet_id=12574395=Fedora=Fedora%20EPEL > > > > > > Retiring epel7's puppet may be the preferred option. It is > allowed > > > [0], but if you go this route please mention it on the epel-devel > list > > > (and perhaps epel-announce) first. > > > >>> > > > >>> I should have realized this, will bring it up there. > > > >>> > > > Alternatively, have you considered doing an incompatible update > [1] to > > > version 5? It may already be EOL, but surely that's a better > option > > > than the current version 3 or removing it entirely. > > > >>> > > > >>> The Ruby version in EL7 is simply too old. In theory you could > write a > > > >>> ton of patches to make it compatible again, but the Puppet modules > users > > > >>> have may be assuming Ruby 2.4+ with Puppet 5. Also note that > Puppet 5 > > > >>> itself is already EOL (for more than a year), but packaging Puppet > 6 vs > > > >>> Puppet 5 (or really, Puppet 7 as well) isn't a big difference: you > need > > > >>> a newer Ruby. After that it's all minor differences. > > > >>> > > > [0] > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#what_can_be_retired > > > [1] > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ > > > >> > > > >> Bundle a newer Ruby? > > > > > > > > RHEL 7 has published "software collection library" versions of ruby, > > > > titled "rh-ruby25". > > > > > > > > As somebody who's backported bulky software for RHEL based operating > > > > systems, like Samba and current ansible and airflow and yes, years > > > > ago, puppet, I don't recommend installing your own ruby. Resolving > the > > > > dependencies gets painful, fast. > > > > > > In that case, I would be fine with saying, “if you need to run Puppet > > > on RHEL 7, do so in a container or VM based on a newer RHEL”. > > > > > > > Puppet is not very useful in a container. It's a systems management > > tool, so it's designed to manage the computer itself. > > That did take a bit of giggling when I saw it. > > "puppet-agent" is available, updated, from puppetlabs at > http://yum.puppetlabs.com/puppet/el/7/ . They even have a > "puppetlabs-release" repo to enable that repo in yum. > > Maybe it's time to drop the obsolete EPEL version altogether? Or to > beg puppetlabs to publish an EPEL package themselves? I don't > currently have a subscription, so have little leverage with them these > days. > ___ > 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 The last time I spoke to them, they had no interest in pushing packages to EPEL. They didn't use standard procedures to create RPM files, they didn't even have the spec files for their packages back then (not sure if this has changed). That was a few years ago, when I pushed puppet 6 to EPEL 8, and later upgraded Fedora's puppet to the 6th version as well. I don't think that that has
Re: Ancient Puppet version in EPEL-7: remove it?
I believe it may be time to retire puppet from EPEL 7. The presented reasons are fair in my opinion. The el7 users can easily migrate over to higher versions either using the self-contained package offered by Puppet Labs, or can install the aforementioned rh-ruby26 and then install puppet >=6 via gem (gem install puppet). - Breno On Tue, Apr 26, 2022 at 4:48 PM Ewoud Kohl van Wijngaarden < ewoud+fed...@kohlvanwijngaarden.nl> wrote: > On Tue, Apr 26, 2022 at 02:49:26PM -0400, Nico Kadel-Garcia wrote: > >On Tue, Apr 26, 2022 at 2:10 PM Ewoud Kohl van Wijngaarden > > wrote: > >> > >> Hello everyone, > >> > >> There is an ancient version of Puppet in EPEL-7. Version 3.6 has been > >> EOL for ages now. https://binford2k.com/2016/11/22/puppet-3.x-eol/ has > a > >> nice EOL overview: > >> > >> * Puppet 3 - 2016-12-31 > >> * Puppet 4 - 2018-10-?? > >> * Puppet 5 - 2021-02-?? > >> > >> Puppet 6 requires a newer Ruby version than is available in EL7 so > >> rebasing the whole stack is not going to work. In theory you could use > >> SCLs but I think it's unrealistic to expect that. > > > >Rebuild it with the sco packages, namely rh-ruby25 ? > > I'll state that I have extensive SCL knowledge, after working with it in > packaging Foreman. With that I'll clarify why I think it's unrealistic. > > The primary reason is that I have no interest nor use for it at all. > Right my last EL7 machine is using the Puppet AIO package and I'll phase > it out soon. > > Second, I don't know if anyone has done this and what the effects will > be. Providers such as the gem package provider will behave different. > You also won't have access to any Ruby gems that you may have installed. > As such it'll be a massive non-trivial migration for any user. > > Speaking of gems, you will need to build all the dependent gems in the > SCL. This means a lot of gems need to be modified and released. From > experience I can tell you there are many things you can easily mess up, > as well as bugs in the SCL stack you need to work around (BZ1995018 > being particularly nasty). Which brings me back to my primary reason: I > have no time for this. > > BZ1995018: https://bugzilla.redhat.com/show_bug.cgi?id=1995018 > ___ 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: Kubernetes Development SIG
I would like to be part too :) - Breno On Tue, 15 Sep 2020 at 11:46, Ankur Sinha wrote: > On Tue, Sep 15, 2020 20:25:18 +0530, Sumantro Mukherjee wrote: > > > > > > On Tue, Sep 15, 2020 at 7:15 PM Leonardo Rossetti > wrote: > > > > Hello all, > > > > I would like to present a Kubernetes Development SIG. > > > > > > I would love to be a part of the group! > > +1, mostly as a user :) > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London > ___ > 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
[EPEL-devel] Re: Puppet 6 in EPEL 8
That's correct. When I started the idea was for me to take care of the epel8 branch. I've been more into Fedora lately and we might push it to Rawhide soon. I'm in touch with other maintainers of the package to make it happen. Thanks for asking. - Breno On Wed, 15 Jul 2020 at 09:02, Stephen John Smoogen wrote: > On Tue, 14 Jul 2020 at 19:41, Igor Raits > wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On Tue, 2020-07-14 at 10:35 -0400, Breno Brand Fernandes wrote: > > > Hi all, > > > > > > I've just pushed puppet 6 (agent) to EPEL 8 (testing) today [1]. > > > > > > If you use puppet 6 and have a moment to test it or want to have a > > > look > > > at/review the spec file [2], that would be nice. I've been testing it > > > for a > > > couple of months, and for my use, it seems all good. > > > > > > Feel free to PM me with any suggestions, questions, fixes, etc. > > > I don't plan to make bigger changes to it, though, since it seems > > > stable. > > > > > > FYI, the next step will be submitting puppetserver 6 to package > > > review. > > > > > > 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e13502b7fa > > > 2 https://src.fedoraproject.org/rpms/puppet/blob/epel8/f/puppet.spec > > > > Any plans for making an update in Fedora Rawhide too? > > > > When Breno started on this, he was only running in EL so could not > support Fedora. We said that was ok and someone in Fedora could take > over maintainer-ship of it if they wanted to. > > > -- > Stephen J Smoogen. > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Puppet 6 in EPEL 8
Hi all, I've just pushed puppet 6 (agent) to EPEL 8 (testing) today [1]. If you use puppet 6 and have a moment to test it or want to have a look at/review the spec file [2], that would be nice. I've been testing it for a couple of months, and for my use, it seems all good. Feel free to PM me with any suggestions, questions, fixes, etc. I don't plan to make bigger changes to it, though, since it seems stable. FYI, the next step will be submitting puppetserver 6 to package review. 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e13502b7fa 2 https://src.fedoraproject.org/rpms/puppet/blob/epel8/f/puppet.spec Thanks. - Breno ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Review swaps
Hi all, I have these 2 packages that are probably almost OK. They were reviewed and should be probably good now. https://bugzilla.redhat.com/show_bug.cgi?id=1811777 https://bugzilla.redhat.com/show_bug.cgi?id=1811774 Would anyone give me a hand? They are important for having puppet and puppetserver 6 on el8. Let's swap reviews. Thanks. - Breno ___ 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: Non-responsive maintainer: glances
I also had filed this ticket, back in Oct/2019 asking the EL8 build. https://bugzilla.redhat.com/show_bug.cgi?id=1763319 On Thu, 21 May 2020 at 14:26, Richard Shaw wrote: > I did a local update and tested it, being innocuous enough I went and and > updated and am performing builds now. Hopefully madko will show back up > at some point. > > I also did a local build for EPEL 8 but it needs two python packages: > psutil & future > > Both built fine from Fedora master so when I get a minute I may file bugs > to request EPEL 8 branches. > > Thanks, > Richard > ___ > 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: Non-responsive maintainer: laxathom (Xavier Lamien)
Thanks for answering Xavier. I am checking with Vascom why I can't see the libgdiplus-devel in EPEL 8. - Breno On Wed, 22 Apr 2020 at 15:04, Xavier Lamien wrote: > Oh hi, > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too efficient I'd say. > > Any way, I'll have a look at your ticket asap. > Also, I'm more than welcome to get co-maintainer on this package so feel > free to request access since you're looking into it. > > Cheers, > -x > > > On Wed, Apr 22, 2020, 8:10 PM Breno Brand Fernandes > wrote: > >> Hi, >> >> I've been trying to get in contact with Xavier Lamien since Sep 2019 [1]. >> The package libgdiplus is particularly important to have mono built in >> EPEL 8. >> >> I am following the policy for non-responsive package maintainers [2]. >> In 7 days if I don't get any answers I will be filling a ticket to >> maintain it if none is against it. >> >> 1 https://bugzilla.redhat.com/show_bug.cgi?id=1749560 >> 2 >> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ >> >> Thank you. >> ___ >> 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: Non-responsive maintainer: laxathom (Xavier Lamien)
Hi Vascom, I don't see the -devel package available. Why is that? On Wed, 22 Apr 2020 at 15:07, Vascom wrote: > I already built it. > > But you can update to 6.0.5 :) > > ср, 22 апр. 2020 г. в 22:04, Xavier Lamien : > > > > Oh hi, > > > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too efficient I'd say. > > > > Any way, I'll have a look at your ticket asap. > > Also, I'm more than welcome to get co-maintainer on this package so feel > free to request access since you're looking into it. > > > > Cheers, > > -x > > > > > > On Wed, Apr 22, 2020, 8:10 PM Breno Brand Fernandes > wrote: > >> > >> Hi, > >> > >> I've been trying to get in contact with Xavier Lamien since Sep 2019 > [1]. > >> The package libgdiplus is particularly important to have mono built in > EPEL 8. > >> > >> I am following the policy for non-responsive package maintainers [2]. > >> In 7 days if I don't get any answers I will be filling a ticket to > maintain it if none is against it. > >> > >> 1 https://bugzilla.redhat.com/show_bug.cgi?id=1749560 > >> 2 > https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ > >> > >> Thank you. > >> ___ > >> 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 > ___ 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
Non-responsive maintainer: laxathom (Xavier Lamien)
Hi, I've been trying to get in contact with Xavier Lamien since Sep 2019 [1]. The package libgdiplus is particularly important to have mono built in EPEL 8. I am following the policy for non-responsive package maintainers [2]. In 7 days if I don't get any answers I will be filling a ticket to maintain it if none is against it. 1 https://bugzilla.redhat.com/show_bug.cgi?id=1749560 2 https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ Thank you. ___ 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 Swap
Hi, Would you want to swap reviews? This was generated with go2rpm. It should be easy to review. https://bugzilla.redhat.com/show_bug.cgi?id=1806219 Thanks ___ 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 Swap
Hi, Would someone mind swapping reviews? I am building puppet 6 for EPEL 8 and this one[1] is a dependency. 1 https://bugzilla.redhat.com/show_bug.cgi?id=1803276 Thank you!! ___ 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 Swap
Hi, Would someone mind swapping reviews? I am building puppet 6 for EPEL 8 and this one[1] is the very first dependency. 1 https://bugzilla.redhat.com/show_bug.cgi?id=1794229 Thank you!! - B ___ 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
[EPEL-devel] Ownership announce of retired package Pound
Hi all, Recently, I've sent an email on epel-dev regarding this ownership request[1]. So, somethings may be repeated for some of you (I'm sorry!). The package Pound was retired about a year ago. It failed to build and at that time the maintainer didn't give any feedback on it[2]. Since then, the Pound project was forked and has been maintained[3]. I would like to maintain the package in EPEL. I've made some tests and I believe I have a working spec file for it[4, 5, 6]. I am now following the Claiming Ownership of a Retired Package procedure[7]. Please, let me know if it is all good for you guys that I'd become the maintainer. Thanks. 1 - https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/74GMAJGMWK3VEA4U2D7C6RRNJDFT3H5K/ 2 - https://bugzilla.redhat.com/show_bug.cgi?id=1674583 3 - https://github.com/patrodyne/pound 4 - https://src.fedoraproject.org/fork/brandfbb/rpms/Pound/commits/epel8 5 - https://copr.fedorainfracloud.org/coprs/brandfbb/Pound-2.8-patrodyne/ 6 - https://koji.fedoraproject.org/koji/taskinfo?taskID=40203731 7 - https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package - Breno ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Ownership announce of retired package Pound
Hi all, Recently, I've sent an email on epel-dev regarding this ownership request[1]. So, somethings may be repeated for some of you (I'm sorry!). The package Pound was retired about a year ago. It failed to build and at that time the maintainer didn't give any feedback on it[2]. Since then, the Pound project was forked and has been maintained[3]. I would like to maintain the package in EPEL. I've made some tests and I believe I have a working spec file for it[4, 5, 6]. I am now following the Claiming Ownership of a Retired Package procedure[7]. Please, let me know if it is all good for you guys that I'd become the maintainer. Thanks. 1 - https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org/message/74GMAJGMWK3VEA4U2D7C6RRNJDFT3H5K/ 2 - https://bugzilla.redhat.com/show_bug.cgi?id=1674583 3 - https://github.com/patrodyne/pound 4 - https://src.fedoraproject.org/fork/brandfbb/rpms/Pound/commits/epel8 5 - https://copr.fedorainfracloud.org/coprs/brandfbb/Pound-2.8-patrodyne/ 6 - https://koji.fedoraproject.org/koji/taskinfo?taskID=40203731 7 - https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package - Breno ___ 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
[EPEL-devel] Pound in EPEL 8
Hi all, It seems that the package was retired on 2019-02-11[1]. I filed a bug[2] asking if it would be possible to build it using the patrodyne fork[3]. This fork contains patches in order to make Pound support OpenSSL v1.1.0 and WebSocket correctly. As so far I didn't receive any answer, I decided to send this message. I forked the package in src.fedoraproject.org, updated the spec file[4] and created a copr[5] mirror. I also built it against EPEL 8 playground[6]. I performed some tests and it all seems to be working well. Do you think we could have this or any other build of this fork of Pound in EPEL 8? I am in the packager group, and I'd be happy to help to maintain this package. Any other input anyone may have is very welcome. Thanks. 1 - https://bugzilla.redhat.com/show_bug.cgi?id=1674583 2 - https://bugzilla.redhat.com/show_bug.cgi?id=1753023 3 - https://github.com/patrodyne/pound 4 - https://src.fedoraproject.org/fork/brandfbb/rpms/Pound/commits/epel8 5 - https://copr.fedorainfracloud.org/coprs/brandfbb/Pound-2.8-patrodyne/ 6 - https://koji.fedoraproject.org/koji/taskinfo?taskID=40203731 - Breno ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Self Introduction: Breno B. Fernandes
Hi all, I am ~33 years old and I've been using (and working with?) Linux since I was 16-ish. I've been using Centos/RedHat/Fedora for a while and am now interested in getting more involved. I talk to some of you at #epel@freenode. People are always very helpful and friendly. I expect to consistently contribute to the Fedora community. It is very nice to get to know such a community with so many brilliant people. - Breno ___ 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
[rpms/perl-Time-Duration] PR #1: Rebuilt for RedHat 8 (EPEL8)
brandfbb opened a new pull-request against the project: `perl-Time-Duration` that you are following: `` Rebuilt for RedHat 8 (EPEL8) `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Time-Duration/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
