Bug 1968416 - Please update PrBoom-Plus to new maintained version
Summary: Please update PrBoom-Plus to new maintained version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: prboom-plus
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-07 11:17 UTC by Simon Putt
Modified: 2021-06-16 20:47 UTC (History)
2 users (show)

Fixed In Version: prboom-plus-2.6-1.fc34
Clone Of:
Environment:
Last Closed: 2021-06-16 20:47:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Simon Putt 2021-06-07 11:17:12 UTC 
Hiya

I was just wondering if PrBoom-Plus could be updated to the new branch that's now used as the current one is now unmaintained

The new branch is here

https://github.com/coelckers/prboom-plus/releases

Many thanks if you consider this.
Comment 1 Fedora Update System 2021-06-07 18:12:52 UTC 
FEDORA-2021-ab6c829e20 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ab6c829e20
Comment 2 Simon Putt 2021-06-07 19:47:16 UTC 
Thanks very much for updating this, just tried it out with a number of iwad/pwad files and all seems to work fine
Comment 3 Gwyn Ciesla 2021-06-07 20:07:01 UTC 
You're very welcome!
Comment 4 Fedora Update System 2021-06-09 01:16:55 UTC 
FEDORA-2021-ab6c829e20 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-ab6c829e20`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ab6c829e20

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2021-06-16 20:47:47 UTC 
FEDORA-2021-ab6c829e20 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.