[EPEL-devel] Re: intent to retire roundcubemail in epel7
On 24/05/2021 19:36, Sérgio Basto wrote: On Sat, 2021-05-22 at 11:57 -0700, Kevin Fenzi wrote: On Tue, May 18, 2021 at 06:32:25AM -0700, Troy Dawson wrote: On Tue, May 18, 2021 at 4:20 AM Stephen John Smoogen < smo...@gmail.com> wrote: ...snip... Here's a scratch build of 1.4.11, but I bet it won't work as many of the php-pear packages are too old. ;( https://koji.fedoraproject.org/koji/taskinfo?taskID=68489451 why not use https://www.softwarecollections.org/en/scls/rhscl/rh-php72/ ? If Roundcube 1.4 doesn't work, 1.3 will. I am wondering if we need a different way to announce reasons for this: [ ] I no longer use RHEL-7 so can not test [ ] I found that there are too many package updates needed that I do not have time for. [ ] The following RHEL packages are too old for this package to be updated [ ] The upstream is dead and I can not fix ... Or maybe instead of saying it's retiring, do Fedora's Orphaning format. Announce they are orphaning the package, and if a package is orphaned for a certain amount of time, and has all the orphan annoucements, it get's removed. But I do like your checkbox way for announcing the reasons for retiring/orphaning. Well, thats what goes in the dead.package file when the package is retired. :) I was just wanting to stop shipping a known vulnerable package and get it off my dashboard with all it's CVE's. I'm pretty sure 1.4.11 isn't actually going to work, but happy for someone to prove me wrong. I don't really have the time to investigate further myself. So, I will orphan it now, if no one takes it in a while, I will retire it then? kevin ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: intent to retire roundcubemail in epel7
On Mon, 24 May 2021 at 14:36, Sérgio Basto wrote: > On Sat, 2021-05-22 at 11:57 -0700, Kevin Fenzi wrote: > > On Tue, May 18, 2021 at 06:32:25AM -0700, Troy Dawson wrote: > > > On Tue, May 18, 2021 at 4:20 AM Stephen John Smoogen < > > > smo...@gmail.com> > > > wrote: > > > > ...snip... > > > > Here's a scratch build of 1.4.11, but I bet it won't work as many of > > the > > php-pear packages are too old. ;( > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=68489451 > > > > why not use https://www.softwarecollections.org/en/scls/rhscl/rh-php72/ > ? > > > EPEL packages may rely on Red Hat SCL's for build dependencies but not run-time dependencies. In this case this would be a run-time dependency requirement. -- Stephen J Smoogen. I've seen things you people wouldn't believe. Flame wars in sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. All those moments will be lost in time... like posts on BBS... time to reboot. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: intent to retire roundcubemail in epel7
On Sat, 2021-05-22 at 11:57 -0700, Kevin Fenzi wrote: > On Tue, May 18, 2021 at 06:32:25AM -0700, Troy Dawson wrote: > > On Tue, May 18, 2021 at 4:20 AM Stephen John Smoogen < > > smo...@gmail.com> > > wrote: > > ...snip... > > Here's a scratch build of 1.4.11, but I bet it won't work as many of > the > php-pear packages are too old. ;( > > https://koji.fedoraproject.org/koji/taskinfo?taskID=68489451 > why not use https://www.softwarecollections.org/en/scls/rhscl/rh-php72/ ? > > > I am wondering if we need a different way to announce reasons for > > > this: > > > > > > [ ] I no longer use RHEL-7 so can not test > > > [ ] I found that there are too many package updates needed that I > > > do not > > > have time for. > > > [ ] The following RHEL packages are too old for this package to be > > > updated > > > [ ] The upstream is dead and I can not fix > > > ... > > > > Or maybe instead of saying it's retiring, do Fedora's Orphaning > > format. > > Announce they are orphaning the package, and if a package is orphaned > > for a > > certain amount of time, and has all the orphan annoucements, it get's > > removed. > > But I do like your checkbox way for announcing the reasons for > > retiring/orphaning. > > Well, thats what goes in the dead.package file when the package is > retired. :) > > I was just wanting to stop shipping a known vulnerable package and get > it off my dashboard with all it's CVE's. I'm pretty sure 1.4.11 isn't > actually going to work, but happy for someone to prove me wrong. I > don't > really have the time to investigate further myself. > > So, I will orphan it now, if no one takes it in a while, I will retire > it then? > > kevin > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: fedpkg Kerberos failing for me on el7
On Mon, May 24, 2021 at 03:30:58PM +, Dave Dykstra wrote: > Is anybody else having trouble with using kerberos with fedpkg on el7? > It is working for me on el8, and it used to work for me on el7, but now > on my el7 machine any time I try to do an upload I get > Could not execute upload: Request is unauthorized. > and with fedpkg build I get > Kerberos authentication fails: unable to obtain a session > Could not execute build: Could not login to > https://koji.fedoraproject.org/kojihub > > This is with fedpkg-1.40-6.el7 installed from epel and after successfully > doing kinit d...@fedoraproject.org. Can you make a ticket at https://pagure.io/fedora-infrastructure and include the output of the failing commands with: "KRB5_TRACE=/dev/stdout" prepended (that will give debugging output). Thanks, kevin signature.asc Description: PGP signature ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] fedpkg Kerberos failing for me on el7
Is anybody else having trouble with using kerberos with fedpkg on el7? It is working for me on el8, and it used to work for me on el7, but now on my el7 machine any time I try to do an upload I get Could not execute upload: Request is unauthorized. and with fedpkg build I get Kerberos authentication fails: unable to obtain a session Could not execute build: Could not login to https://koji.fedoraproject.org/kojihub This is with fedpkg-1.40-6.el7 installed from epel and after successfully doing kinit d...@fedoraproject.org. Dave ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
