Bug 1733949 - Two different repositories are reported instead of one regarding Opera for Linux
Summary: Two different repositories are reported instead of one regarding Opera for Linux
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-29 10:00 UTC by ricky.tigg
Modified: 2019-07-29 14:38 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description ricky.tigg 2019-07-29 10:00:37 UTC
Description of problem: Once package –https://www.opera.com/download?os=linux_ from a third-party software has been installed on system dnf displays two different repositories.

Version-Release number of component: dnf.noarch 4.2.5-2.fc30 @updates
Actual results:

$ dnf -q repolist | grep opera
opera                               Opera packages                 6
$ dnf -q list installed opera-stable | sed -n '2p'
opera-stable.x86_64                 62.0.3331.99-0                 @@commandline

Expected results: existence of at most one repository here "opera" instead of "@@commandline".

Comment 1 Jaroslav Mracek 2019-07-29 10:30:54 UTC
Please could you provide an output from command 'sudo dnf history info opera-stable | grep opera-stable'

Comment 2 ricky.tigg 2019-07-29 11:30:04 UTC
$ LANG=C sudo dnf history info opera-stable | grep opera-stable
    Install opera-stable-62.0.3331.99-0.x86_64 @@commandline
Command Line   : -y remove opera-stable
    Removed opera-stable-62.0.3331.99-0.x86_64 @@System
    Upgrade  opera-stable-62.0.3331.99-0.x86_64               @opera
    Upgraded opera-stable-62.0.3331.66-0.x86_64               @@System
    Install opera-stable-62.0.3331.66-0.x86_64 @@commandline

An installation relying on Gnome Software 3.32.2 was attempted first, while an installation already existed. Then the package was uninstalled using command line then reinstalled relying on Gnome Software.

Comment 3 Jaroslav Mracek 2019-07-29 14:38:50 UTC
Thanks a lot, it means that the problem is probably in libdnf code that is used by packagekit. I am changing the component to packagekit, because I belive that they know how PackageKit is using the library.


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