Bug 1858448 - Upgrade Mono from 6.6 to 6.8 in Epel8
Summary: Upgrade Mono from 6.6 to 6.8 in Epel8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mono
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timotheus Pokorra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-18 04:16 UTC by Timotheus Pokorra
Modified: 2020-08-04 01:22 UTC (History)
7 users (show)

Fixed In Version: mono-6.8.0-3.el8
Clone Of:
Environment:
Last Closed: 2020-08-04 01:22:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Timotheus Pokorra 2020-07-18 04:16:30 UTC 
I tried to upgrade Mono from the tarball mono-6.6.0.161.tar.xz to mono-6.6.0.166.tar.xz, but I had issues building on the s390x architecture.

On the other hand, Ubuntu 20.04 LTS (focal) has Mono 6.8: https://packages.ubuntu.com/de/focal/mono-complete

So Mono 6.8 can be somehow considered LTS.

So it makes sense, to also move Mono in Epel8 to version 6.8

I have a successful scratch build across all architectures for Mono 6.8 for Epel8: koji.fedoraproject.org/koji/taskinfo?taskID=47361241
Comment 1 Fedora Update System 2020-07-18 06:25:39 UTC 
FEDORA-EPEL-2020-09dffd1659 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-09dffd1659
Comment 2 Fedora Update System 2020-07-19 02:00:13 UTC 
FEDORA-EPEL-2020-09dffd1659 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-09dffd1659

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2020-08-04 01:22:07 UTC 
FEDORA-EPEL-2020-09dffd1659 has been pushed to the Fedora EPEL 8 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.