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

Carl George 🤠 <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Review Request:             |Review Request: python-pydo
                   |python3-pydo - Python       |- Python client for Digital
                   |client for Digital Ocean    |Ocean
              Flags|needinfo?([email protected])  |



--- Comment #8 from Carl George 🤠 <[email protected]> ---
> Carl What is the correct process here, should I follow the full process for 
> renaming a repo here:

Obsoletes/provides won't be necessary, because the binary RPM name isn't
changing.  Anyone who installed python3-pydo on Rawhide will see the next
update to python3-pydo (from the python-pydo SRPM) as a natural upgrade.  You
can trigger this sooner by going ahead and bumping the release from 1 to 2. 
You'll also want to add a changelog, which is missing from the current package.

> Or shall I just hit retire on all my branches and create a new repo?

Yes please.  I think to make the SCM toddler happy the subject of this bug has
to match the package name, so I'll go ahead and change that.


-- 
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=2380413

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

-- 
_______________________________________________
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://pagure.io/fedora-infrastructure/new_issue

Reply via email to