#66 copr edit-package-tito on pypi package redefines it
Closed: Won't fix 3 years ago by praiskup. Opened 6 years ago by brianjmurrell.

If I run copr edit-package-tito --name foo --git-url ... --git-branch on a package that was created with copr add-package-pypi it will redefine the package from pypi to tito.

I think this violates the principle of least surprise. My expectation is that that would produce an error that you cannot use edit-package-tito on a pypi-source package.


Metadata Update from @clime:
- Issue assigned to clime

6 years ago

It's true that it might be an unwanted behavior. It's like that, however, to make package type changes possible (e.g. from tito to scm or vice versa).

Metadata Update from @clime:
- Issue assigned to frostyx (was: clime)

5 years ago

Metadata Update from @msuchy:
- Issue tagged with: UI, code-cleanup

5 years ago

Metadata Update from @frostyx:
- Assignee reset

3 years ago

This is though the only way to re-define the package from e.g. the -pypi to e.g. -scm. As for example discussed recently.

I'm sure currently it is not a 100% ideal UI, though changing this would require us to add new
CLI, Web UI forms and python API interface, and the work on that would be expensive. While
I appreciate any RFE, we won't have time for working on this issue. So I'm closing
this. Certainly through, pull requests on this topic would be accepted.

Metadata Update from @praiskup:
- Issue close_status updated to: Won't fix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata