Bug 1739773 - Wrong behavior using dnf update for downloaded package
Summary: Wrong behavior using dnf update for downloaded package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 30
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
Assignee: Marek Blaha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-10 10:41 UTC by vkeranov
Modified: 2019-10-10 16:55 UTC (History)
10 users (show)

Fixed In Version: dnf-4.2.11-2.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-10 16:55:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description vkeranov 2019-08-10 10:41:36 UTC
Description of problem:
Some software vendors don't include package version in their file name. For example: skypeforlinux-64.rpm; viber.rpm; etc.
It it not so easy to find up-to-date changelog for some of these programs. Viber is a good example and while its Windows version is 11.3, the linux is still at 10.3. The only way to check for a newer version is by simply downloading it every month or so. Then update with:
sudo dnf update /path/to/viber.rpm

The result is:
Package viber of higher version already installed, cannot update it.
Dependencies resolved.
Nothing to do.

The installed package is not higher version, it is the same version, which means dnf can not correctly compare package versions (at least for locally downloaded packages).


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


How reproducible:


Steps to Reproduce:
1. Download viber: wget https://download.cdn.viber.com/desktop/Linux/viber.rpm
2. Try to update it (we don't have an info for the package version, nor updated changelog.
3. sudo dnf update /path/to/viber.rpm

Actual results:
Package viber of higher version already installed, cannot update it.

Expected results:
Same version of package viber already installed.

Additional info:
Maybe dnf needs better version check?

Comment 1 Marek Blaha 2019-09-03 11:54:08 UTC
I enhanced the "dnf update" message: https://github.com/rpm-software-management/dnf/pull/1473

Comment 2 Fedora Update System 2019-10-02 08:31:56 UTC
FEDORA-2019-049b4836a6 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-049b4836a6

Comment 3 Fedora Update System 2019-10-03 01:52:34 UTC
dnf-4.2.11-2.fc30, dnf-plugins-core-4.0.10-1.fc30, libdnf-0.35.5-2.fc30, librepo-1.10.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-049b4836a6

Comment 4 Fedora Update System 2019-10-10 16:55:59 UTC
dnf-4.2.11-2.fc30, dnf-plugins-core-4.0.10-1.fc30, libdnf-0.35.5-2.fc30, librepo-1.10.6-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


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