Bug 1645771 - dnf copr remove doesn't work
Summary: dnf copr remove doesn't work
Keywords:
Status: CLOSED DUPLICATE of bug 1644563
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-03 14:25 UTC by Artem
Modified: 2018-11-05 14:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-05 14:42:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dnf copr remove name/project (1.18 KB, text/plain)
2018-11-03 14:25 UTC, Artem
no flags Details

Description Artem 2018-11-03 14:25:16 UTC
Created attachment 1500913 [details]
dnf copr remove name/project

Description of problem:

When i am trying to remove COPR repo i got error (attached in .txt file).


Version-Release number of selected component (if applicable):

dnf-4.0.4-1.fc29


How reproducible:

Enable any COPR repo first and then try to remove it.


Steps to Reproduce:

1. # dnf copr enable alunux/budgie-desktop-git 
2. # dnf copr remove alunux/budgie-desktop-git


Actual results:

See attached file.


Expected results:

Removed COPR repo.

Comment 1 Artem 2018-11-04 07:00:26 UTC
This only happens with an old format. After re-enable they can be removed without any issue.

For example:

1. # dnf copr enable alunux/budgie-desktop-stable
2. # dnf copr remove alunux/budgie-desktop-stable

---

$ sudo dnf copr list

copr.fedorainfracloud.org/alunux/budgie-desktop-git
copr.fedorainfracloud.org/phracek/PyCharm (disabled)
copr.fedorainfracloud.org/alunux/budgie-desktop-stable (disabled) *
* These coprs have repo file with an old format that contains no information about Copr hub - the default one was assumed. Re-enable the project to fix this.

Comment 2 Miroslav Suchý 2018-11-05 14:42:50 UTC

*** This bug has been marked as a duplicate of bug 1644563 ***


Note You need to log in before you can comment on or make changes to this bug.