Description of problem:
DNF is not support url rpm installation as yum supports.
Version-Release number of selected component (if applicable):
dnf install http://kojipkgs.fedoraproject.org//packages/python-flask-sqlalchemy/1.0/2.fc20/noarch/python-flask-sqlalchemy-1.0-2.fc20.noarch.rpm
Error: Nothing to do.
It's should fetch the rpm and install it after resolving the dependencies.
Praveen, just to confirm, what does 'rpm -q python-flask-sqlalchemy' return?
Maybe related to bug 1049671, Radek please take a look once the time permits.
Fixes the bug for me..
Author: Zdenek Pavlas <firstname.lastname@example.org>
Date: Wed Jan 22 09:12:18 2014 +0100
Installing a local pkg is okay. (RhBug#1056400)
diff --git a/dnf/cli/cli.py b/dnf/cli/cli.py
index 16ba6c2..5ca258c 100644
@@ -322,6 +322,7 @@ class BaseCli(dnf.Base):
for arg in userlist:
+ done = True
continue # it was something on disk and it ended in rpm
# no matter what we don't go looking at repos
Reproduces even when pkg is not installed..
It's different from #1049671 ( which claims that local downloaded package not able to install) , In this bug if 'python-flask-sqlalchemy' don't present locally then it's suppose to download with give url and store in some tmp location as yum use to do and then install.
moving this to Zdenek who's got a patch.
*** Bug 1049671 has been marked as a duplicate of this bug. ***
*** Bug 1058980 has been marked as a duplicate of this bug. ***
The patch is merged upstream.
*** Bug 1060166 has been marked as a duplicate of this bug. ***
dnf-0.4.13-2.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnf-0.4.13-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnf-0.4.13-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
That's works. Solved.
*** Bug 1070441 has been marked as a duplicate of this bug. ***