Bug 428386 (urbanterror_update)

Summary: urbanterror 4.1 is available
Product: [Fedora] Fedora Reporter: Sander Hoentjen <sander>
Component: quake3Assignee: Hans de Goede <hdegoede>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.urbanterror.net/news.php
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-11 12:49:35 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:

Description Sander Hoentjen 2008-01-11 08:51:05 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
4.0-1

How reproducible:
always

Steps to Reproduce:
1. start urbanterror
2. try to join a game
  
Actual results:
get some error message, that after googling means you have to update your client

Expected results:
game joined, ready to play

Additional info:
Comment 1 Sander Hoentjen 2008-01-11 09:21:24 UTC 
Hum, I must have installed a package from the review process or something. But
the problem will remain with an update from one version to another:
in the bin file is this line:
if [ ! -f ~/.q3a/q3ut4/zpak000.pk3 ]; then
but with 4.1, you already get this file, so if it is the same in 4.2 there is a
problem.
Comment 2 Hans de Goede 2008-01-11 12:49:35 UTC 
(In reply to comment #1)
> Hum, I must have installed a package from the review process or something. 

Correct, there once was a plan to make urbanterror a seperate package the plan
has changed.

> But
> the problem will remain with an update from one version to another:
> in the bin file is this line:
> if [ ! -f ~/.q3a/q3ut4/zpak000.pk3 ]; then
> but with 4.1, you already get this file, so if it is the same in 4.2 there is a
> problem.

I know, the autodl wrapper scripts need some work to handle this, I already have
some plans on howto handle this, but currently I have other priorities, I'll
deal with that situation when it actually occurs. Closing this as not a bug.