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

Ruslan Bekenev <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(benson_muite@emai
                   |                            |lplus.org)



--- Comment #6 from Ruslan Bekenev <[email protected]> ---
SPEC URL:
https://download.copr.fedorainfracloud.org/results/krydos/emacs-php-mode/fedora-rawhide-x86_64/10202813-emacs-php-mode/emacs-php-mode.spec
SRPM URL:
https://download.copr.fedorainfracloud.org/results/krydos/emacs-php-mode/fedora-rawhide-x86_64/10202813-emacs-php-mode/emacs-php-mode-1.27.0-1.fc45.src.rpm

Updated. 

Thank you for the links and especially for the "dnf repoquery whatowns".
Since eask is now in f44 I only built this package for f44 and rawhide. I hope
that is correct way of doing it. 

I'm still quite unclear on how do I take ownership of
https://src.fedoraproject.org/rpms/emacs-php-mode. 
Benson, do you know if it is something that I'll be able to do after I become a
packager or is there something else to do? If it's something else I should
probably work on that in parallel.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2440157

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202440157%23c6

-- 
_______________________________________________
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, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to