Bug 1824130 - openttd-opengfx 0.6.0 is available
Summary: openttd-opengfx 0.6.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openttd-opengfx
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Felix Kaechele
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-15 11:53 UTC by Kalev Lember
Modified: 2020-04-25 03:01 UTC (History)
1 user (show)

Fixed In Version: openttd-opengfx-0.6.0-2.fc32 openttd-opengfx-0.6.0-2.fc30 openttd-opengfx-0.6.0-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-25 02:24:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kalev Lember 2020-04-15 11:53:33 UTC
Looks like there's a new opengfx 0.6.0 release available at https://www.openttd.org/downloads/opengfx-releases/latest.html

Comment 1 Felix Kaechele 2020-04-15 13:20:32 UTC
Thanks for the report. I was talking to the OpenTTD devs the other day because I need a new release of nml to build 0.6.0. That was a few weeks ago.
But since it seems there hasn't been a new release. So I'll just update nml to git master for the time being and will push the 0.6.0 update.

Comment 2 Kalev Lember 2020-04-15 14:29:25 UTC
Sounds like a good plan to me. Thanks!

Comment 3 Fedora Update System 2020-04-16 02:06:17 UTC
FEDORA-2020-99f0c1ccc0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-99f0c1ccc0

Comment 4 Fedora Update System 2020-04-16 02:06:18 UTC
FEDORA-2020-539d0f4170 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-539d0f4170

Comment 5 Fedora Update System 2020-04-16 02:06:18 UTC
FEDORA-2020-e45a108089 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e45a108089

Comment 6 Fedora Update System 2020-04-16 19:29:27 UTC
FEDORA-2020-99f0c1ccc0 has been pushed to the Fedora 32 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-99f0c1ccc0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-99f0c1ccc0

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

Comment 7 Fedora Update System 2020-04-16 22:18:18 UTC
FEDORA-2020-e45a108089 has been pushed to the Fedora 31 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-e45a108089`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e45a108089

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

Comment 8 Fedora Update System 2020-04-16 23:28:42 UTC
FEDORA-2020-539d0f4170 has been pushed to the Fedora 30 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-539d0f4170`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-539d0f4170

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

Comment 9 Fedora Update System 2020-04-25 02:24:16 UTC
FEDORA-2020-99f0c1ccc0 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-04-25 02:42:53 UTC
FEDORA-2020-539d0f4170 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2020-04-25 03:01:39 UTC
FEDORA-2020-e45a108089 has been pushed to the Fedora 31 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.