https://bugzilla.redhat.com/show_bug.cgi?id=1886621

Mattia Verga <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
           Assignee|[email protected]          |[email protected]
         Resolution|---                         |NOTABUG
              Flags|fedora-review+              |
                   |needinfo?(mattia.verga@prot |
                   |onmail.com)                 |
        Last Closed|                            |2022-01-28 17:22:48



--- Comment #11 from Mattia Verga <[email protected]> ---
(In reply to Daniel Axelrod from comment #10)
> My apologies for the delay here, Mattia. I had a family emergency shortly
> after posting this ticket, and an email misconfiguration meant that I missed
> Bugzilla notifications until now.
> 
> Unfortunately, this package causes a particularly nasty PHP coredump in
> real-world use, for reasons I was unable to track down. Therefore, I would
> like to retract it from consideration.
> 
> Should I just set this ticket to CLOSED, or are there other cleanup steps
> that need to be done?

Don't worry, we all have other higher priorities other than Fedora packaging
:-)

I'll take care to ask to retire the repository in src.fedoraproject.org.


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1886621
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to