Actually, I take that statement about those commands back. They would probably work with this as the argument: https://copr-be.cloud.fedoraproject.org/results/mikedep333/nx-libs-3.6/fedor...
Although you would have to fill in the values of $releasever and $basearch yourself.
Still, the dnf copr enable mikedep333/nx-libs-3.6 command is what you want.
On Wed, Sep 28, 2016 at 3:43 PM, Mike DePaulo <mikedep333@gmail.com> wrote:
The following URL: https://copr.fedorainfracloud.org/coprs/mikedep333/nx-libs-3.6/ Is not the URL to the repo. It is the web page / webGUI for the repo.
As explained on the right of the page, try this command: dnf copr enable mikedep333/nx-libs-3.6
I assume that those commands would work with "mikedep333/nx-libs-3.6" as the argument too.
-Mike
On Wed, Sep 28, 2016 at 3:36 PM, Robert Dinse <nanook@eskimo.com> wrote:
Hate to be a pest, I am sure this is something stupid I am doing wrong.I followed the instructions in the Fedora 24 manual for adding and enabling a repository:
dnf config-manager --add-repohttps://copr.fedorainfracloud.org/coprs/mikedep333/nx-libs-3.6/
dnf config-manger --set-enabledhttps://copr.fedorainfracloud.org/coprs/mikedep333/nx-libs-3.6/
Both on one line, pico made it line wrap because it didn't fit in thee-mail.
The second command that is supposed to enable tells me no suchrepository even though sent after the first.
I've more or less come to the conclusion that 'dnf' stands for Does NotFunction but that's an aside.
Is there a new trick to this? I could not find the files to editdirectly, neither /etc/yum/repos.d nor /etc/dnf anything that remotely looked like a repository so I'm kind of stuck.
< [...]