Bug 921472 - wesnoth UI window title should drop (Unversioned directory)
Summary: wesnoth UI window title should drop (Unversioned directory)
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: wesnoth
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-14 09:46 UTC by Parag Nemade
Modified: 2013-09-10 16:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-10 16:13:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Turns off the svn revision string whenever svnversion does not find one. (371 bytes, patch)
2013-03-14 09:46 UTC, Parag Nemade
no flags Details | Diff

Description Parag Nemade 2013-03-14 09:46:03 UTC
Created attachment 709936 [details]
Turns off the svn revision string whenever svnversion does not find one.

Description of problem:
I got following problem reported by Wolfgang Lieff. I am just rewriting it on behalf of him as he don't have bugzilla account.

When rebuilding wesnoth-1.10.5-5 on a system which has 'svnversion' in
the path, scons (via the main 'SConstruct') appends the string
'(Unversioned directory)' to the program name - and thus eg. to the
window title - which, while true (as it is a released version and not an
svn snapshot), is rather annoying ...

Attached patch turns off the svn revision string whenever svnversion does
not find one.

Version-Release number of selected component (if applicable):
wesnoth-1.10.5-5

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:
check the UI window title it shows (Unversioned directory)

Expected results:
it should not show like (Unversioned directory)

Additional info:

Comment 1 Gwyn Ciesla 2013-03-14 17:29:43 UTC
I have no objection to the patch, but I don't see this on 1.10.5-3 on f18 in Gnome 3.  Is this in another DE?


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