Bug 117973

Summary: unison heavily outdated - please update!
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Lenz Grimmer <lgrimmer>
Component: X11 ApplicationsAssignee: Heiko Rommel <heiko.rommel>
Status: RESOLVED WONTFIX QA Contact: Stefan Dirsch <sndirsch>
Severity: Normal    
Priority: P5 - None    
Version: RC 1   
Target Milestone: ---   
Hardware: Other   
OS: All   
URL: http://www.cis.upenn.edu/~bcpierce/unison
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: unison.spec

Description Lenz Grimmer 2005-09-20 11:06:49 UTC
Unfortunately I noticed that too late for the 10.0 release - the version of
unison on the distribution is quite aged by now. Never versions are available,
and the UI now even supports GTK2 (requires lablgtk2 to be built first). Please
update unison to the latest version (current version is 2.13.16) - see the URL.
If possible, also change the build to use GTK2 instead, thanks!
Comment 1 Lenz Grimmer 2005-09-20 11:07:55 UTC
Created attachment 50410 [details]
unison.spec

Updated spec file for unison 2.13.16 - feel free to use it.
Comment 2 Michael Gross 2005-09-20 11:16:23 UTC
Will surely be done for the next version. The package-maintainer has been notified.
Comment 3 Michael Gross 2005-09-20 11:17:01 UTC
Closing this with reso:later.
Comment 4 Stephan Kulow 2008-06-25 09:33:29 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:35:09 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:41:14 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 7 Stephan Kulow 2008-06-25 09:52:49 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(