Bug 428386 (urbanterror_update) - urbanterror 4.1 is available
Summary: urbanterror 4.1 is available
Keywords:
Status: CLOSED NOTABUG
Alias: urbanterror_update
Product: Fedora
Classification: Fedora
Component: quake3
Version: 8
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL: http://www.urbanterror.net/news.php
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-11 08:51 UTC by Sander Hoentjen
Modified: 2008-01-11 12:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-11 12:49:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.



Note You need to log in before you can comment on or make changes to this bug.