Bug 1941220 - Upgrade to 5.4
Summary: Upgrade to 5.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: minetest
Version: 34
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aleksandra Fedorova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1947701 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-20 22:09 UTC by Sahaj Sarup
Modified: 2021-04-24 20:13 UTC (History)
5 users (show)

Fixed In Version: minetest-5.4.1-1.fc33 minetest-5.4.1-1.fc32 minetest-5.4.1-1.fc34
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-24 18:05:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
minetest diff file (1.07 KB, patch)
2021-04-09 14:23 UTC, Fábio Rodrigues Ribeiro
no flags Details | Diff

Description Sahaj Sarup 2021-03-20 22:09:09 UTC
Its been almost a month since 5.4 release. 5.3 now breaks on atleast aarch64 for f34.
Requesting upgrade to 5.4

Comment 1 Fábio Rodrigues Ribeiro 2021-04-09 12:37:14 UTC
*** Bug 1947701 has been marked as a duplicate of this bug. ***

Comment 2 Fábio Rodrigues Ribeiro 2021-04-09 14:23:54 UTC
Created attachment 1770651 [details]
minetest diff file

Build passed in koji... https://koji.fedoraproject.org/koji/taskinfo?taskID=65579696

Build falied in copr... https://copr.fedorainfracloud.org/coprs/farribeiro/minetest/build/2124007/

Comment 3 Fedora Update System 2021-04-16 20:37:50 UTC
FEDORA-2021-26ea2b3f63 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-26ea2b3f63

Comment 4 Fedora Update System 2021-04-16 20:37:53 UTC
FEDORA-2021-6b19a2e738 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6b19a2e738

Comment 5 Fedora Update System 2021-04-16 20:37:56 UTC
FEDORA-2021-0a702ee90e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-0a702ee90e

Comment 6 Fedora Update System 2021-04-17 14:34:52 UTC
FEDORA-2021-0a702ee90e has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0a702ee90e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0a702ee90e

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

Comment 7 Fedora Update System 2021-04-17 14:49:02 UTC
FEDORA-2021-26ea2b3f63 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-26ea2b3f63`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-26ea2b3f63

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

Comment 8 Fedora Update System 2021-04-18 17:03:54 UTC
FEDORA-2021-6b19a2e738 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-6b19a2e738`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6b19a2e738

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

Comment 9 Fedora Update System 2021-04-24 18:05:41 UTC
FEDORA-2021-26ea2b3f63 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2021-04-24 18:23:27 UTC
FEDORA-2021-0a702ee90e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2021-04-24 20:13:43 UTC
FEDORA-2021-6b19a2e738 has been pushed to the Fedora 34 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.