Bug 1893422 - Conflict with openjfx8 doing update
Summary: Conflict with openjfx8 doing update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openjfx
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nicolas De Amicis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-31 08:55 UTC by Yaroslav Sidlovsky
Modified: 2020-11-10 05:31 UTC (History)
4 users (show)

Fixed In Version: openjfx-11.0.9.2-3.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-06 01:14:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Yaroslav Sidlovsky 2020-10-31 08:55:55 UTC
Description of problem:
I've got conflict doing `dnf update --refresh`:
```
Problem: package openjfx-devel-11.0.9.2-1.fc33.x86_64 requires openjfx(x86-64) = 11.0.9.2-1.fc33, but none of the providers can be installed
- package openjfx8-8.0.202-25.b07.fc33.x86_64 obsoletes openjfx <= 2:8.0.202-13 provided by openjfx-11.0.9.2-1.fc33.x86_64
- cannot install the best update candidate for package openjfx-devel-11.0.9.2-1.fc33.x86_64
- cannot install the best update candidate for package openjfx-11.0.9.2-1.fc33.x86_64
```

Am I doing something wrong?

Comment 1 Fedora Update System 2020-11-02 14:35:23 UTC
FEDORA-2020-a0522d2911 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a0522d2911

Comment 2 Fedora Update System 2020-11-03 02:25:42 UTC
FEDORA-2020-a0522d2911 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a0522d2911`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a0522d2911

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Yaroslav Sidlovsky 2020-11-03 10:42:14 UTC
After doing `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a0522d2911` I see this error:
```
 Problem 1: cannot install the best update candidate for package openjfx-devel-11.0.9.2-1.fc33.x86_64
  - nothing provides openjfx(x86-64) = 11.0.9.2-2.fc33 needed by openjfx-devel-3:11.0.9.2-2.fc33.x86_64
 Problem 2: problem with installed package openjfx-devel-11.0.9.2-1.fc33.x86_64
  - package openjfx-devel-11.0.9.2-1.fc33.x86_64 requires openjfx(x86-64) = 11.0.9.2-1.fc33, but none of the providers can be installed
  - cannot install both openjfx-3:11.0.9.2-2.fc33.x86_64 and openjfx-11.0.9.2-1.fc33.x86_64
  - cannot install both openjfx-11.0.9.2-1.fc33.x86_64 and openjfx-3:11.0.9.2-2.fc33.x86_64
  - cannot install the best update candidate for package openjfx-11.0.9.2-1.fc33.x86_64
  - nothing provides openjfx(x86-64) = 11.0.9.2-2.fc33 needed by openjfx-devel-3:11.0.9.2-2.fc33.x86_64
```

Comment 4 Fedora Update System 2020-11-03 16:23:42 UTC
FEDORA-2020-07d4c64208 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-07d4c64208

Comment 5 Fedora Update System 2020-11-04 03:01:51 UTC
FEDORA-2020-07d4c64208 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-07d4c64208`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-07d4c64208

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Yaroslav Sidlovsky 2020-11-05 12:31:58 UTC
Update FEDORA-2020-07d4c64208 works as expected - I'm able to update openjfx without conflicts.
Thanks!

Comment 7 Fedora Update System 2020-11-06 01:14:55 UTC
FEDORA-2020-07d4c64208 has been pushed to the Fedora 33 stable repository.
If problem still persists, 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.