[EPEL-devel] Re: Outstanding package requests for EPEL-8
On Fri, Oct 25, 2019 at 11:14 AM Troy Dawson wrote: > On Fri, Oct 25, 2019 at 9:10 AM Richard Shaw wrote: > > > > On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote: > >> > >> All of the ones I've requested, I waited a few days to see if the > >> maintainer would pick it up. And after that I asked if they would > >> mind if I maintained it in EPEL8. About half of those the maintainer > >> was fine with me maintaining the package in EPEL8. > >> So, to answer your question, yes you can. > > > > > > That may be overly nice! > > > > I'm a pretty nice guy but if they are unwilling to maintain a package > in another branch you don't need their permission to do it yourself. What > do you do if they say no? :) > > > > Actually, I've had two say no. They were just about to retire the > packages from Fedora. They explained their reasons why, and I'm > currently working on getting those dependencies out of my packages > that required them. > > Honestly, I don't want more packages to maintain, I just want the > functionalities. I'm being overly nice hoping that someone else will > maintain them. But ... since I want the functionality, and I have the > skillset, I'm willing to maintain them. > Well that's a little different of a situation... You could still maintain them in EPEL if you wanted to though, but like you I'm trying not to pick up more packages. Thanks, Richard ___ 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] Re: Outstanding package requests for EPEL-8
On Fri, Oct 25, 2019 at 9:10 AM Richard Shaw wrote: > > On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote: >> >> All of the ones I've requested, I waited a few days to see if the >> maintainer would pick it up. And after that I asked if they would >> mind if I maintained it in EPEL8. About half of those the maintainer >> was fine with me maintaining the package in EPEL8. >> So, to answer your question, yes you can. > > > That may be overly nice! > > I'm a pretty nice guy but if they are unwilling to maintain a package in > another branch you don't need their permission to do it yourself. What do you > do if they say no? :) > Actually, I've had two say no. They were just about to retire the packages from Fedora. They explained their reasons why, and I'm currently working on getting those dependencies out of my packages that required them. Honestly, I don't want more packages to maintain, I just want the functionalities. I'm being overly nice hoping that someone else will maintain them. But ... since I want the functionality, and I have the skillset, I'm willing to maintain them. ___ 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] Re: Outstanding package requests for EPEL-8
On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote: > All of the ones I've requested, I waited a few days to see if the > maintainer would pick it up. And after that I asked if they would > mind if I maintained it in EPEL8. About half of those the maintainer > was fine with me maintaining the package in EPEL8. > So, to answer your question, yes you can. > That may be overly nice! I'm a pretty nice guy but if they are unwilling to maintain a package in another branch you don't need their permission to do it yourself. What do you do if they say no? :) Thanks, Richard ___ 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] Re: Outstanding package requests for EPEL-8
I wonder if we can request the branch and be added as co-maintainer ?
On Wed, 2019-10-23 at 13:38 -0400, Stephen John Smoogen wrote:
> So this came up in the last EPEL meeting:
> bugzilla query -s NEW -t 'epel8' --outputformat "%{id}:
> %{component}:
> %{summary}" | sort | less
>
>
> Most of these are package requests but some are other types.
>
> 1739162: libxml++: libxml++ for EPEL8
> 1739163: libffado: libffado for EPEL8
> 1741523: mod_auth_cas: mod_auth_cas for EPEL8
> 1741654: dash: RFE: dash for EPEL8
> 1744341: jq: RFE: jq for EPEL8
> 1744343: nagios-plugins-openmanage: RFE: nagios-plugins-openmanage
> for EPEL8
> 1744699: perl-Apache-LogFormat-Compiler: [RFE] EPEL8 branch of
> perl-Apache-LogFormat-Compiler
> 1744700: perl-Authen-Passphrase: [RFE] EPEL8 branch perl-Authen-
> Passphrase
> 1744704: perl-Authen-Simple-Passwd: [RFE] EPEL8 branch of
> perl-Authen-Simple-Passwd
> 1744705: perl-Authen-Passphrase: [RFE] EPEL8 branch of perl-Authen-
> Simple
> 1744712: perl-IO-Handle-Util: [RFE] EPEL8 branch for perl-IO-Handle-
> Util
> 1744782: perl-Crypt-SSLeay: (RFE) EPEL8 branch of perl-Crypt-SSLeay
> 1744785: perl-Proc-Daemon: (RFE) EPEL8 branch of perl-Proc-Daemon
> 1745727: apcupsd: [RFE] apcupsd: epel8 build request
> 1749146: lxqt-session: Build LXQt in EPEL8
> 1749780: genders: please build for epel8
> 1750404: php-phpmailer6: [RFE] EPEL8 branch of php-phpmailer6
> 1753203: weechat: Can you please make a package in EPEL8 with new
> Weechat version?
> 1753397: scons: Build for EPEL8
> 1753401: perl-Class-Accessor-Lite: [RFE] EPEL8 branch of
> perl-Class-Accessor-Lite
> 1754155: quazip: Create EPEL8 branc
> 1755034: python-passlib: [RFE] EPEL8 branch of python-passlib
> 1755264: dnf-plugins-extras: Please release the snapper plug-in for
> epel8 also.
> 1755345: python-mysql: Request to build python3-mysql for EPEL8
> 1755761: clementine: [RFE] : clementine : epel8 build request
> 1755789: pidgin-otr: [RFE] : pidgin-otr epel8 build request
> 1755791: powerline: [RFE] : powerline : epel8 build request
> 1755793: autossh: [RFE] : autossh epel8 build request
> 1755809: cross-binutils: [RFE] EPEL8 branch of cross-binutils
> 1755816: simple-scan: [RFE] : simple-scan : epel8 build request
> 1755945: bats: [RFE] bats: epel8 build request
> 1755960: liblastfm: Please provide EPEL8 package
> 1755963: libmygpo-qt: Please provide EPEL8 package
> 1755964: libprojectM: Please provide EPEL8 package
> 1755965: qca: Please provide EPEL8 package
> 1755966: udisks: Please provide EPEL8 package
> 1755968: sha2: Please provide EPEL8 package
> 1755975: phonon: Please provide EPEL8 package
> 1756036: perl-XML-TreePP: [RFE] perl-XML-TreePP build for epel8
> 1756170: libcec: [RFE] libcec build for epel8
> 1756171: perl-Net-UPnP: [RFE] perl-Net-UPnP build for epel8
> 1756941: kid3: [RFE] : kid3 : epel8 build request
> 1756942: pylast: [RFE] : pylast : epel8 build request
> 1756976: gtk-murrine-engine: [RFE] : gtk-murrine-engine : epel8 build
> request
> 1757000: xmlstarlet: xmlstarlet missing in EPEL8
> 1757002: docbook2X: docbook-utils-pdf missing in RHEL8/CentOS-8: need
> it in EPEL8
> 1757009: perl-Qt: perl-Qt 4.14.3 missing for EPEL8
> 1757016: ntfsprogs: ntfsprogs is missing for EPEL8
> 1757645: python-urlgrabber: [RFE] python3-urlgrabber build for epel8
> 1757682: thunderbird-enigmail: [RFE] : thunderbird-enigmail : epel8
> build request
> 1757868: uboot-tools: Package uboot-tools is not available in EPEL8
> 1758005: xlockmore: build xlockmore for epel8
> 1758271: ipython: Branch request: python3-ipython for epel8
> 1758311: nova-agent: build nova-agent for epel8
> 1758329: python-requests-cache: [RFE] python-requests-cache for epel8
> 1758340: python-oauth: [RFE] python-oauth build for epel8
> 1758778: fmt: fmt not packaged for epel8
> 1758779: xalan-c: xalan-c not packaged for epel8
> 1758780: spdlog: spdlog not packaged for epel8
> 1758822: python-funcsigs: [RFE] EPEL8 branch of python-funcsigs
> 1759107: python-celery: Branch request: python-celery for epel8
> 1759108: python-markdown2: Branch request: python-markdown2 for epel8
> 1759109: python-aiohttp: Branch request: python-aiohttp for epel8
> 1759112: python-requests-mock: Branch request: python-requests-mock
> for epel8
> 1759114: python-cached_property: Branch request:
> python-cached_property for epel8
> 1759116: python-xmlsec: Branch request: python-xmlsec for epel8
> 1759121: python-zeep: Branch request: python-zeep for epel8
> 1759124: python-XStatic-Patternfly: Branch request:
> python-XStatic-Patternfly for epel8
> 1759129: nodejs-typeahead.js: Branch request: nodejs-typeahead.js for
> epel8
> 1759130: python-flask-openid: Branch request: python-flask-openid for
> epel8
> 1759132: python-flask-wtf: Branch request: python-flask-wtf for epel8
> 1759133: python-flask-sqlalchemy: Branch request:
> python-flask-sqlalchemy for epel8
> 1759136: nodejs-moment: Branch request: nodejs-moment for epel8
> 1759459: phpMyAdmin: Please build phpMyAdmin for
[EPEL-devel] Re: Outstanding package requests for EPEL-8
Add txt2man, it got filed against el6 for some reason. I just fixed it. https://bugzilla.redhat.com/show_bug.cgi?id=1741795 Thanks, Richard ___ 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
