Re: intent to retire roundcubemail in epel7

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

 





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

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




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux