Bug 145780

Summary: Suggested update of BZFlag to 2.0.0
Product: [Fedora] Fedora Reporter: Matthias Saou <matthias>
Component: bzflagAssignee: Alan Cox <alan>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: nphilipp, wtogami
Target Milestone: ---Keywords: EasyFix, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-20 03:35:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to update to 2.0.0. none

Description Matthias Saou 2005-01-21 15:58:40 UTC
BZFlag has reached 2.0.0. This is a major update, as network gameplay
with prior versions is incompatible, but given all the improvements,
it's definitely worth having in FC4.

Attached is a patch to the current FC Development spec file. See the
few comments in the %changelog for details about the changes.

It may also worth doing a quick check to see if this update may fix
#139832 by any chance.

Comment 1 Matthias Saou 2005-01-21 15:59:32 UTC
Created attachment 110054 [details]
Patch to update to 2.0.0.

Comment 3 Alan Cox 2005-01-31 15:17:17 UTC
The problem is that bzflag2 and bzflag1 are not fully compatible and at the
moment quite a few of the major servers are still bzflag1. I agree with Matthias
I think because by FC4 release everyone will be using bzflag2